Sharing my open source developer hub A developer has released DevHub, an open-source local desktop dashboard that consolidates tasks, notes, pull requests, repos and AI coding agents into a single window. The app embeds a local helper called Paseo for chatting with Claude Code, Codex, Cursor, OpenCode and Copilot, syncs reusable Skills and Personas across those tools, and exposes MCP tools so agents can operate DevHub itself. Agent-proposed changes require a review step showing the exact destination and content before anything is sent, while the developer's own actions remain one-click. About six months ago I got fed up with how many tabs my working day needed. Jira in one, GitHub in another, notes somewhere else, a terminal or three, and then a couple of AI coding agents each with there own set of skills and personalities. So I started building something for myself. It's called DevHub, it's a desktop app that puts tasks, notes, pull requests, repos and coding agents in one window. I've been slowly adding to it since, mostly whenever something in my own day annoyed me enough. It's reached the point where it might be useful to other people, so I thought I'd share it. That's recorded against throwaway fixture data, not real accounts. DevHub is a local dashboard. Everything is stored as files on your own machine, and the integrations GitHub, Jira, Google Calendar and so on are all optional. If you don't connect Jira, you just don't see the Jira pages. The bits I use most: There's also a git client, a Databases page SQLite, Postgres and MongoDB and full-text search. The part that's grown the most is agents. DevHub has Paseo embedded, a small local helper, so you can chat with Claude Code, Codex, Cursor, OpenCode or Copilot from inside the app. Where it can read your sign-ins, it'll also show how much of each subscription you've used, which has saved me a few surprises. The other thing I wanted was for all my AI tools to work to the same standards without me setting each one up by hand. DevHub has a Skills page for that. A skill is a reusable set of instructions; you write it once and DevHub copies it into Claude Code, Codex, Cursor, OpenCode and Antigravity. A Persona tab does the same for your engineering standards, and there's a "My voice" quiz that teaches agents to write a bit more like you. It also goes the other way. DevHub exposes MCP tools, so agents can use DevHub itself, rather than me copying things between windows. This is the decision I've thought about most. If I want to move a Jira ticket, that's one click. I'm the human, I know what I'm doing mostly , and I don't want a confirmation dialog getting in the way. If an agent wants to change something, it's different. Agent-proposed changes get a review step: you see the exact ticket or PR proposal, and the exact destination and content, before anything is sent. A few other things fall out of that: It's a bit more friction, but I'd rather that than find out afterwards that something got posted somewhere. I built it around my own setup, which happens to be Jira and GitHub, but I didn't want it to only work for that. It's somewhat agnostic, and there's a plugin system so people can add their own workflows. A plugin is just a separate repo with a devhub-plugin.json in it. It can add skills, agents, MCP servers, dashboard pages or database connections. In the app you go to Plugins, Add from GitHub, paste the URL, review what it adds and enable it. From a checkout it's: npm run plugins -- add