Resume without a briefing
A new person or coding agent can pick up the architecture from the repository instead of relying on chat history.
Architecture context for software teams
Stop explaining your system from scratch.
YarraMate gives your team and coding agents one shared map of how your software is meant to work—checked, versioned, and kept in Git.
Open source · runs locally · no telemetry · pre-1.0
The repository becomes the handover
Today’s sessionrecords decisions and open questions
.yarramate/checked architecture in Git
The next sessionresumes from the same architecture map
People, Codex, Claude, or another harness: the context lives with the code, not in one chat.
Why it exists
Your code shows what exists. It rarely explains what you intended.
That missing context gets repeated in prompts, lost between sessions, and buried in documents that quietly drift. YarraMate keeps the important decisions beside the code and checks them as the repository changes.
Catch stale assumptions
Checks and evidence make disagreements visible instead of letting architecture notes drift silently.
Keep your existing tools
YarraMate is a local CLI and plain files in Git. It works across editors, agents, and model providers.
How it works
Start small. Grow the map as decisions are made.
You do not need to document the whole system upfront. YarraMate asks for the next useful decision and keeps the result valid.
Add YarraMate to the repository
Initialize a checked architecture workspace beside your code.
yarramate init .
Answer one useful question
Your agent or team records intent, boundaries, ownership, and open decisions as work happens.
yarramate design
Share and verify the context
Anyone can read a focused explanation, while CI can catch broken references and drift.
yarramate ask
A real handover
One agent stopped. Another resumed cold.
A Claude Code session ended without transferring its conversation. A Codex session resumed the same architecture work from the repository, answered 63 open questions, and exposed two product defects.
Shared conversationnone
Questions answered after handover63
Product defects found2
Human direction needed1 sentence
Is it for you?
Useful when context must survive a handover.
YarraMate adds maintenance work. It earns that cost when architecture context needs to outlive one person, session, or tool.
A good fit when
- Several people or coding agents work in the same repository.
- Important design intent is not obvious from the code.
- You need architecture changes to be reviewable in Git.
Probably unnecessary when
- The repository is small and owned by one person.
- A short, current design document already does the job.
- You do not need checked or resumable architecture context.
Give the next session a map, not another briefing.
Install the CLI, initialize your repository, and let YarraMate identify the first useful architecture question.
npm install --global yarramate
yarramate init .
yarramate init .