Built with Aictiq
We don't just sell the factory. We work in it.
Aictiq's own backlog lives in Aictiq. Tickets get refined by an agent, handed to an agent on our runner, and come back as pull requests a human reviews and merges. Here's what that looked like since the public release.
- Merged pull requests
- 72
- Latest ticket
- AICTIQ-58
- CLI releases
- 9
- Days since public release
- 15
From the GitHub API at build time, 2026-10-07. Public release 2026-09-22.
A real ticket's journey
AICTIQ-21, from one line to merged.
Picked because it's ordinary. That's the point: this is what a normal Tuesday looks like.
The ticket
UI - Add shareable links for tickets
A one-line story on the board, like any other.
Written out
User story, requirements, acceptance criteria
"As a user, I want to copy and share a direct link to a ticket." Six requirements and six acceptance criteria, in the ticket where the agent reads them.
The run
Claude implement on hetzner-vps
Succeeded in 5 minutes. Cost $1.41, 2.5m tokens in, 18.2k out. Exit 0.
The pull request
AICTIQ-21 Add shareable links for items
Copy link button, hover text on the copy panel, and an unrequested fix: signed-out visitors on a shared link no longer see "Loading item…" forever.
Review and merge
A human clicked merge
The agent tested it against a local stack as an admin, a project member and a non-member before handing it over. Merge stayed a human button.
The commit log as proof.
The latest merged pull requests, each named after the ticket it came from. 49 of them so far.
- #91AICTIQ-58 Fix CI dependency audits with patched MCP SDK10-07
- #90AICTIQ-58 Keep mobile ticket details within the viewport10-07
- #89AICTIQ-56 AICTIQ-57 Start scheduled runs early, say why a run waits, retry failed update checks10-06
- #88AICTIQ-55 Name the browser tab after the page and project10-06
- #87AICTIQ-54 Add GitHub Copilot CLI as a fifth runner harness10-06
- #85AICTIQ-53 Show #KEY references as links in the item editors10-06
- #84AICTIQ-53 Remove the Edit/Preview toggle from the item description10-06
- #83AICTIQ-52 Show the newest comments first on an item10-06
What we learned.
Short tickets, then refine.
Most tickets start as one line. Refinement turns them into something an agent can finish, and asks when it can't guess.
The playbook does the heavy lifting.
Test commands, house style and the things not to touch live in the playbook, not in every ticket. Fix it once, every run gets better.
Merge stays human.
Agents test their own work and say what they changed. A person still reads the diff and clicks merge. We haven't wanted it any other way.
Ship your project the same way.
No card, no automatic charge. Or self-host everything for free, forever.