Coding agents that already know your project.
Mate keeps your agent instructions, skills, and tools in a companion repository and wires them into Claude Code or OpenCode every time you launch.
npm install -g @uniqbit/mate$ mate install✓ Core requirements installed$ mate companion link✓ Linked companion acme-companion✓ Installed selected capabilities$ mate claude→ Resolve · Sync · Index · Launch✓ Claude Code started with companion context$
The problem
Your team's AI work is invisible to the business
- Product owners, business analysts, and developers all use AI to shape requirements, plans, and decisions.
- The results stay in private chats, local files, or scattered across code repositories the business side never opens.
- Teams spend extra effort aligning, and it gets harder to trace why something was built.
The idea
One shared source of truth for every role
- A companion repository collects specifications, plans, and decisions in one place that every role can read and contribute to.
- Documentation comes for free: developers following the recommended Mate workflow produce up-to-date specs as a by-product of delivery.
- The business sees what is being built and why, and every AI session starts from the same, current context.
Secret guardrails are on by default: agents are kept away from secret files, and secrets are kept out of indexes and companion artifacts. How the guardrails work →
How it works
Install, link, launch
Three commands from your working repository. After that, every launch prepares the agent the same way.
- 1
Install
mate installInstall the CLI from npm, then verify Mate's core runtime in your working repository.
- 2
Link
mate companion linkPick a registered companion or clone one from Git. Mate installs what the companion selects.
- 3
Launch
mate claudeStart Claude Code or OpenCode with the companion's context already wired in.
- 1Resolve
Find the companion linked to this working repository.
- 2Sync
Copy companion instructions, skills, and capabilities into place.
- 3Index
Refresh enabled code indexes such as TokenSave and Graphify.
- 4Launch
Start Claude Code or OpenCode in the working repository.
Repository model
Two repositories, two jobs
The companion repository holds everything your agents need. Working repositories hold your product. One companion can serve many working repositories, and each keeps its own history.
- Mate configuration (.mate/config/)
- Agent instructions and skills
- Capability-managed files
- OpenSpec changes and specs
- Reports and other agent output
web-appProduct code and tests, plus a local, git-excluded .mate/ link.
api-serviceProduct code and tests, plus a local, git-excluded .mate/ link.
shared-libProduct code and tests, plus a local, git-excluded .mate/ link.
Use cases
What working with Mate looks like
Step-by-step walkthroughs of the core flows.
Your first agent session
Go from a fresh install to a running agent that knows your project in three commands.
Read the walkthrough →One companion, many repositories
Share one set of instructions, skills, and capabilities across several codebases.
Read the walkthrough →Design a team companion
Set the agents, rules, skills, and guardrails your whole team works with.
Read the walkthrough →More walkthroughs soon
Mate already supports more flows than these. Their walkthroughs are still being written.
Capabilities
Optional tools, wired in at launch
Select capabilities per companion. Mate installs them and syncs them into every linked working repository.
Give your agents the context they need.
Install Mate, link a companion, and launch your first session in a few minutes.