Aglio

AI-FIRST PROJECT BOARD · FIG. 1

Plan a card. Approve the spec. Ship the PR.

Aglio turns rough tickets into reviewed specs, then hands them to an agent that works in its own container, asks typed questions, and comes back with a pull request and proof it works. Humans still merge.

Open the boardSign in

01 — PROCESS

How a card moves

  1. 01

    Draft

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

  2. 02

    Approve

    Only accepted card content reaches the builder. You approve the spec before any code is written.

  3. 03

    Build

    One container per run, one git worktree per repo. The agent asks typed questions and resumes the same session.

  4. 04

    Review

    Every run returns a PR, a work log and verification evidence. Feedback resumes the agent; you merge.

02 — WORKSHOP

Built like a workshop, not a demo

Planning chat with attachments

Rough tickets become reviewed specs, and images or files stay in the planning thread where they were discussed.

Isolated containers

Every run gets its own container and a worktree per repo; the agent never receives the host docker socket.

Typed questions, same session

When the agent needs a decision it asks a typed question, suspends, then resumes the exact same session.

Mandatory verification evidence

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

Separate reviewer agent

A different agent reviews the pull request, and review feedback moves the card back to Doing.

Spend caps you control

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