Your AI software factory

Tickets in.
Pull requests out.

Aictiq is the project board your coding agents can actually work from. Write a ticket, click Hand to agent, and Claude Code, Codex, OpenCode, Cursor or Copilot picks it up on your machine and sends back a pull request. No more copy-pasting tickets into a terminal.

Start free 30-day evaluation Self-host it, it's free

No card. Open source (AGPL-3.0). Your code never leaves your machine.

Claude Code
Codex
OpenCode
Cursor
GitHub Copilot

Your system asks for less motion, so this page is standing still.

Ready TODO3

ACME-123

Hand to agent

Unassigned

ACME-131

Rate limit the CSV export endpoint

Subtasks 0/0B builder

ACME-128

CSV import skips rows with an empty last column

Subtasks 0/0 Unassigned

Active DOING2

ACME-119

Slack alert when a payment fails twice

running

Subtasks 0/0B builder

ACME-117

Upgrade Postgres to 17

Subtasks 0/0A Ana

In Review DOING2

ACME-110

Dark mode for invoice PDFs

#139 · +212 −40

Subtasks 0/0R reviewer

ACME-108

Rewrite the onboarding checklist copy

Subtasks 0/0M Marko

Done DONE41

ACME-102

Retry outgoing webhooks with backoff

Subtasks 0/0B builder

ACME-99

Keyboard shortcut for the command palette

Subtasks 0/0A Ana

You, in 2026

Be honest. This is your workflow.

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

You're not a developer anymore. You're a clipboard with opinions.

Aictiq takes steps 1 to 6. You keep the opinions.

tracker.example.com/browse/ACME-123

ACME-123

CtrlC

tab 1 · claude

> Login redirect forgets the query string.
and run the tests please
✻ Thinking…

tab 2 · codex

> ACME-131 rate limit the export
reading 214 files…

tab 3 · ???

refactoring src/auth/** (all of it)
nobody asked for this

tab 1 · claude · 50 min ago

? Should I also fix the logout
redirect? (y/n) ▍

tab 2 · scrollback

line 1,847 of 2,000
...did it pass? keep scrolling

Your PM · 17:52

so what did the AI actually do today?

ACME-123

succeeded#142 · +86 −12

B builder

1Write the ticket (or don't, really)

Write it like you'd say it.

"Login redirect forgets the query string." That's a ticket. Paste a screenshot, drop a file, done.

Want it implementation-ready? Click Refine ticket. An agent reads the ticket, the screenshots and the relevant bits of your code, then rewrites it with acceptance criteria. If it can't guess something, it asks. You answer in the ticket, not in a chat window you'll lose.

Templates for Bug and User story
#ACME-123 links with autocomplete
Word, Excel, PDF and image attachments

ACME-123 · Bug · Ready

Save & close

Harness

Claude Code

Runner

Any free runner

Refine ticket

Description

Before: Login redirect forgets the query string.

User story

As a signed-out user who opens /invoices?status=overdue, I land on that exact page after logging in.

Acceptance criteria

• The full path and query survive the login round trip.
• Only same-origin targets are allowed (no open redirect).
• Works with Google and GitHub sign-in too.
• A test covers ?next= with nested params.

builder asked · question 1 of 1

Which browsers do we need to support?

You answered

Evergreen ones. Safari 17 too.

2Hand it over

One button. Seriously, one.

Hand to agent. Pick the playbook (your team's instructions, versioned in the wiki), pick the agent, optionally pick the machine. Or Start later: we prefill six hours from now, because we know what you're going to do tonight. Sleep.

Prefer automation? Add a rule: "when a ticket with label agent-ok enters Ready, run Implement as builder". The board becomes the queue.

Run now or schedule
Rules by state and label
aictiq run start ACME-123
MCP: start_run

3Your runner picks it up

It runs on your machine. Not ours.

The runner is one command on your laptop, a VPS or a CI box.

It only makes outbound HTTPS calls. No open ports, no VPN, no "please whitelist our IP range". It asks for work, we answer. Your repository, your harness subscription, your rules. Aictiq dispatches and records. It never holds your code.

$ npm install -g @aictiq/cli
$ aictiq runner register --url https://app.aictiq.com --token jrn_…
$ aictiq runner start

Linux, macOS, Windows
Runs as a service (systemd, launchd, Task Scheduler)
Updates itself between runs
1 to 16 runs in parallel per machine

One run, start to finish.

Keep scrolling. The ticket does the travelling.

queuedYou click Hand to agent. The ticket waits in Ready with a run queued.
assignedYour runner asks for work over outbound HTTPS and gets this run. Nothing calls in.
runningThe agent works in a fresh worktree on your machine. The log streams back as it happens.
runningIt commits to a branch and opens a pull request with your git login.
succeededThe ticket moves itself to In Review, with the pull request attached.

Aictiq

Ready

Active

In Review

Done

outbound HTTPS only. no inbound ports.

your runner

git push

run · ACME-123 · live log

✓Read the ticket✓Branch✓Tests

→ mcp__aictiq__get_item {"key":"ACME-123"}

← {"title":"Login redirect forgets the query string"}

→ mcp__aictiq__claim_item {"key":"ACME-123"}

← {"claimed":true,"by":"builder"}

→ git switch -c acme-123-keep-query-on-redirect

→ Read src/auth/redirect.ts

→ Edit src/auth/redirect.ts +14 −3

→ mcp__aictiq__update_comment progress: fix in place

→ pnpm test auth

← ✓ 48 passed (2.1s)

→ pnpm lint && pnpm typecheck

← no problems

→ git commit -m "ACME-123 Keep the query string…"

→ gh pr create --base main

← https://github.com/acme/web/pull/142

→ mcp__aictiq__link_item {"key":"ACME-123"}

✓ Work complete: PR #142 is open, ready for review.

ACME-123queuedassignedrunningsucceeded

Hand to agentBbuilder

#142 · +86 −12

4The agent works (and you can watch)

Watch it think. Or don't. It's fine either way.

The runner makes a fresh worktree, hands the harness a token that only lives as long as this run, and the agent gets to work. It reads the ticket over MCP, keeps one progress comment updated (not 40 of them), runs your tests and pushes a branch.

The live log streams into Aictiq as it happens. Close the tab. Your phone will tell you when it's done, via email, Slack, Discord or Telegram.

Live log
Cost and tokens per run
Time limit per playbook
Auto-retry on rate limits and overloads

RunningSucceededACME-123ClaudeBbuilder

Playbook: Implement
Runner: build-box
Duration: 5 min
Cost: $1.41 · 18.2k out
Exit: 0
Limit: 60 min
Branch: acme-123-keep-query-on-redirect

✓Read the ticket✓Branch✓Tests✓Pull request

Log 148 lines ● live

→Bash{"command":"git status --short"}

←M src/auth/redirect.ts

←M src/auth/redirect.test.ts

→Bash{"command":"pnpm test auth --reporter=dot"}

←················································

←✓ 48 passed (2.1s)

→mcp__aictiq__update_comment{"key":"ACME-123","bodyMarkdown":"Progress (builder): tests pass, opening PR"}

←[{"type":"text","text":"{\"unchanged\":false}"}]

→Bash{"command":"git commit -qm \"ACME-123 Keep the query string on the login redirect\""}

→Bash{"command":"git push -u origin acme-123-keep-query-on-redirect"}

→Bash{"command":"gh pr create --base main --title \"ACME-123 Keep the query string…\""}

←https://github.com/acme/web/pull/142

→mcp__aictiq__link_item{"key":"ACME-123","url":"https://github.com/acme/web/pull/142"}

←[{"type":"text","text":"true"}]

What changed (in src/auth/redirect.ts):

- The login redirect keeps the full path and query string.

- Only same-origin targets are followed. Anything else goes to /.

- New test covers ?next= with nested params.

I didn't move the item; Aictiq does that from this run's outcome.

✓Work complete: PR #142 is open and linked on ACME-123, ready for review.

Run succeeded · ACME-123

builder opened PR #142. Via Telegram.

Active DOING1

ACME-119

Slack alert when a payment fails twice

Subtasks 0/0B builder

In Review DOING3

ACME-123

succeeded#142 · +86 −12

B builder

ACME-110

Dark mode for invoice PDFs

Subtasks 0/0R reviewer

Done DONE41

ACME-102

Retry outgoing webhooks with backoff

Subtasks 0/0B builder

Bbuilder· run outcome · just now

Opened PR #142. Tests, lint and type-check pass. Moved to In Review and released the ticket.

5Pull request, ticket moves itself

The PR shows up. The ticket moves itself.

When the run ends, Aictiq links the pull request, writes one outcome comment, releases the ticket and moves it to the state your playbook says: In Review on success, something else on failure. Nobody drags cards around at 6 pm anymore.

Small project, no PR ceremony? Set the playbook to push directly to the default branch. We won't judge. Your branch protection might.

6You're still the boss

Review it. Steer it. Or let it try again.

Not quite right? Say so in a comment.

Comment @builder keep the query string on the redirect too and the agent picks up the same session, on the same branch, and replies in the thread with what it changed.

Run failed? Pick up where it stopped.

Continue resumes the agent's session where it stopped, with its edits still there. Retry starts clean.

Want to take over by hand?

Copy resume command gives you the exact claude --resume … line (or Codex, OpenCode, Cursor, Copilot) for that checkout.

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

Other tools bolted an AI button onto a tracker. We built the tracker around the agents.

The usual setup compared with Aictiq
Question	The usual setup	Aictiq
Where the agent runs	In a terminal tab you opened and forgot	On a runner you registered, as a service
Who picks the ticket	You, by copy-paste	The agent claims it. One claim per ticket, enforced by the database
Where its progress lives	Scrollback	One progress comment on the ticket, plus the live log
When two agents start at once	Two PRs, both wrong	One claim, one polite refusal
On a rate limit	You notice an hour later	Auto-continue after 1 and 5 minutes
Who did what	"The AI"	A named agent, owned by a named person, in every commit and comment
Whose code, whose machine	Theirs, often	Yours. Always
Which agent	The one the vendor sells	Claude Code, Codex, OpenCode, Cursor, Copilot. Switch per run

It's also just a really good tracker

Not using agents yet? It's still the board you wanted.

Boards, backlog, sprints, epics down to tasks, a wiki, analytics, keyboard shortcuts, a command palette. Fast at 100,000 items. Teams that only track work can ignore the AI bits forever. Nothing nags.

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: 72
Latest ticket: AICTIQ-58
CLI releases: 9
Days since public release: 15

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

AICTIQ-58 Fix CI dependency audits with patched MCP SDKAICTIQ-58 Keep mobile ticket details within the viewportAICTIQ-56 AICTIQ-57 Start scheduled runs early, say why a run waits, retry failed update checksAICTIQ-55 Name the browser tab after the page and projectAICTIQ-54 Add GitHub Copilot CLI as a fifth runner harnessAICTIQ-53 Show #KEY references as links in the item editorsAICTIQ-53 Remove the Edit/Preview toggle from the item descriptionAICTIQ-52 Show the newest comments first on an itemAICTIQ-51 Point run links in emails and chat at the factory run pageAICTIQ-50 Choose runner and harness when starting ticket refinementAICTIQ-48 Add project ticket autocomplete and Markdown reference linksAICTIQ-47 Give native select options readable colors in dark modeAICTIQ-42 Runner self-update from npm with automatic restartAICTIQ-45 Rewrite performance docs to show current numbers onlyAICTIQ-46 Add Cursor CLI as a fourth runner harnessAICTIQ-41 Deliver notifications to Telegram, Slack and DiscordAICTIQ-35 Let users steer an agent's work by mentioning it in commentsAICTIQ-44 Show run statistics on Factory → RunsAICTIQ-43 Show notice when ticket refinement is not configuredAICTIQ-25 Inline quick edits and duplicate on Items and Backlog listsAICTIQ-39 Copy a terminal command to resume an agent run's session on its runnerAICTIQ-37 Schedule a run for later from Hand to agentAICTIQ-34 Add emoji reactions and author notifications to commentsAICTIQ-38 Keep ticket refinement on existing ticket detailsAICTIQ-36 Show the unread notification count on the sidebar InboxAICTIQ-58 Fix CI dependency audits with patched MCP SDKAICTIQ-58 Keep mobile ticket details within the viewportAICTIQ-56 AICTIQ-57 Start scheduled runs early, say why a run waits, retry failed update checksAICTIQ-55 Name the browser tab after the page and projectAICTIQ-54 Add GitHub Copilot CLI as a fifth runner harnessAICTIQ-53 Show #KEY references as links in the item editorsAICTIQ-53 Remove the Edit/Preview toggle from the item descriptionAICTIQ-52 Show the newest comments first on an itemAICTIQ-51 Point run links in emails and chat at the factory run pageAICTIQ-50 Choose runner and harness when starting ticket refinementAICTIQ-48 Add project ticket autocomplete and Markdown reference linksAICTIQ-47 Give native select options readable colors in dark modeAICTIQ-42 Runner self-update from npm with automatic restartAICTIQ-45 Rewrite performance docs to show current numbers onlyAICTIQ-46 Add Cursor CLI as a fourth runner harnessAICTIQ-41 Deliver notifications to Telegram, Slack and DiscordAICTIQ-35 Let users steer an agent's work by mentioning it in commentsAICTIQ-44 Show run statistics on Factory → RunsAICTIQ-43 Show notice when ticket refinement is not configuredAICTIQ-25 Inline quick edits and duplicate on Items and Backlog listsAICTIQ-39 Copy a terminal command to resume an agent run's session on its runnerAICTIQ-37 Schedule a run for later from Hand to agentAICTIQ-34 Add emoji reactions and author notifications to commentsAICTIQ-38 Keep ticket refinement on existing ticket detailsAICTIQ-36 Show the unread notification count on the sidebar Inbox

AICTIQ-27 Continue failed agent runs from where they stoppedAICTIQ-33 Hide ticket refinement from stakeholdersAICTIQ-32 Make the refine ticket button prominent and compactAICTIQ-30 Show the active project in page breadcrumbsAICTIQ-31 Fix notification popup, destinations and unread stateAICTIQ-28 Give refine runs a research budgetAICTIQ-26 Apply item templates during ticket creation and preserve template editsAICTIQ-23 Refine tickets from a short descriptionAICTIQ-21 Add shareable links for itemsAICTIQ-20 Show pointer cursors for active clickable elementsAICTIQ-19 Preserve the current view when switching projectsAICTIQ-17 Show items created outside a team on Backlog and BoardAICTIQ-15 Enrich watched workflow emails with item and run detailsAICTIQ-14 Allow Word, Excel and related document attachmentsAICTIQ-13 Connect sidebar Agents to organization managementAICTIQ-9 Self-checking Factory setup guide for runners and projectsAICTIQ-6 Fail direct runs fast when the local checkout has no origin remoteAICTIQ-6 Allow playbooks to push directly to the default branchAICTIQ-7 Open notification emails on the project board with the ticket modalAICTIQ-8 Say so when a save goes through, and only offer Save while there is something to saveAICTIQ-3 Hand out the install-as-service commands with the runner secretAICTIQ-1 Stop the run log flickering mid-scroll on scaled displaysAICTIQ-5 Add an eye to reveal what was typed into a password fieldAICTIQ-1 Stop the live run log flickering while it followsAICTIQ-27 Continue failed agent runs from where they stoppedAICTIQ-33 Hide ticket refinement from stakeholdersAICTIQ-32 Make the refine ticket button prominent and compactAICTIQ-30 Show the active project in page breadcrumbsAICTIQ-31 Fix notification popup, destinations and unread stateAICTIQ-28 Give refine runs a research budgetAICTIQ-26 Apply item templates during ticket creation and preserve template editsAICTIQ-23 Refine tickets from a short descriptionAICTIQ-21 Add shareable links for itemsAICTIQ-20 Show pointer cursors for active clickable elementsAICTIQ-19 Preserve the current view when switching projectsAICTIQ-17 Show items created outside a team on Backlog and BoardAICTIQ-15 Enrich watched workflow emails with item and run detailsAICTIQ-14 Allow Word, Excel and related document attachmentsAICTIQ-13 Connect sidebar Agents to organization managementAICTIQ-9 Self-checking Factory setup guide for runners and projectsAICTIQ-6 Fail direct runs fast when the local checkout has no origin remoteAICTIQ-6 Allow playbooks to push directly to the default branchAICTIQ-7 Open notification emails on the project board with the ticket modalAICTIQ-8 Say so when a save goes through, and only offer Save while there is something to saveAICTIQ-3 Hand out the install-as-service commands with the runner secretAICTIQ-1 Stop the run log flickering mid-scroll on scaled displaysAICTIQ-5 Add an eye to reveal what was typed into a password fieldAICTIQ-1 Stop the live run log flickering while it follows

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.

Start free 30-day evaluation docker compose up

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

Tickets in.Pull requests out.

Be honest. This is your workflow.

Write it like you'd say it.

One button. Seriously, one.

It runs on your machine. Not ours.

One run, start to finish.

Watch it think. Or don't. It's fine either way.

The PR shows up. The ticket moves itself.

Review it. Steer it. Or let it try again.

Not quite right? Say so in a comment.

Run failed? Pick up where it stopped.

Want to take over by hand?

Other tools bolted an AI button onto a tracker. We built the tracker around the agents.

Not using agents yet? It's still the board you wanted.

Aictiq is built with Aictiq.

Questions, answered

Your next ticket could be a PR by tomorrow morning.

Tickets in.
Pull requests out.