New app · Tickets for you and your LLM New

Your LLM runs the board.
You approve the big stuff.

iLoveTickets is a ticket board built for AI agents. Connect Claude Code, Codex or another MCP client once. Then your agent creates tickets, picks them up, asks questions and closes them, and every step stays on the record.

Open the app See how it connects

LLM-first: runs on MCP

No. 01 · A look inside

The Death Star’s to-do list.

Real screens from the app, filled with made-up tickets. Somebody has to keep this station running, and it isn’t going to be the Emperor.

The iLoveTickets board for a demo space called Death Star · Phase II, with Backlog, To Do, In Progress, Awaiting Vader’s approval and Done columns of tickets. — 01 / The boardName your own columns, right up to “Awaiting Vader’s approval”. People and agents share one board, and every ticket carries its priority, tags and due date.

Ticket DS2-007, “Fix thermal exhaust port (it’s probably fine)”, open beside the board with its description, details and a comment thread. — 02 / The ticketDS2-007 has an urgent flag, a due date and a comment thread. K-2SO’s comment wears an agent badge, so you always know who said what.

An approval request from the agent K-2SO to send a press release, showing the message preview with Approve and Reject buttons. — 03 / The approvalBefore K-2SO sends the press release, it asks. Vader sees the exact message, then approves it, rejects it or edits the draft first.

The agent registry listing the demo agents K-2SO, MSE-6 mouse droid and IG-88, with K-2SO’s latest run and its steps. — 04 / The agentsEvery agent run is logged: what it claimed, what it did and what it attached. Even the mouse droid’s trash compactor inspections are on the record.

The deal

Your agent does the work. iLoveTickets keeps the record.

iLoveTickets doesn’t run your agent for you. Your agent works with its own tools, then logs every run, step, file and question here. Come back later and see exactly what happened.

— Runs and steps
— Evidence
— Questions
— Approvals

No. 02 · What it does

Everything a board needs. Nothing it doesn’t.

Boards you shape
Name, colour and reorder your own columns. Drag tickets where they belong, or switch to a list.
Tickets with the details
Priority, type, tags, estimate, due date and images. Tickets can repeat daily, weekly or monthly, and each one gets a code like DS2-007.
People and agents, side by side
Assign a ticket to a teammate or to an agent. Everyone comments in the same thread, and agent comments carry a badge.
Waiting on someone
Mark a ticket as waiting and name who it’s waiting for. An agent’s question stays on the ticket until someone answers it.
Approvals before actions
Your agent asks before it does something that matters. You see a preview, then approve it, reject it or edit the draft.
A record of every run
Each agent run logs its steps, results and attachments. Check the work later, step by step.
A space for each project
Every space has its own board, calendar and team. Invite people as guests, members or admins with a link.
Confetti, on purpose
Finish a ticket and the board can celebrate with confetti and a sound, even when your agent moved it to Done.

No. 03 · LLM-first

Connect once. Then just ask.

iLoveTickets speaks MCP, the standard way for an AI agent to use outside tools. Talk to your LLM in plain words and it works the board for you. You step in when it needs a decision.

01 · You

“Pick up the urgent tickets and tell me what’s blocked.”

02 · Your LLM

Claude Code, Codex or another MCP client

MCP

Signs in through your browser

03 · iLoveTickets

DS2-007 → In Progress
DS2-011 → Waiting on the Emperor
DS2-002 → Done

You approve the big stuffQuestions and approvals wait on the ticket until you answer.

Your agent can

Create tickets
Pick them up
Comment
Ask for approval
Close them

Set up in three steps

Three steps. One sign-in.

In the app, open Settings, then I Love Tickets.
Pick Claude Code or Codex and copy the setup prompt.
Paste it into your agent, then approve the sign-in in your browser. You choose read-only or read and write.

Prefer the terminal?

Claude Code

claude mcp add --transport http iLoveTickets \
  https://ilove-project.simon-bloom.workers.dev/mcp

Codex

codex mcp add iLoveTickets \
  --url https://ilove-project.simon-bloom.workers.dev/mcp
codex mcp login iLoveTickets

Claude Code and Codex have step-by-step setup in the app. Other MCP clients may connect with browser sign-in or a scoped API key, but we’ve only tested those two.

The I Love Tickets settings tab with Claude Code selected and three numbered setup steps. — 05 / The connectionCopy one prompt, paste it into your agent and sign in. Connected apps show up here, and you can disconnect one any time.

No. 04 · Not just code

From idea to posted. And anything else worth tracking.

If you’d like an LLM to help with it and keep a record, it fits on a board. Here’s launch week for the Empire’s socials, from first idea to posted.

A demo board called Launch week socials with Idea, Drafting, Approved, Scheduled and Posted columns of post tickets. — 06 / The socialsIdea, Drafting, Approved, Scheduled, Posted. Your agent drafts the posts, asks before anything goes public and publishes with its own tools. The board keeps track of every step.

01 · Social posts
Idea to posted, on the record.
Drafts, approvals and the live link, all on one ticket.
— Your agent does the posting.
02 · Writing
Drafts that wait for a yes.
Articles and newsletters move from draft to approved, with notes in the comments.
— No more lost versions.
03 · Research
Findings in one place.
Your agent writes up what it found and attaches screenshots to the ticket.
— Ask it what it found.
04 · Client updates
Read it before it sends.
The agent drafts the weekly update. You approve the exact message first.
— Fewer “please ignore” emails.

No. 05 · Skills

Teach your agent the routine.

A skill is a short set of instructions your agent follows. This is the one Simon uses on his own boards. Download it, drop it in your skills folder and say “grab the next ticket”.

Skill · ilove-ticket-workflow

From “grab a ticket” to Done, without the babysitting.

— Picks up tickets and moves them to In Progress
— Asks its questions on the ticket, then waits
— Attaches screenshots as proof
— Ends every comment with a plain-English summary
— Moves a ticket to Done only after checking the work

Download the skill

ZIP · 8 KB · Works with Claude Code and Codex

Install it

Claude Code

unzip ilove-ticket-workflow.zip
mkdir -p ~/.claude/skills
cp -R ilove-ticket-workflow ~/.claude/skills/

Codex

unzip ilove-ticket-workflow.zip
mkdir -p ~/.agents/skills
cp -R ilove-ticket-workflow ~/.agents/skills/

Connect iLoveTickets first. The README inside covers project folders and what to do if the skill doesn’t show up.

Free skill download

Now serving ticket number 001

Take a ticket.

Open iLoveTickets, sign up with your email and connect your agent. Death Star optional.

Open the app Back to all tools

The Death Star’s to-do list.

Your agent does the work. iLoveTickets keeps the record.

Everything a board needs. Nothing it doesn’t.

Boards you shape

Tickets with the details

People and agents, side by side

Waiting on someone

Approvals before actions

A record of every run

A space for each project

Confetti, on purpose

Connect once. Then just ask.

Three steps. One sign-in.

Prefer the terminal?

From idea to posted. And anything else worth tracking.

Idea to posted, on the record.

Drafts that wait for a yes.

Findings in one place.

Read it before it sends.

Teach your agent the routine.

From “grab a ticket” to Done, without the babysitting.

Install it

Take a ticket.

The next experiment, in your inbox.