← Blog

Note from ground

Comot go outside. Agent still dey work.

No be phone been dey keep your agent alive. Na the server. Once you believe that one, afternoon for outside no go cost you anything — you comot, the work continue, and na only question wey really need answer go disturb you.

Four sessions for machine wey be your own. Three of dem no send where you dey. Na the fourth one be the only reason to bring phone comot for pocket.

Work dey end whether build don end or e never end. Pau hana — the end of the work day — dey come with im own time, and the usual answer na to ignore am: leave laptop open for table, dey half-watch progress bar, and give the evening give process wey no need you for any of am.

That trade only make sense if the work dey happen for the machine wey you dey carry. Most times e no be so. The agent na process for server, e dey edit files for that server disk, e dey run that server tests. Your phone na window wey dey look am. Close the window, the room still dey there.

Na the server be the layer wey dey last

Start Claude Code or Codex inside tmux, herdr or Zellij and the session belong to the server, no be to your connection. Fall reach one bar of signal, waka enter lava tube, keep phone for two hours — the agent go continue to read, edit and run tests, because nothing about am ever tie to you.

Na this be the whole trick, and e good make we talk am well well, because e easy to praise the wrong part. No be the app dey hold the process up. Na the multiplexer for the other end dey hold am. Mobile SSH own work na to comot and come back clean.

No be you be the power supply. Stop to dey behave like one.

Check am small, no dey nurse am

Agent wey dey run for one hour need person for around ninety seconds out of the whole thing. Waiting never be the problem; the problem na say you no sabi when the ninety seconds go land, and na that one dey make people dey stare screen wey no get anything to talk.

Agent Alerts answer that one. The detection dey deliberately dull, na why person fit trust am: terminal bell, OSC 9 or OSC 777 notification, and the agent hook wey you install for the server once. E no dey read your output take guess wetin you mean, and no sensitivity knob dey to tune — e dey report wetin the program for the other end really announce.

So phone go stay for your pocket until real question show. Then e go buzz, you read the prompt, tap answer, and put am back. Na the whole interaction be that, and e dey work from beach, from trail head, or from the queue wey you dey stand buy shave ice.

Before you waka comot

  1. Start am under multiplexer

    Run the agent inside tmux, herdr or Zellij so that the session go survive your connection instead of to depend on am.

  2. Install the agent hook

    Once for every server, from inside the app. Na small shell script wey any agent fit call — no be vendor integration, and e no tie to one CLI.

  3. Prove say one alert dey land

    Trigger prompt and confirm say the phone buzz before you go depend on am. Alert wey you never see work no be plan.

  4. Give am stopping point

    Task wey dey end for sensible place better pass one wey no get end, because na you choose not to watch am.

Task wey you fit leave alone Read AGENTS.md, then fix the handler tests wey dey fail. Inspect the diff before you edit, run the focused tests, and stop after dem pass — no commit.

Wetin the island no fit fix

Two honest limits, because post wey only list strength na advert.

Wetin survive when you waka comot
When phone enter your pocketE dey continue?
The agent process for the serverNa tmux, herdr or Zellij own am ✓ Yes
Files, diffs and test outputFor the server disk ✓ Yes
Your place inside the sessionE re-attach when you come back ✓ Yes
The connection, for AndroidForeground service dey hold am ✓ Yes
The connection, for iOSSmall background time — then e reconnect — No
Alert wey no get signal to carry amE needs active connection; delivery no dey guaranteed — No
The agent dey run for every row. Na only whether your phone still hold the window open dey change.

The platform difference dey real and e worth to plan for am. For Android, foreground service dey hold the connection while the app dey background — that notification wey no dey comot na the session. iOS dey give the app only small time for background; after e suspend, e go reconnect and attach back to your multiplexer when you return. Alerts need the connection to still dey active. Either way, the agent for the server never stop, na that be the point. Na only the window close.

Aloha no be excuse to careless

To comot well na small discipline. Anything wey you no go gree make e run alone for two hours no suppose start as you dey waka comot door — agent wey dey middle of migration no dey better because you far. Give am task wey get natural stopping point, tell am make e inspect before e edit, and make the diff be the thing wey you go review when you come back.

And take the same care for the notification like say na pager. If everything dey alert, nothing dey alert. The hook dey fire for the states wey worth to disturb person; leave am like that and the buzz go still mean something.

The build no need audience. Comot go dey somewhere.