BugWEB-142
Login button dead on iOS
“the login button does nothing on my phone 😤” — Sam
via telegramUrgent
A work tracker for solo devs & tiny teams
From “someone had an idea” to “it’s in production.”
Tickhatch is a lightweight work tracker for solo developers and teams of two to five. Every idea, bug, and task moves through one clear pipeline — New → In Progress → Testing → In Production — so the whole team knows what shipped without asking you.
Free · No credit card · Works on your phone
Web appWEByou + Sam + Priya are hereDSP
NewNew3
ProgIn Progress2
TestTesting2
ProdIn Production2
New
3IdeaWEB-141
Dark mode
Priya: “three customers asked this week”
via telegramMedium
ChoreWEB-140
Rotate the API keys
Low
In Progress
2TaskWEB-137
Empty states for the dashboard
agent: claudeHigh
BugWEB-135
Duplicate invite emails
Medium
Testing
2TaskWEB-133
Board invites by email
PR #87High
BugWEB-130
Safari drag ghosting
Medium
In Production
2TaskWEB-128
Password reset by email
shipped 2h ago
BugWEB-126
Checkout 500 on Safari
shipped yesterday
The problem
Your team’s work lives in a group chat.
Ideas and bug reports arrive as messages. Then they scroll away — and you become the only person who knows what’s being worked on and what already shipped.
Ideas evaporate
A good idea lands at 9:14 am. By Friday it’s forty messages up and nobody remembers it.
You are the status page
“Any news on the login bug?” Every answer interrupts the person doing the fixing.
Shipping is invisible
You fixed it Tuesday. Nobody noticed. Three weeks later: “did that ever ship?”
How it works
Four stages. That’s the whole method.
Every ticket moves through the same pipeline: New → In Progress → Testing → In Production. No sprints, no epics, no configuration. Here’s one bug’s life:
New
BugWEB-142
Login button dead on iOS
via telegram
Sam messages the bot. The ticket arrives typed and triaged — no form, no app.
In Progress
BugWEB-142
Login button dead on iOS
fix/web-142
You claim it — or your AI agent does. The branch names the ticket.
Testing
BugWEB-142
Login button dead on iOS
PR #91 open
The PR opens and the ticket follows the code — no one moves it by hand.
In Production
BugWEB-142
Login button dead on iOS
shipped · just now
The merge ships the ticket — and Sam gets an email: “WEB-142 shipped 🚀”.
Integrations
Work comes from chat, code, and agents. Tickhatch meets all three.
How do ideas get in?
Teammates text the bot. Tickets appear triaged.
Anyone on the team messages your Telegram bot and Tickhatch turns it into a ticket — type, priority, and project included, with the original message kept on the ticket. No app to open, no form to fill, no idea lost to the scroll.
@Tickhatchbot · connect once per board
S
the login button does nothing on my phone 😤
@Tickhatchbot · filed as bug · urgent · Web app
BugWEB-142
Login button dead on iOS
via telegramUrgent
What happens when the code ships?
Merge the PR. The ticket ships itself.
Put the ticket ID in your branch or PR title. Opening the PR moves the ticket to In Progress; merging moves it to In Production — and emails whoever reported it. Your board stays true without anyone updating it.
connect a repo per board · webhook, no bot account
fix/web-142-login-button
#91Fix login tap target on iOSMerged
tickhatch · WEB-142 → In Production
WEB-142Login button dead on iOSShipped
Can AI agents work the board?
Native to AI agents.
Tickhatch has a built-in MCP endpoint, so Claude, Cursor, and other agents can find, claim, prioritize, and move tickets on the same board your team sees. The rule: an agent can’t mark work shipped — only a merged PR or a human can.
tickhatch.com/api/mcp · scoped tokens per agent
# claude, wired to your board over MCP
› what should I work on?
3 open tickets. Highest: WEB-142 · bug · urgent
› claim it and start a branch
✓ WEB-142 → In Progress (agent: claude)
✓ branch fix/web-142-login-button
— ship blocked for agents · a merged PR does that —
And the rest
Small on purpose. Sharp everywhere.
Share the board
Invite cofounders by email as owner, editor, or viewer. Status questions answer themselves.
⌘K everything
Jump to any ticket, project, or action from one keystroke. Built for keyboard people.
Realtime board
Moves show up for everyone instantly — no refreshing, no “wait, who changed that?”
#
Human ticket IDs
WEB-142 means something in a commit, a chat, and a changelog. UUIDs don’t.
Tags, per board
Light labels for the slices you care about — payments, onboarding, tech-debt. Filter in a tap.
Phone-first
The whole board works in a mobile browser. Triage from the couch; check status from anywhere.
Who it’s for
Built for tiny teams. Not for big ones.
Tickhatch is for solo developers and technical founders shipping real products with a couple of collaborators — especially when those collaborators don’t live in dev tools.
A fit if you are
- A solo dev shipping a product (or three) on the side
- A technical founder whose cofounders report bugs by text
- A 2–5 person team that finds Jira-style process absurd
- Anyone whose AI agents do real work and need a queue
Not a fit if you need
- Sprints, story points, or velocity charts
- Custom workflows and required fields
- Enterprise roles, audits, and approvals
- Jira’s depth — genuinely, use Jira for that
If a feature would add configuration, it’s probably not in Tickhatch. Opinionated simplicity is the whole point.
FAQ
What is Tickhatch?
Tickhatch is a lightweight work tracker for solo developers and tiny teams of two to five. Every idea, bug, and task becomes a ticket that moves through one pipeline — New → In Progress → Testing → In Production — so the whole team can see what’s happening and what shipped.
Is Tickhatch free?
Yes — the free plan is free forever, not a trial: one project, the full board, and Telegram intake, no credit card. Pro is a flat $10/month (or $96/year) per workspace and adds unlimited projects, members, the GitHub integration, and AI agent access. People you invite never pay.
How is Tickhatch different from Jira, Trello, or Linear?
Tickhatch trades depth for opinion. Four fixed stages instead of configurable workflows, no sprints or story points, and intake happens over chat instead of forms. If your team needs enterprise process, use Jira. If you want to know what shipped without asking, use Tickhatch.
How does the Telegram intake work?
Connect your board to @Tickhatchbot once. From then on, anyone on the team can message the bot and Tickhatch turns the message into a ticket — typed, prioritized, and filed to the right project — with the original message kept on the ticket.
Can AI agents use Tickhatch?
Yes. Tickhatch has a built-in MCP endpoint, so agents like Claude and Cursor can list, claim, prioritize, and move tickets with a scoped token. One guardrail is deliberate: an agent can’t mark work shipped — only a merged pull request or a human can.
Does Tickhatch integrate with GitHub?
Yes. Put a ticket ID like WEB-142 in your branch name or PR title. Opening the PR moves the ticket to In Progress; merging it moves the ticket to In Production and emails the person who reported it.
Does Tickhatch work on a phone?
Yes — the board is designed for mobile browsers first, with no app to install. Capture ideas from the couch and check status from anywhere.
Your next idea deserves better than a group chat.
Free · No credit card · A board in under a minute