Even better is the licensing model where you can keep using the version as-is after the subscription ends. You just don't get any new features. It's even possible to do on iOS, as Working Copy [0] is doing it. (You also get all the bug fixes and stuff, only new features are behind a flag that requires you to purchase another year of updates. I would also argue that Working Copy specifically is too cheap, but I... - Source: Hacker News / almost 3 years ago

Yeah, Working Copy is a proper Git front-end which helps do safe syncing, via features such as:. Source: over 3 years ago

So I have a laptop and a iPhone. On laptop I have the Obsidian.md desktop app, on iPhone I have the app and Working Copy app too. This is all for syncing my notes. Source: over 3 years ago

> It uses the same format of storage as Obsidian... Can Obsidian and Jot co-mingle in the same vault? I use Obsidian and am very happy with the git plugin[0] and Working Copy(iOS)[1] for keeping things automatically synced between my phone and desktop(s). Often I find myself dumping notes into random places from the terminal; feeding markdown via pipes. But I then have to remember to collect these artifacts and... - Source: Hacker News / almost 4 years ago

This is the only one I've heard people use: https://workingcopyapp.com/. Source: about 4 years ago

I have a small "GitHub summarizer" agent: one system prompt, one job — answer questions about my GitHub account by calling the GitHub MCP server. I duplicated its configuration (MAVERIK supports this directly — same model, same prompt, same everything) and changed one field on the copy: the set of attached MCP servers, adding deepwiki, microsoft-learn, and context7. Neither agent needs any of those three for the... - Source: dev.to / 12 days ago

GitHub's official MCP server is excellent — and GitHub is narrowing its default toolset and consolidating PR tools into fewer, more capable ones, explicitly to cut tool bloat and improve agent reasoning. The implication is hard to miss: even one of the best API companies on the planet is learning that a 1:1 mapping from product API to agent tools isn't the right shape. - Source: dev.to / about 2 months ago

The official GitHub MCP server registers 83 tools. Most people set it up for reading code and managing issues. What they don't realise is they've also handed their agent the keys to:. - Source: dev.to / about 2 months ago

A lot of people use MCP servers to connect Claude to tools. I'm not generally a fan. MCP servers load a lot of information into context and often don't do everything that the API can. Last I looked, even the official Github MCP Server is guilty of this. I'd rather write tools directly, to my specifications. - Source: dev.to / 4 months ago

Rather than manually searching through repositories, I used Kiro with the GitHub MCP server to:. - Source: dev.to / 4 months ago