Remote control · internal system
BEAM
Start a full autonomous working session from a phone, then put the phone away.
Live
No public endpoint
BEAM
The problem it solves
The useful unit of AI work is not a chat message, it is a session with a goal, tools and a workspace. Those normally require sitting at a terminal. If starting work requires being at the desk, everything away from the desk is dead time.
How it works
01
Trigger
pick a job from the phone
→
02
Admit
capacity check — queue if the machine is full
→
03
Spawn
a real terminal session opens with the brief
→
04
Work
runs to completion unattended
→
05
Report
results land on disk and in the status channel
Under the hood
- Subtree-aware capacity limits: the cost of a session includes everything it spawns, not just the parent process.
- Queued-at-capacity is a normal state, not an error — idle sessions get reclaimed and the queue drains.
- Tombstone-gated reaping: nothing is ever killed before its state has been recorded, and the reaper fails closed.
- Liveness is judged on several signals, because a human reading and thinking uses almost no CPU.
Why it matters
Delegation only compounds if starting the work is cheaper than doing it. From a phone, in one tap, it is.