Hand over the work. Keep the decisions.
Shinsa runs Claude Code and Codex on your own machine, from your request to a merged pull request, checking their work at every step. You step in only for what needs a person: the review, the merge and the odd question.
You see decisions, not chats.
A task stops for you only at a gate: the review, the merge, a question when the agent is stuck, and the plan when you turn plan approval on. Everything between them is Shinsa’s job. Try it below: take one task from its plan to its merge.
Try it: approve the plan.
Split store onboarding into steps
Not every request ends in a pull request.
Shinsa reads what you asked for and picks the path. A question gets an answer, a bug gets a diagnosis first, an operation waits for your OK. You never choose a mode.
Review the change, not the diff.
The agent hands over a work report: what it did, phase by phase, pointing at the lines that need your eyes, ranked by risk. A second agent reviews it first, with fresh context.
Open a file
Pick one in the list, or press Ctrl+P to open any file by name.
Many agents at once. One list for you.
Every task runs on its own agent, in its own worktree and branch. A task that depends on another waits until it merges. You work down one list, in the order things need you.
All tasks
8 open · 2 done
Checked at every step, without you.
Shinsa runs your repository’s own checks itself, so a green build is a fact, not an agent’s claim. A separate agent reviews every change. Failing CI and review-bot comments go back to the agent that built it. You hear about it again when it is ready to merge.
Nothing reaches main without you.
Agents never commit, push or merge. Shinsa does, and only after your review and your merge. Every command an agent runs is checked before it runs, and for the default branch itself Shinsa sets you up with GitHub branch protection.
Runs on your machine
One local server and a Mac app. Your repositories never leave your disk, and there is no cloud.
Your agents, your accounts
Claude Code and Codex, on the logins you already have. When one account hits its limit, the next one takes over.
Your tools come along
The MCP servers, skills and plugins you set up in Claude Code and Codex load for every agent.
Every decision is a record
Tasks, gates and answers are events in a log. Restart anything and the work carries on where it was.
Lean context
MCP servers and skills an agent has not used in 30 days stay out of its context, and load mid-run when it needs one.
Usage limits handled
A run that hits a limit moves to an account with room. With none left, the task waits for the reset and carries on.
Rounds
A new idea in the chat starts the next round on the same branch and the same agent session, which remembers everything.
Focus
Say which project you are on. Decisions from the others wait quietly until you switch.
Evidence
Agents attach screenshots in both themes, recordings, and tests that failed before the change and pass after it.
A worktree per task
Every task gets its own worktree and branch, so ten agents never touch the same files.
Schedules and webhooks
Run a request every night, or when something happens in another service.
Agents manage Shinsa
An agent can start, prioritise and order tasks for you. The decisions at your gates stay yours.
A command line
The shinsa command does everything the app does, for you and for agents in your own terminal.
One shortcut
⌘K reaches every task, every action and the next decision that needs you.
A Mac app
A Dock badge with what needs you, notifications, and links that open a task.
Open source
MIT licensed and free. Read every line, run it, change it.