Imports, owners, tests, and reusable patterns.
Brief your coding agent with a map and a mission.
Map the repo. Bound the task. Check the diff.
Fix APP-218. Reuse existing patterns and prove it.Fix APP-218. Follow our repo rules and prove it.Fix APP-218. Find the existing component first.- MapRelevant code found
Routes, owners, tests, rules, and an existing component
- Mission3 files in scope
A small plan with allowed changes, tests, and stop conditions
- Diff check3 checks passed
The actual change matches repo rules and focused tests pass
- HandoffReady for human review
Sources, test results, and remaining risk are named
01 · Brief the task
Ask as usual. Brief finds what matters.
Brief finds the relevant code and rules, then bounds the task.
Internal shipped code and external references, compared.
Mandatory rules for the files in scope.
Scope, tests, proof, and stop conditions.
Task scopedMake and check the change
02 · Mission, then check
Set the scope. Check the diff.
Brief defines scope, rules, tests, approvals, and stop conditions. A read-only check reviews the diff.
Browse mission starters Read the context engineering field guideSee the six-stage coding agent workflowBrief defines files, rules, tests, approvals, and stop conditions. Your coding agent runs the model with your credential.
- TriggerLinear issue labeled Brief Ready
- ExecuteCodex in Actions
- ProofReviewed pull request
Brief never receives your model credential.
Change checkedKeep what the reviewer teaches
03 · Learn from review
Keep the corrections your team repeats.
Reviewer corrections become source-cited lessons, approved before team reuse.
Browse shared guidance“Auth routes use requireUser().”
Brief saves the correction as a source-cited proposal.
Approve wording and scope
Personal preference cannot weaken mandatory team policy.
Brief includes the approved lesson
The correction returns only when its paths and task match.
PR checks, sources, and review proof
Clear tickets, mission status, and next steps
Focused decisions and replies tied to the coding task
Lesson approvedUse it on the next matching task
04 · Route the work
Spend more only when the task needs it.
Brief recommends a model, reasoning level, and fan-out. You set the ceiling.
Keep a familiar, easy-to-test change fast.
- Fan-out
- One builder
- Proof
- Focused tests
- Quality bar
- Routine
- Cost posture
- Minimize spend
Quality raisedSource still stays local
05 · Review the artifact
Review HTML and Markdown without making it public.
Publish from Claude or Codex as Restricted. Teammates can comment on the page, selected text, or an element; the agent reads the thread and uploads the next version.
Open the artifact review guide- Access
- Restricted by default
- Comments
- Stay attached to what was selected
- Versions
- Use the same link
Artifact reviewedKeep source local
06 · Keep source local
Your repo stays yours.
Files and diffs stay local. Team sync sends derived summaries and receipts; raw source requires opt-in.
scan · context · diff reviewstays local by defaultreceipts · summaries · approved guidanceraw source needs explicit opt-in- The MCP process reads files and git diffs on your machine.
- No raw source leaves by default.
- Every recommendation names its source.
Connect Brief
Install locally. Connect your workspace when you need it.
Run one short command. Brief detects your agents, installs its default instructions, and opens secure browser sign-in with a short-lived browser approval when you connect a workspace.
Runs locally. Your source stays in your repo.
Choose one or more coding agents
npx -y runbrief@latest setup --agent codexPricing
Start with one repo. Add the team when it helps.
Local context and diff review are free. Team memory is optional.
Repo mapping, task context, and local diff review.
Install BriefOwner-approved guidance and review memory across the team.
Create a team workspace