Your agent guesses. Give it answers.
A coding agent fills every gap in a Spec with something that compiles. Tinkerbee finds the gaps first, asks you, and hands the agent the answers over MCP.
Beta access. We approve every account by hand. Or email us- 21 ticketsbuilt in one evening, one agent per ticket, from Tinkerbee Specs
- Read-onlyGitHub App and MCP server. Tinkerbee never writes to your repo
- 3 agentsClaude Code, Cursor and Codex read the same live Spec
- 1
Grill the Spec
Tinkerbee reads the Spec and your code, then lists what is missing as Open Questions, each with options and a recommended pick.
- 2
Keep the answers
Each answer becomes a Decision. Glossary terms and ADRs stay with the repo, so the next Spec starts from them.
- 3
Cut thin tickets
A Ready Spec splits into small slices in blocked-by order, each marked AFK or HITL.
- 4
Serve it over MCP
Your agent pulls the Spec, its Decisions and its tickets, signed in with your GitHub identity.
Questions
Which agents work with Tinkerbee?
Any MCP client. We test with Claude Code, Cursor and Codex.
Does Tinkerbee change my code?
No. The GitHub App reads contents, metadata and pull requests. It cannot write.
What does it cost?
The beta is free. We plan to charge per editor seat with a monthly Token cap, and we will tell you before anything costs money.
Get on the beta list.
We approve every team by hand. Leave your email and we will reach out.