The product problem
A task can keep running after its owner leaves the desk. The person still needs to understand findings, answer questions and steer the work without repeating its context.
Engineering & product decisions
Keep a persistent coordinator and direct sessions
The coordinator helps discover and continue real work. Direct session input remains available for steering, queuing and interruption.
Make intermediate results actionable
Useful answers and notifications lead back to their original context. Supported questions retain their actual outstanding request identity.
Represent delivery uncertainty explicitly
Durable reply state distinguishes submitted work, observed progress and uncertain outcomes. Recovery does not assume an interrupted response means an action failed.
Let Android be an execution environment
Optional phone-local Termux and separately enabled accessibility make the phone more than a remote display.
What the evidence supports
Self-hosted alpha for an owner and trusted devices. Runtime observations are version-specific; they do not establish universal eyes-free operation, exactly-once execution or current-release reliability for every workflow. Stock Codex supplies the underlying agent runtime.
This case study describes Arjun Iyer’s product and engineering work through Fallible Software, Co. Model services, frameworks and upstream runtimes retain their own provenance. Evidence and status notes →
Discuss this kind of work ↗