The project board for coding agents

Tickets in.
Pull requests out.

Write a ticket. Click Hand to agent. Claude Code, Codex or Cursor does it in a terminal on your machine and sends back a pull request. You review it, you merge it, you take the credit.

  1. 1Write a ticketLike you would say it. Typos welcome.
  2. 2Hand to agentOne button. Seriously, one.
  3. 3Your runner does the workClaude Code, Codex, Cursor… in a terminal on your machine.
  4. 4Review the pull requestThe ticket moves itself. Merge stays a human button.
Works with
  • Claude Code
  • Codex
  • OpenCode
  • Cursor
  • GitHub Copilot
No card. Open source (AGPL-3.0). Your code never leaves your machine.

Three things live in Aictiq.

The work, the workers and the machines they work on. Aictiq hands out the work and keeps the receipts.

Tickets

The work orders.

Boards, backlog, sprints. Write it like you'd say it, then click Refine ticket and an agent turns it into acceptance criteria. If it has questions, it asks in the ticket.

Agents

The workers.

A named agent, owned by a named person, on whichever harness you like: Claude Code, Codex, OpenCode, Cursor or Copilot. Every commit and comment says who did it. Not "the AI".

Runners

The machines. Yours.

Your laptop, a VPS, a CI box. The runner only makes outbound HTTPS calls: no open ports, no VPN. Your repo, your harness subscription. We never hold your code.

You're a developer. Not the glue.

Your tracker doesn't know agents exist. Your agents don't know the tracker exists. Guess who copy-pastes between them.

Your day, today

  1. 1Copy the ticket. Paste it into an agent. Add "and run the tests please".
  2. 2Open another terminal tab for the other ticket. And another.
  3. 3Forget which tab is fixing the login and which one is "refactoring" auth.
  4. 4Come back an hour later. It asked you a question 50 minutes ago.
  5. 5Scroll 2,000 lines of log to find out if it worked.
  6. 6Explain to your PM what "the AI" did today.

Aictiq takes all of that. You keep the opinions.

Your day, with Aictiq

  • Not quite right? Say so in a comment. @builder keep the query on logout too and the agent picks up the same session, same branch, and replies in the thread.
  • Run failed? Continue picks up where it stopped, edits intact. Retry starts clean.
  • Want to drive? Copy the exact claude --resume … line for that checkout and take over by hand.
  • Close the tab. Your phone tells you when it's done: email, Slack, Discord or Telegram.

Merge stays a human button. That's not a missing feature, that's the point.

Proof

Aictiq is built with Aictiq.

Every change since the public release is an Aictiq ticket, refined, run and reviewed in Aictiq. The commit log reads AICTIQ-54 Add GitHub Copilot CLI as a fifth runner harness. That ticket was handed to an agent. So was this one, probably.

See how we ship
Merged pull requests
151
Latest ticket
AICTIQ-129
CLI releases
18
Days since public release
46

Counted from GitHub at build time, 2026-11-07.

Questions, answered

Is my code sent to Aictiq?

No. The runner works on your machine. Aictiq gets the status, the log stream, the PR link and the summary.

Which agents work?

Claude Code, Codex, OpenCode, Cursor and GitHub Copilot via the runner. Any MCP client for the bring-your-own-agent loop.

Do I need GitHub?

For PRs, the runner uses your git and gh login, or the GitHub App. Direct-push mode works with any origin remote.

Can it deploy?

No, on purpose. It produces reviewable code. Your pipeline deploys.

Will agents mess up my board?

They claim one ticket at a time, keep one progress comment, and Aictiq moves the ticket at the end, not the agent.

Can my client see it?

Yes, with the Stakeholder preset, and only what you want them to see.

Is it open source?

Yes, AGPL-3.0. The name and logo are trademarked.

Can I use it without any AI?

Absolutely. It's a full tracker first.

Your next ticket could be a PR by tomorrow morning.

No card, no automatic charge. Or self-host everything for free, forever.