Nexus
My answer to Jira going down for a couple hours.
Board, tickets, state machine. No Jira.
Themed viewer for reports from Claude Code.
Where Claude's design mockups go for future reference
Architectural graph of all projects, powered by Sonny
For when I forget things
00What it is
More than just my project board, it's where my agent pipeline lives. Live agent session monitoring, a full ticket board, architectural diagrams for all projects, report consolidation, and a glossary.
- Multi-project ticket board with full state machine, atomic claim, and branch and PR links
- Live Sessions view showing each active agent's current step, heartbeat, and alerts in real time
- Themed Reports hub for standups, post-mortems, swarm summaries, and session reports
- Designs tab as a stable home for Claude-authored mockups, linked to the ticket they belong to
- Architecture tab driven by Sonny, refreshed daily across every project
- Glossary as a graph rather than a simple document
- Local-first storage: JSON files, no database, optional auto-commits to a separate data repo
- Anchors a deliberate agent pipeline (brainstorm, spec, plan, TDD, friction-pattern review, PR) rather than free-form code generation
- Self-healing swarm supervision: heartbeat monitoring, automatic restarts on stall, end-of-run HTML reports
01Why it exists
Because I learned to use Jira as part of my daily work routine years ago, setting it up for my personal projects seemed like a no-brainer. It was a good opportunity to test what I knew, and fill in the gaps of what I didn't. After a month of using it with Claude Code through the MCP, I saw some limitations, and some opportunities to streamline my own workflow.
I was also generating a lot of reports from Claude Code. Not just the specs and implementation plans, but agent session reports. Learnings from debugging and troubleshooting. Targeted investigations on best practices for new frameworks like Liquid Glass. I decided I should have something better than markdown files, and the result was the first iteration of Nexus- a report viewer with a theme picker. When Atlassian had a major outage one evening, I started wondering if I could build my own solution, chiselled down to just the parts I needed.
What started as a simple report viewer grew a ticket board, knowledge repo, design extension for Claude, and a full workflow hub as each gap became obvious.
02What I built
Nexus runs locally as a Node.js server backed by plain JSON files. The ticket system handles multiple project spaces, full state transitions, comments, branches, and PR links, with auto-commits to a separate data repo so the code stays clean.
The reports hub is a themed viewer for everything Claude generates during a session: standups, post-mortems, swarm summaries, insights. Additional themes are easily added according to the vibe of the day. Themes apply everywhere, picked by whatever the vibe of the day is. The designs tab is where mockups and visual decisions live, so they don't get lost in chat history.
The architecture tab runs Sonny against any project and renders the result as a navigable graph showing types, dependencies and relationships without leaving the hub. Same format for the glossary. Explore, don't just read.
03What's next
Nexus evolves with my workflow. Each agent session that surfaces a gap becomes a ticket. It's a tool I use every day, and the backlog is the roadmap.