Skip to main content

Open-source tools for AI-assisted engineering

Delegate with clear scope.
Keep the evidence.

Work with your agent to develop a specification, plan a change, and review build, repair and test results. Harness keeps the agreed scope and task evidence available so you can decide what happens next.

Collaborate

Discuss a pilotSponsor open-source milestones

Attune Harness

A task you can inspect.

  1. Agree the scopeGoal, limits and acceptance criteria
  2. Authorize the workPermitted actions and recorded output
  3. Check the resultIndependent checks, outcome and errors
Illustrative workflow. A real receipt records what ran and what the checks established.

The lead project · Attune Harness

Make the work inspectable.

Develop the specification, agree with the scope, and inspect the evidence as work progresses.

Complex work starts with a specification you can review: requirements, constraints and acceptance criteria. Harness supports the next steps with explicit scope, retained decisions and checks you can inspect.

Develop a reviewable specification.

Work with your agent to record requirements, constraints and acceptance criteria before implementation.

Agree to the plan and scope.

Inspect the allowed files, proposed work and acceptance checkpoint before authorizing execution.

Build and repair within limits.

Use scoped workflows with permitted files and declared verification checks alongside your agents.

Review independently against evidence.

Assign a separate reviewer to assess a document against project sources. Keep unsupported claims and uncertainty visible.

Test the change and keep the results.

Run checks on captured changes. Inspect what ran, what passed and what failed before deciding the next step.

Keep decisions and continue.

Inspect saved task state and recover context from supported, configured sources before resuming work.

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.

Authorization has limits.

Accepting intent and authorizing execution are separate decisions. Paid calls need their own authorization.

Evidence has limits too.

A passing check establishes what it tested. It does not guarantee every output is correct.

Published: Attune Harness 1.3.0. Package and release guide

Browser forms guide intake and intent approval. Each workflow retains its own execution permissions and checks.

Read the evidence and limits

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

Find the next opportunity in work you already have.

A bounded workflow with your agent: bring relevant context, review possible follow-up work, and decide what is worth pursuing.

Bring the relevant context.

Use project evidence and supported memory sources you explicitly provide or configure.

Keep the next step visible.

Retain an opportunity-review checkpoint with its goal, progress, evidence and unfinished review.

Choose what to pursue.

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

Three ways to take part.

Proposed paths for contributors, potential pilot customers and open-source sponsors.

Start by building together

Collaborate

Help improve specification development, planning, build and repair workflows, and independent checks. Bring a reproducible problem, a design question or a contribution.

Explore collaboration

A starting conversation could identify a useful contribution, its scope and how to check it. Documentation, usability and real workflow evidence matter alongside code.

Start a conversation

Explore a possible customer engagement

Discuss a pilot

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.

Explore a pilot

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.

Start a conversation

Supporting tools and earlier work

Project references.

Harness is the current focus. Supporting libraries and earlier project references remain available.

Earlier project · Memory and workflows

Attune AI

v16.4.0

Reference for the earlier project’s memory and workflow tools. Existing code and documentation remain available.

Attune AI reference

Structured questions and decisions

Attune Forms

Make questions and choices easier to review, with structured answers validated on return.

Explore Attune Forms

Retrieval with citations

Attune RAG

Retrieve relevant project sources and return citation records for the next step.

Explore Attune RAG

Built by Patrick Roebuck

Developed in the open.

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.