{"call_it":"\"Fix my assistant app when I report a bug\" by James Raybould","owner":"James Raybould","runbook":"https://myrunbook.ai/jamesraybould","n":24,"id":"fix","name":"Fix my assistant app when I report a bug","runner":"an assistant I built, plus a coding agent","schedule":"on demand","description":"I report a bug to my assistant by text or voice. A coding agent writes and tests the fix, and my assistant tells me when it is live.","reads":["a complaint sent by text or voice","the ticket tracker","the app's code","the existing tests"],"lands":"A ticket in a tracker, then a tested fix and a push notification saying it is live","loop":"A fixed ticket is closed and the person is told it is live","source":null,"figure":"10 fixes live and smoke-tested since tickets began on 6 Oct","link":null,"example":{"kind":"invented","note":"You: The Harbour Street meeting card shows the end time as the start time.\nAssistant: Filed as ticket 57. I will tell you when it is fixed.\n(35 minutes later)\nAssistant: Ticket 57 is fixed and live. The parser read the end of a time range as the start. It now takes the first time."},"output":"Fix report","build":"Ask first\n- Where should complaints be sent? (default the assistant you already message)\n- May the coding agent deploy without asking? (default no; it opens a change for you to approve)\n- Where should tickets be visible? (default a simple tracker with five statuses: open, in flight, ready, waiting, resolved)\n- How many fixes may run at once? (default two)\n- Where does the \"it is live\" message arrive? (default a text; a notification if the assistant cannot text)\n- Do you have a coding agent with access to the app's code today? (default no; then the routine stops at a filed ticket you fix yourself)\n\nNeeds\n- An assistant that can take a message and store a ticket row: number, title, the complaint as said, status.\n- A tracker people can look at, mirrored from the rows.\n- A coding agent with the app's repository, its tests, and a way to deploy. Connecting: \"It reads the app's code and tickets; it messages only you.\"\n- A watcher that notices new tickets and starts one agent session per job, recording each job's state in a file so nothing starts twice.\n- If your assistant can only chat: say \"bug: X\" and it writes the ticket; you paste the ticket into your coding tool yourself and tell the assistant when it is fixed.\n\nBuild\n1. Read (file): the assistant's ticket tool takes a short title and the complaint as said, stores a row with an incrementing number, and replies with that number. Mirror the row to the tracker.\n2. Read (pick up): the watcher checks for open tickets on a schedule, a few minutes apart, and starts a session per ticket up to the limit. The job file holds each ticket's state.\n3. Decide (brief): the agent's standing brief is: read the ticket; find the cause; fix; run the type check and the tests; mark it ready. A separate merge step merges, deploys and checks the live app.\n4. Decide (status): open when filed; in flight when a session starts; ready when the change passes its checks; waiting when the agent needs the person, with the reason; resolved when the fix is live, with a plain note of what shipped.\n5. Deliver: when live, resolve the ticket and message the person what was wrong and what it now does. If it cannot finish, message that it needs them, with the reason. Fallback: a notification. Nothing goes to anyone else.\n6. Memory: the job file and the tracker; a resolved ticket is never reopened by the watcher. One agent session per ticket.\n\nCheck\n- File a deliberately small complaint with deploy off: the ticket appears as open, moves to in flight, then ready, with the type check and tests passing.\n- The message to you names the cause and the result.\n- Quiet run: a watcher pass with no open tickets does nothing and logs one line; the first real run shows as a status change in the tracker.\n\nIn my version\n- I complain to Q, my assistant, by text or voice; tickets mirror to a Notion database; a watcher on my Mac starts Claude Code sessions, one at a time; a merge step deploys and smoke-tests; Q sends a push notification when the fix is live.","built":{"method":"POST","url":"https://myrunbook.ai/api/runbooks/_bSFet4kFzjy/built","body":{"job":"fix","by_handle":"<your own runbook handle, if you have one>","note":"<what you built, what you changed, what broke; up to 1200 characters>"},"ask_first":"Only send this after the person says yes.","link_for_the_person":"https://myrunbook.ai/jamesraybould/built?routine=24"}}