Fellowship

Your AI Agents Remember Everything.

Persistent memory, auto-generated specs, and code review for coding agents.
Day 30 agents know what they learned on day 1.

$ npm install -g fellowship-cli

See what makes it different ↓

The problem with AI coding agents

Every tool gives you an agent.
None of them give it a brain.

Amnesia

Every run starts from zero. Your agent makes the same mistakes it made yesterday.

No plan

You say "add auth" and pray. No spec, no criteria, no way to verify the output.

No review

Code goes straight to your branch. No second pair of eyes. No quality gate.

What makes Fellowship different

Agents that learn.

Fellowship stores learnings, gotchas, and architecture decisions. Every run builds on the last.

Day 1

$ fellowship run "add API endpoint"

spec generated

writing code...

done

learned → "Use bcrypt rounds ≥ 12"

learned → "Validate JWT server-side"

memory: 2 learnings saved

Day 30

$ fellowship run "add payment system"

spec generated with 47 learnings

retrieved → "Always use decimal for money"

retrieved → "Validate webhook signatures"

retrieved → "Idempotency keys on all charges"

writing code (already knows your patterns)

zero mistakes. first try.

Same agent. Same codebase. 30 days of accumulated wisdom.

The full pipeline.

From planning to shipping. One CLI.

Spec-First Runs

Every task auto-generates a spec with acceptance criteria from your codebase context. The agent implements against the spec, not vibes.

$ fellowship run "add user roles" --review-spec

  spec: 002-user-roles.md 8 acceptance criteria 3 gotchas applied from memory
review spec before implementation? [Y/n]

Writer-Reviewer

One agent writes, another reviews against the spec. Automated quality gates with human override via --review.

 writer (sonnet) implementing...
  reviewer (opus) checking criteria...
8/8 criteria met
scribe updated CHANGELOG.md
ready to push

Hire Your Team

Build your agent team through conversation. Define roles, models, specialties. Fellowship writes the config.

$ fellowship hire

  what role? backend engineer
which model? claude-sonnet
specialties? APIs, databases, auth
added forge to team.yaml

Auto Documentation

The Scribe agent updates your CHANGELOG, README, and API docs after every run. Documentation that writes itself.

$ fellowship run "add payments" --scribe
...
scribe: updated CHANGELOG.md
  scribe: updated docs/api.md
  scribe: updated README.md
3 docs updated automatically

Simple commands. Powerful results.

Everything from setup to shipping.

fellowship --help

fellowship init Set up a new project

fellowship adopt Add Fellowship to an existing repo

fellowship hire Build your agent team interactively

fellowship run "task" Spec → write → review → done

fellowship run "task" --review Human-in-the-loop diff approval

fellowship spec "task" Generate spec without implementing

fellowship search "query" Search project learnings and gotchas

fellowship scribe Auto-generate docs from current code

fellowship status Dashboard of runs, learnings, agents

Stop prompting.
Start building.

One install. Zero config. Agents that actually remember.

$ npm install -g fellowship-cli

Works with

Claude Code

Codex

Ollama

Any CLI-based coding agent. Cloud or local.