gBlockParty
Run on the workstation.
Codex runs in a host-owned session on the cloud machine. Your browser connection isn’t the process keeping it alive.
A CLOUD WORKSTATION FOR AI CODING AGENTS
Your laptop leaves.
Your workstation stays.
Give your coding agents a place to run beyond your laptop. Keep sessions on a cloud host, and see what needs you in one Agent Board.
Codex-first · Private alpha · Onboarding by conversation
gBP / WORKSTATION
Cloud hostPersistent runtime
01
Refactor the APICodex session
Running02
Investigate a failing testCodex session
RunningHOST-OWNED SESSIONS
Observe / attach / control
Agent BoardBrowser interface
Client connectionDetach without stop
THE WORK LIVES ON THE HOST.THE CONNECTION IS YOUR WAY IN.
01 / A PLACE FOR THE WORK
Less terminal hunting.
More knowing what’s happening.
For solo developers and technical founders already running coding agents. Especially when another terminal tab is becoming another thing to babysit.
Watch the Agent Board.
See session status and recent output together. Open the session that needs attention for a closer look at its terminal.
Reconnect to the work.
Detach without stopping the session. Reattach while the host and process remain healthy. History recovery and physical device handoff are still being qualified.
02 / THE AGENT BOARD
The big picture.
Then the right terminal.
A monitoring and control surface for your workstation, with a session’s status, repository, and output in the same view.
Notice the exception.
Running, waiting, and failed sessions have distinct states. Approval behavior depends on the agent adapter; the Codex-first path uses sandboxed writes and post-task diff review.
Keep the runtime separate.
The browser is a way into the workstation. The external-client protocol supports revocable devices, read-only observers, and one leased terminal writer at a time.
03 / WHY A WORKSTATION?
Keep your agents.
Lose the scavenger hunt.
A VPS and tmux can already keep a process running. The missing piece is a clear view of the work—and a deliberate way back into it.
gBlockParty brings session lifecycle, board visibility, terminal attachment, and access controls into one system. The first cloud path is Codex; broader agent and client choice is being developed, not promised as universal compatibility.
04 / BUILT. STILL BEING QUALIFIED.
A working alpha.
A clear boundary.
The MVP is implemented. We’re proving the operational details before offering self-serve access.
What to know before joiningIMPLEMENTED
Codex host + Agent Board
Host-owned sessions, browser monitoring and terminal attachment, scoped external clients, and input leases.
BOUNDED PROOF
24-hour VPS qualification passed
A supervised alpha run passed, including a planned service restart. This is a bounded test, not an uptime guarantee.
STILL OPEN
History acceptance + device continuity
A later prompt-handling incident broke session/history continuity. The safety correction is deployed; durable-history acceptance and the physical Mac → phone → Mac run remain open.
05 / BEFORE YOU JOIN
The practical questions.
Who is early access for?
Solo developers and technical founders who already use coding agents, understand remote development, and want to help test persistent sessions and monitoring. The current alpha is a private, single-operator environment, not a shared team service.
Which agents and clients work today?
Codex CLI is the implemented cloud-host path. The codebase also includes Claude Code, Claude Agent SDK, and basic CLI adapters, but they are not qualified cloud offerings. A VS Code extension is implemented; physical Windows acceptance is pending. Chromux has partial attach-only integration. T3 Code, Cursor, and arbitrary bring-your-own clients are not promised integrations.
How much setup is involved?
There is no instant provisioning flow today. Alpha setup is operator-assisted: a cloud host, agent installation and authentication, private network access, and client configuration. We’ll discuss your workflow and readiness before arranging access; no setup-time promise.
Where does it run, and who can access it?
The current alpha runs on a dedicated OVH VPS behind a private Tailscale network. The workstation is not exposed on this public website. External-client enrollment uses revocable scoped credentials, with one input lease and concurrent read-only observers. Production multi-user authentication, team permissions, and enterprise compliance are not available.
What does “persistent” mean here?
Disconnecting a client does not stop a host-owned agent. It does not mean an agent can run through every failure or work past its own limits. Same-host terminal history is implemented with default retention of seven days, 32 MiB per agent, and 1 GiB per host. Acceptance remains open after a preservation incident. Host loss, machine replacement, and cross-host recovery are not proven.
Can I use my phone?
The responsive browser interface includes an away-from-desk Stream view. Phone enrollment, backgrounding, reconnect behavior, and the complete physical Mac → phone → Mac session handoff still need acceptance. We are not advertising proven anywhere-on-any-device control.
What does it cost, and what are the limits?
Public pricing and commercial plans are not set. Agent accounts or model usage and cloud infrastructure are separate cost considerations; no bundled allowance is promised. Capacity depends on the host and workload. Early-access discussions will cover costs and operating limits before any commitment.
LET’S TALK ABOUT YOUR WORKSTATION
What would you
leave running?
Tell us which agent you use, what you run, and where your current setup gets in the way. Start an early-access conversation with the founder.
Email about early accessOpens your email app. You can also write to george@leexperimental.com. Private alpha; access is arranged individually.