How Attune AI works
Reference for the earlier project’s memory and workflow model. Attune Harness is the current focus; these materials remain available for existing users.
The reliability loop
Five stages describe a way to organize development. Choose checks appropriate to the change and inspect their results. This practice does not enforce every step in every workflow or guarantee correct output.
Specify
Socratic spec engine: requirements, design, and tasks with an approval gate.
Ground
Retrieval supplies project sources and citations for checking an answer.
Build
The agent executes the spec'd tasks — 21 workflows: review, tests, bug prediction, refactor.
Remember
Cross-session memory and a lessons corpus surface what worked before.
Verify
Check selected properties such as imports, flags, links and counts; inspect the results and limits.
What's working underneath
Project memory can support the loop alongside four supporting capabilities, each real and shipped.
Your agent stops starting from zero
Saved findings and a lessons corpus can supply context across sessions. Recall depends on the configured memory integration; check recalled material against current project evidence.
- Local memory storage and workflow data transfer are separate concerns
- Redis and embedding destinations depend on the configured setup
- Recall availability depends on the selected integration
- Git-tracked lessons and handoffs can carry context between agents; check the integration in use.
Forms that improve how you and the AI talk
Attune improves human/AI communication by dynamically using interactive forms: instead of a fixed wall of prose, it renders the right form in response to your prompt whenever a structured turn communicates better than text. A multi-part question becomes one click; a recommendation arrives as weighable cards; a disagreement is shown side-by-side so you overrule it in one tap.
- Intake, decision, and pushback fire at a fork; progress reports status
- Rich on widget surfaces, graceful menu fallback elsewhere
- Answer with one click — or the terse y / go / 1 vocab
Specialist teams, not one prompt
21 workflows run teams of 2–6 Claude subagents to review code, surface vulnerabilities, generate tests, and plan refactors — with cost-tiered model routing.
- Security audit, code review, bug prediction, release prep
- Cheap / capable / premium model routing
- Structured, readable reports
Answers anchored to your code
Keyword and semantic retrieval supply source context and citations for review. Check the retrieved material and resulting answer; a benchmark does not establish accuracy for every task.
- Powered by attune-rag — built in, no extra install
- Citations back to source
- Faithfulness measured, not assumed
Check generated output before use
Check properties such as imports, CLI flags, links and counts against project sources. Inspect which checks ran and what remains unchecked before accepting a change.
- Powered by attune-verify — built in, no extra install
- Verifies docs, code, and generated content
- Closes the loop the spec opened
- Cross-model review and roundtable deliberation — advisory; you decide
The agent asks with structure — go ahead, answer it
Both of these are live renders from the production form pipeline, not mockups. Left: scope an audit — a recommended decision card with tradeoffs, multi-select, a dropdown, a bounded number, free text. Right: a session retro triaged one tap per item. Submit either empty and validation catches you.
Live embed — filling it here goes nowhere; in a session, answers come back validated.
The session retro as a triage form — real items from the session that built this demo, ruled one tap each.
Cross-model review, with you deciding.
The earlier /roundtable integration provides a shared board for discussion with configured model seats. Check each seat's availability, authentication and permissions before use. The advice informs your decision; you choose what to adopt.
Deliberate
Participants can post positions and critiques to a Redis-backed board. Check which reviewers actually participated and which source material they saw. Re-verify handoff context against the current project before continuing work.
You decide
The seats advise; only the chair promotes. You rule on what gets adopted, and the ruling is recorded — a decision that outlives the session.
Receipts, still
For actions you approve, capture the executed result and relevant check evidence. A decision to act is separate from evidence that the action succeeded.
For a second opinion, /cross-review requests an advisory review of a real diff. Check the reviewer's identity, the files included and any omissions. Findings need assessment and appropriate verification before adoption.
Draft the specification, agree the work and inspect the checks.
Use specifications and independent checks to make a change reviewable. Keep their tested scope and limits visible.
Before implementation
- •Write requirements, design and tasks; agree to the plan and scope before implementation
- •Use structured questions to resolve unclear requirements and record the decisions
- •Compare the result with the agreed specification and keep changes in scope visible for review
Before accepting a change
- •Check generated claims against the relevant project sources
- •Choose checks for imports, CLI flags, links, counts and other properties the change depends on
- •Inspect what passed, what failed and what remains unchecked. Passing checks do not guarantee a correct change
Explore Attune Harness
Work from a concrete goal, check the result, and retain the context needed for the next step.