The agent kept going. The laptop did not.
For solo builders, the cost of coding agents is rarely the model. It is losing the workspace when you close the laptop. Farstax keeps that workspace on.
A coding agent can keep going for hours. Your laptop session usually cannot.
If you build with Claude, Codex, Cursor or Copilot, you already know the pattern: the useful work is a long thread of repo state, provider session, tests and a half-written PR. Then you close the lid, switch networks, or walk away, and the expensive part is not the model. It is restarting the environment.
Solo operators feel this first. There is no teammate holding the branch. There is you, the agent, and whatever survives after you leave the desk.
What actually has to stay up
Not another chatbot. The workspace: the checkout, the tools, the background processes, and a place to review what the agent did.
- Start a task at the desk.
- Let it keep running while you are away.
- Check in from your phone when a decision is actually required.
- Keep using the agents you already pay for.
Farstax is a managed always-on workspace for that loop. It is in private beta for people who already live in coding agents and have felt the cost of tying long-running work to one machine.
Apply for the Farstax beta: farstax.com
If you would rather run the same idea yourself, Agent Bridge OSS is the self-hosted path. The product question is the same either way: can the work continue after you close the laptop?