Your agents code on evidence —
three layers deep.
One shared repository of everything your team and its agents know — piped back into every spec, review, and PR so the loop actually closes.
Your agent sessions
Every former agent session, skill, and PR review — pulled in automatically, so your agents already learn from how your team actually codes.
Company evidence
Connect BuildBetter and bring in your calls, Slack, docs, and knowledge base — the decisions and conventions behind the code.
Customer context
BuildBetter also brings your customers — support tickets, CRM, complaints, and feature requests — so agents build what was actually asked for.
Stop paying twice
for the same context.
Every session — chat, file edits, tool calls — is saved and shared across your whole team. Check out an old branch and pull up the chat that produced it. Resume a teammate’s session on your machine. No agent ever pays tokens to rediscover what someone already figured out.
- → Sessions synced across repo, branch, PR, commit, and teammate
- → Resume any teammate’s session with one command
- → Switch Claude Code → Codex mid-task, same memory
The same question.
A radically different answer.
Same agent, same PR, same teammate’s work. The difference is whether it can pull the session that produced the code — or has to burn tokens re-deriving it from scratch.
• Goal: ingest LLM chat history as a new signal source
• Decision: reused conversation as a placeholder — wants to migrate to agent_logs
• Open Q for Nikhil: “should agent_logs be its own model? need your call before I split it.”
conversation table.agent_logs. Pulling project history.• Mar ’26 · spencer scoped initial schema (PR #3308)
• Apr ’26 · maya denormalized for streaming reports “to keep queries under 50ms” (PR #408)
• Aug ’26 · daniel added session_type column (PR #1547)
session_type from Daniel’s August change. Draft /bb-specify for the migration?/bb-plan and /bb-tasks queued the migration.session_type index convention 3× this quarter. Opened a weekly skill PR so your agents catch it next time.Every job is cheaper with the context.
Onboarding, debugging, scoping, reviewing — the same question costs a fraction of the tokens when your agent can pull the work that came before. Each card shows the skills it leans on.
A ticket in the morning.
A PR by end of day.
A ticket comes in. ZeroShot clusters it with the other customers who hit the same thing, /bb-specify pulls those quotes into a spec, /bb-review checks your conventions, and the PR ships.
A customer ticket, end-to-end. Same day.
Export CSV failing for orgs > 10k rows
+ 7 prior tickets · Enterprise · High severity
Spec drafted with 8 customer quotes
passes · PR #2089 merged
Loop closed.
Every stage of the loop — and the skills that run it.
From capturing the work to shipping the PR to learning from it — the whole thing runs inside the CLI, and feeds back on itself so the library compounds.
- 1Capture
Every session, commit, steering event, file edit, and tool call — synced into one shared repo across your whole team.
- 2Scope
/bb-specify/bb-clarify/bb-constitutionTurn customer signals into a spec, resolve the unknowns before you build, and encode your team’s principles.
- 3Plan
/bb-plan/bb-tasks/bb-analyzeBreak the spec into a build plan and a dependency-ordered task list — checked for cross-artifact consistency.
- 4Build
/bb-implementExecute the plan task by task — in whichever agent you’re already using, with the full context loaded.
- 5Verify
/bb-review/trust-but-verify/generate-tests/bb-checklistReview against your conventions, walk the UI like a real user, generate tests, and run the pre-merge checklist.
- 6Ship
The PR merges. The customers who reported it hear back — same day, not next quarter.
- 7Learn
weekly skill PRSignals run over the sessions, identify the patterns your team keeps repeating, and open a weekly PR with new and sharper skills.
Agent sessions are
the new call recording.
Every chat your team has with an agent is company knowledge — prompts, decisions, conventions — that’s lost the moment the window closes. ZeroShot captures it as a first-class data type.
The prompts your team already wrote — pulled out of chat sessions, shared, reused.
Signals run over every session — decisions, blockers, and conventions, structured.
Knowledge docs your agents wrote — yours to view, edit, and share. Delete ZeroShot, lose it all.
One platform behind the evidence.
Out of the box, ZeroShot grounds every agent in your own sessions, skills, and reviews. Connect BuildBetter.ai — a customer intelligence platform built for agents — and that evidence goes all the way to your customers: the whole stack.
Prototyping
Snapshot your web app and spin up 10 variants for the price of one build — then test them against synthetic personas.
Projects
Every call, signal, doc, and decision for a project organized in one place.
Knowledge base
Your company's docs, specs, and product knowledge — structured for agents.
Product taxonomy
An auto-labeled, rule-based taxonomy that organizes every signal the way your product is built.
Signal pipeline
The customer & company signal pipeline — 35+ signal types extracted from every conversation.
Call recording
Auto-record and transcribe calls from Zoom, Google Meet, Microsoft Teams, and Gong.
Custom dashboards
Build report dashboards over all your customer and product data.
Integrations
Slack, Zendesk, Intercom, your CRM, and Linear & Jira — connected.
Customer health
A success platform with customer health scores and risk signals.
Close the loop
Follow up with the exact customers behind every feature you ship.
Changelogs & releases
Generate changelogs and release notes from what actually shipped.
“Whether extreme spend pays off comes down to the business value of shipped code — which most companies still can’t measure.”
Get twice as far at twice the speed
on the same budget.
Your agents inherit your team’s skills, your sessions stay shared, and your token spend drops. Join the waitlist — or book a demo to skip the line.