# Fix a production bug from your phone

> Source: <https://treena.app/blogs/fix-production-bugs-from-your-phone>
> Published: 2026-07-17 00:00:00+00:00

# Fix a production bug from your phone

An incident playbook for developers away from their desk — reproduce, patch, test, and ship a hotfix from a phone using a cloud workspace and a coding agent.

Treena

Bugs don't check your calendar. The alert arrives at dinner, on the trail, in the checkout line — precisely when the laptop is elsewhere.

The traditional playbook is grim: acknowledge the page, apologize in the channel, race home, boot up, and *then* start debugging. The bug gets thirty minutes older before anyone touches code.

Here's the pocket-scale version.

## 1. Open the repo cold

No desktop session to resume, because none is needed. Sign in, open the repo, and a cloud workspace clones it fresh. You're looking at the same `main`

your production build came from.

## 2. Point the agent at the evidence

Paste the stack trace or describe the symptom. A coding agent with repo access does what you would do at a desk, faster:

- Search for the failing code path
- Read the surrounding logic and recent history
- Propose a diagnosis you can sanity-check

You know your system; the agent knows where everything is. That division of labor works on a five-inch screen.

## 3. Patch in plan mode

For a production fix, ceremony is a feature. Plan mode drafts the change before a single line moves — you approve the approach, then the agent edits. On a phone, reading a short plan is easier than writing a long prompt, and much easier than typing the patch yourself.

## 4. Prove it

A fix you didn't test is a second incident. The workspace is a real machine, so the proof is real too:

- Run the failing test, watch it pass
- Run the suite around it
- Add the regression test the bug deserved all along

## 5. Ship and follow up

Review the diff line by line — it's a diff, not a wall of chat. Commit, push, open the PR. Your CI and your review process take it from there, same as any desk-born fix.

## The point isn't heroics

Nobody should run their whole on-call from a phone. The point is the gap between *"I saw it"* and *"the fix is up for review"* no longer has to include a commute. Fifteen minutes of steering from wherever you are often beats an hour of delay followed by the same fifteen minutes.

Incidents age badly. Fixes shouldn't have to wait for a desk.

[Join the waitlist](/#waitlist) — the next page you get, answer it from your pocket.
