L LOCAL
The tool runs on this device, next to the files. Phone, laptop, or workstation — if it can run here, it runs here.
Stare Network
Stratura
Coding-agent sessions that continue across every device.
Closed alpha
THE PROBLEM
A long coding-agent session starts on a laptop. Close the lid and the session disappears. Open another machine and the conversation remains trapped on the first one. The usual workaround is tmux on a VPS, reducing the laptop to a window onto a box that stays on. That is a setup, not a multi-user product.
Git records the commit. It does not record what the agent read, which tools it called, or what happened before the commit. Chat logs are not an audit trail. When something goes wrong, the central question remains unanswered: “what did the agent actually do?”
Stratura keeps the files and the session in a workspace you can reopen from a phone, a laptop, or a server. Tool calls go through a policy check on the machine you are using, and into a signed log the agent does not write.
TOOL PROVIDER LAYER
Sandbox products put the tools inside a VM image they own. We don’t. Compilers, language runtimes, browsers, and model servers should come from the people who already ship them — not from a second copy we have to maintain.
Agentic tool and platform providers integrate once through two language-agnostic programs, with no OS-specific SDKs.
C CONNECTED
This device keeps the session. Another machine runs the tool. Use this when a phone or a laptop cannot run the workload, instead of failing quietly.
F RESTORE
On Linux, resume a saved process on another host. The session continues on a machine that is still awake.
PROVIDER INTERFACE
A provider is a directory with two programs: warm and materialize. Warm builds a self-contained image and prints its checksum. Materialize installs that image on the machine where the session is running and prints one JSON line when it is ready.
If the tool is ready, exit 0. If this machine cannot run it, exit 3 — we show that, then try the next provider. Checksums are stored with the workspace, checked before use, and the agent cannot overwrite them.
Install attempts, including blocked attempts, enter the same signed log as shell commands, HTTP fetches, and model calls. Provider authors supply the two programs; Stratura handles installation, checksums, and logging.
STRATURA HANDLES
- locking the workspace so two devices don’t write at once
- the session UI on each device
- the policy engine
- the signed log
- a separate integration for each OS
The provider only needs to make a known tool available on the current machine, or report that it cannot.
Closed alpha. Building an agentic tool or platform? Bring it to Stratura in the closed alpha.
github.com/maceip/stratura →