Fellowship
In active development

Your agents. One place to build.

A local workbench for Codex and Claude Code. Bring your projects, agent teams, Git and review into one visible workflow.

Explore the workbench Explore the workflow
Your installed coding clientsYour local projects
Workflow illustrationExample project: Atlas
Not a live run or app screenshot
  1. 01 Scope
  2. 02 Build
  3. 03 Checks
  4. 04 Review
  5. 05 Delivery
  6. 06 Feedback

Start with a project and an objective.

Choose the working folder. Set the goal and the team’s limits before work begins.

Named project / explicit scope

Give each assignment a place to work.

A coordinator directs workers in separate worktrees. Follow the exact assignment, files and conversation.

Direct assignments / separate branches

Run the checks you named.

Save the required commands and inspect their output against the combined commit. Incomplete evidence stays visible.

Saved commands / inspectable output

Review the result. Ask for changes.

Bring in a fresh reviewer. Inspect the combined work, request another revision, then explicitly accept the result.

Fresh review / owner acceptance

Give delivery its own task.

Prepare a separate Solo task from accepted source. Use your external release tools; acceptance does not deploy it.

Separate delivery / external release tools

Bring the next change back.

Record a delivery, check an endpoint once, and queue a follow-up from what you observe. Start new work explicitly.

Delivery records / follow-up queue

One place to follow the work. From a scoped objective to a reviewed change.

Read the current status

Keep the work in context.

The folder, the conversation, the agent and the diff belong together. Fellowship brings them into a shared workbench, with visible assignments and explicit actions.

Projects with a name and a place

Open a local project, name its conversations, browse files and inspect changes. Isolated tasks bind the work to a specific checkout.A worktree separates files and branches; it is not an operating-system sandbox.

Solo focus or a bounded team

Use an installed Codex or Claude Code client. Work in one conversation, or give a coordinator scoped assignments, separate worktrees and explicit team limits.Client installation, account access and native execution policies still apply.

Conversations with a destination

Follow direct messages, channels and individual assignments. Keep the selected recipient and task in view as you move around the workbench.

Source control beside the work

Inspect status, diffs and history. Stage whole files, commit, fetch, pull a clean fast-forward or review a guarded push.Managed Team checkouts restrict mutations. PR creation and merge use external tooling.

Make completion inspectable.

A useful workflow leaves something you can review: a specific change, its check output, and a clear decision about what happens next.

  1. Name the checks before the run.

    Define the commands, working directory and time limits for the combined result.

  2. Keep the review attached to the change.

    Inspect files and evidence. Request changes when the result needs another pass.

  3. Make the next action explicit.

    Accept the reviewed result, prepare delivery separately, and use your release tools when ready.

Bring the tools you already use.

Browse and import local skills and commands. Define MCP connections and choose the tools attached to managed runs.

Notion and Linear connector implementations are present. Real account sign-in, renewal and client attachment are still part of acceptance testing.

Skills and commandsDiscover, preview, import, then choose Use.
Local library
Local MCP toolsDefine a connection, test it, select its tools.
Connections
Notion and LinearHosted connector acceptance remains open.
In validation

What’s here. What’s next.

Updated 1 November 2026

Implemented in the development branch

  • Named projects, files and isolated tasks
  • Codex and Claude Code conversations and bounded teams
  • Git views, saved check commands and owner review
  • Local skills, commands and MCP connection definitions
  • Delivery records, one-shot endpoint checks and follow-up queues

Acceptance work still open

  • The complete local project acceptance journey
  • New reviewer-execution receipt work
  • Real Notion and Linear account journeys
  • Native desktop and signed distribution verification
  • Fresh full-platform gates on the final combined revision

Implementation is not release acceptance. Deployment, rollback and continuous production monitoring require external tooling. This page does not announce a production-ready release.

Workbench capabilitiesWorkflow illustration

A clearer place to build with agents.

Explore the workflow and the work still ahead.

View development status