Bring the relevant context.
Use project evidence and supported memory sources you explicitly provide or configure.
Open-source tools for AI-assisted engineering
Plan a change, review a document, repair files, run tests or return to saved work with your assistant in Codex or Claude Code. Harness keeps the output and check results so you can see what happened and decide what to do next.
Choose your next taskThe lead project · Attune Harness
Choose a useful goal, agree on the work and checks, and review the result.
Start with the problem you want to solve. Your assistant helps prepare the work, presents what needs your review and uses Harness to carry out the steps you authorize.
Develop the goal, affected files, tasks and checks with your assistant before implementation.
Give configured agents the accepted tasks, then inspect their work against the agreed checks.
Compare a document with your criteria and supporting sources. Inspect findings and unresolved questions.
Check a proposed repair against a test fixed before the repair begins.
Preview the tests selected for a code change, then inspect their output and results.
Read the saved decisions and results before choosing the next action with your assistant.
See what passed, what failed and what needs another look. Harness keeps the output and check results together so you can review the work before deciding what to do next.
Accepting intent and authorizing execution are separate decisions. Paid calls need their own authorization.
A passing check establishes what it tested. It does not guarantee every output is correct.
Published: Attune Harness 1.6.0. Get started · Published package
Harness 1.7.0 is in preparation. Use the published release for installation. Explore the 1.7.0 preparation guide.
Browser forms guide intake and intent approval. Each workflow retains its own execution permissions and checks.
In one exporter comparison, command-line checks found three defects that direct serializer checks had missed.
The result applies to that example. General model reliability needs separate assessment.
Read the comparison and its limits
A passing check establishes what it tested. Native planning and building remain experimental. Claude Code and Codex have documented setup paths; Antigravity integration is unverified in this review. Native MCP panel delivery remains unverified. Review the qualification guide.
Context and useful next steps
A bounded workflow with your agent: bring relevant context, review possible follow-up work, and decide what is worth pursuing.
Use project evidence and supported memory sources you explicitly provide or configure.
Retain an opportunity-review checkpoint with its goal, progress, evidence and unfinished review.
Assess the proposed benefit and uncertainty. A saved suggestion grants no execution authority.
Scoped recall and saved review checkpoints are supported. Automatic access to all chat history is not implied; the richer opportunity-ranking and selection journey remains proposed. Review the current boundary.
Help shape what comes next
Proposed paths for contributors, potential pilot customers and open-source sponsors.
Start by building together
Help improve specification development, planning, build and repair workflows, and independent checks. Bring a reproducible problem, a design question or a contribution.
A starting conversation could identify a useful contribution, its scope and how to check it. Documentation, usability and real workflow evidence matter alongside code.
Explore a possible customer engagement
Explore one workflow guided by a specification, from a clear goal and agreed scope to evidence you can review. Define what a possible pilot would need to demonstrate.
Possible starting points include developing a specification with explicit acceptance criteria, reviewing a generated document against project evidence, or checking a scoped agent-assisted change. Scope, responsibilities and commercial terms would need separate agreement.
Support work in the open
Discuss support for an open-source milestone in specification workflows, independent checks or usable documentation, with its scope, evidence and limits stated up front.
A discussion could connect support with an agreed milestone in usability, documentation or verification. Milestones and any sponsorship terms remain to be defined.
Supporting tools and earlier work
Harness is the current focus. Supporting libraries and earlier project references remain available.
Earlier project · Memory and workflows
Reference for the earlier project’s memory and workflow tools. Existing code and documentation remain available.
Attune AI referenceStructured questions and decisions
Make questions and choices easier to review, with structured answers validated on return.
Explore Attune FormsRetrieval with citations
Retrieve relevant project sources and return citation records for the next step.
Explore Attune RAGBuilt by Patrick Roebuck
The direction is practical: make agent work easier to authorize, inspect and evaluate. The next step is to find useful problems to work on together.