Trusted context for AI coding
Start every fresh AI coding task with the right context.
Gobb keeps project decisions, constraints, evidence, and handoffs readable and inspectable — so people and AI can continue work across tasks, tools, and repositories.
01 — CONTINUITY
Chat ends. Project context should not.
A new task should not depend on reconstructing decisions from a previous chat. Keep durable context in the repository where the next person or AI can inspect it.
02 — Illustrative example
Task A → repository context → Task B
Existing clients must continue to parse the response.
The existing-client compatibility test passes for this illustrative change.
Should the follow-up add the new response field for newer clients?
Task B reads the accepted compatibility decision and test evidence before making the follow-up change.
03 — GOBB
One workflow, four connected parts.
Method, CLI, agent integrations, and Hub carry the same inspectable context from one task to the next.
Method
Treat current repository context as the starting point for each bounded task.
See the method →CLI
Start and finish managed work from the prepared work repository.
Use the CLI workflow →Agent integrations
Let a new AI task read the current repository context before it continues the work.
Resume with current context →Gobb Hub
Review shared context, evidence, and proposals while keeping acceptance a separate action.
Review the team workflow →04 — EVIDENCE
Keep the work inspectable.
Keep context in readable files, use version history and evidence links to inspect how it changed, and distinguish accepted context from proposed changes. These records make work inspectable; they do not guarantee that a change is correct.
Readable files
Keep decisions, constraints, and handoffs beside the work.
Version history
Inspect how repository context changed over time.
Evidence links
Keep supporting tests and findings connected to the decision.
Accepted vs proposed
Treat current accepted context and candidate changes as distinct states.
05 — TEAM
Extend the workflow to team review in Hub.
Engineering leads can inspect a proposal, diff, reasoning, and evidence in Hub, record approval, accept the context as a separate action, and hand the accepted result to a colleague.
Explore Gobb HubStart locally, then bring the team into the same context workflow.
Use the public CLI Beta or the organizer-assisted source-build workflow in an existing prepared repository. Use the Usage guide for the complete steps or Hub for team review.
Start with an existing prepared repository. Team access uses an organizer-provided organization and Project.