Aglio

THE AI-FIRST PROJECT BOARD FOR 21ST CENTURY COMPANIES

Plan the work. Agree on it. Then ship.

Aglio turns rough ideas into agreed specs, then runs the build asynchronously. You know what is being built, what it costs, and when it lands — before any code is written.

01 — PROCESS

How it works

  1. 01

    Plan

    Write the card, or let the planning agent interview you. Attachments and images stay in the thread.

  2. 02

    Agree

    Only approved content reaches the builder. You sign off on the spec before any code is written.

  3. 03

    Build

    The agent works on its own copy of the codebase, asks when it needs a decision, then picks up exactly where it left off.

  4. 04

    Review

    Every run comes back with a summary, a work log and proof it works. You review and merge.

02 — WORKSHOP

Built like a workshop, not a demo

Start from a rough idea

A half-formed ticket becomes a reviewed spec, with images and files kept in the thread where they were discussed.

Nothing builds unagreed

The builder only sees what you approved, so scope cannot drift in the dark.

Questions, not guesswork

When the agent needs a decision it asks, then resumes the same session. Silence never becomes a wrong assumption.

Proof, not promises

A run cannot call itself done without test, lint and build evidence recorded on the card.

A second pair of eyes

A separate reviewer agent checks the pull request before it reaches you.

Costs you can see

Set a daily cap per project and watch spend on every run.

03 — UNDER THE HOOD

Under the hood

Every build runs in its own container, with a git worktree per repo and no host docker socket. Runs emit a work log and verification evidence, and spend caps are enforced per project per day.

  • Isolated container per run
  • One git worktree per repo
  • Typed questions resume the same session
  • Verification evidence required before done
  • Separate reviewer agent
  • Spend caps per project per day