Run Claude Code and Codex the way you run your team.

Delegate a task, review the plan and the diff, ship the pull request — from a keyboard-first Mac app, any browser, or your phone.

Keyboard-first
Uses your Claude or ChatGPT subscription
Source-available on GitHub

Solus

Fri, Aug 28 9:41 AM

Solus — acme

Solus

Download for macOS

The workflow

Delegate. Review. Ship. The loop you already run.

Solus maps agent work onto the way software actually gets built. Hand work off like you would to a teammate, gate it twice, land it clean.

01 / Delegate

Hand off work like a teammate.

Create a session, assign the task, and let the agent plan, code, and validate end to end. It asks before it runs anything you have not already allowed.

⌘T new session, new task

The Solus workspace running a task: the agent explains its plan while a permission card asks to run the test command, with branch, git state, and task panels alongside.

02 / Review

Review intent, then output.

A second agent reads the branch and writes a guided report — what to check, in what order, and why it matters — with each concern sitting next to the exact code it refers to.

4 concerns · +31 −0 · per-file

The Solus review guide for a rate-limiting change, listing numbered concerns beside the token bucket and middleware code they refer to.

03 / Ship

Land approved work cleanly.

Reviewers, checks, and every changed file in one place. Merge when it is ready, or hand a conflicted branch back to an agent in its own worktree.

✓ ready to merge

How it works

Built for how engineers
actually work.

The spec is in Confluence. The ticket is in Jira. The diagram went stale three sprints ago. Solus reaches all of it, so the agent works from the context you work from — and writes back to it when it's done.

Specs

Read the spec where it lives.

Hand an agent a Confluence link or a Google Doc URL and it reads the real page. Or let it search across both by full text when you only half-remember which doc it was.

search_docs · read_doc

Tickets

Work the ticket, not a copy of it.

Jira and GitHub Issues sync both ways. Pull a ticket in as a task, push status and field changes back, and post the comment from the session that did the work.

jira · github issues

A task open full width in Solus, synced with Jira ticket ACME-214: the spec in the body, the agent session working it, an upstream panel naming Jira, and a thread where the agent and two people answer each other. — One ticket, synced with Jira — the spec in the body, the session working it, and a thread where the agent answers the reviewer directly. Status, labels and comments move in both directions.

Write-ups

Publish the result back out.

Docs, decks, and diagrams the agent produces are real artifacts. Publish one to Confluence or Google Docs and it stays linked, so the next publish updates that same page instead of littering copies.

publish_work · pull_work_upstream

A rollout runbook open in Solus: a numbered table of contents, a decision summary, and an open comment thread, with a Publish action in the header. — The runbook that came out of this task — its own table of contents, an open comment thread, and Publish in the header.

Diagrams

Architecture you can edit, not a screenshot.

System, data-flow, and ER diagrams render on a canvas you can rearrange, drill into, and keep next to the code. Serialize to Mermaid when it needs to live in the repo.

mermaid export

The billing end of an architecture diagram: Redis feeding a billing worker over a usage queue, a PostgreSQL node listing typed columns and keys, and a dashed edge to Stripe. — The billing end of the same diagram. Store nodes carry their columns, keys, and types; dashed edges mark the async hops. Drag a node and the layout follows.

Atlassian and Google connect once in Settings. Everything above is a tool the agent can call in any session — no copy-and-paste round trip, and nothing leaves your machine except the calls to those services.

Features