Skip to main content
SpecWeave Studio / private pilot

Your agents.
Your machines.
One clear view.

Keep native coding sessions within reach across your Macs. See the machine, account, work and approvals behind each session.

Discuss a team pilot ↗Read the architecture

Privately validated on three Macs. Public distribution and enterprise service commitments are not announced.

Architecture / private fleetEach boundary is explicit
Your browserReview the session. Approve the next action.
HTTPS over your private Tailscale network
Network accessTailscale Serve

Reaches the selected machine’s loopback service.

Separate Studio pairing on every host
01Your laptopStudio runtime
Native agent · selected account
Local repo + session state
02Your workstationStudio runtime
Native agent · selected account
Local repo + session state
03Your remote MacStudio runtime
Native agent · selected account
Local repo + session state

Model provider boundary
Native agents contact their configured providers. Private remote access does not make cloud inference local.

Architecture illustration. Host names are examples. Network access and permission to act are separate controls.
Inside the private pilot

The actual controls.
The actual state.

Choose the model, effort and supervision. Inspect provider health before asking it to work.

28 seconds / Actual private-pilot interface captures, 8 October 2026, with narrated navigation guidance. This overview is not a live execution recording. AI narration using Anton’s voice; music: “Make Funk” by HoliznaCC0, CC0.
Actual Studio composer showing GPT-6.1-Sol, Low effort and Supervised controls
Native composer / model, effort and supervision remain separate choices.
Actual provider status: Codex authenticated; Claude needs attention
Provider status / this capture shows a Claude warning, not successful Claude execution.

Actual private-pilot UI, 8 October 2026. Cropped to exclude private account and workspace details. Versions and availability reflect that capture.

Three products / distinct jobs

The work. The expertise.
The workspace.

Use the open-source workflow today. Add skills when they help. Evaluate the new native workspace through a pilot.

03 / The workspace

SpecWeave Studio

A private pilot for native coding sessions across your machines, with explicit accounts and approvals.

Explore the private pilot ↗
Start with SpecWeave

One task.
Evidence you can follow.

Watch a real CLI workflow from spec to tests to a local handoff. This is the repository workflow available today.

60 seconds / SpecWeave 3.0.6. Actual CLI output from a disposable repository: two passing tests, one of two tasks complete, and a local handoff into a clean clone. No remote push or production changes. AI narration using Anton’s voice; music: “Make Funk” by HoliznaCC0, CC0.
Designed around real boundaries

Reach a machine.
Keep control of the work.

A network connection, an account and permission to run are different things. Studio keeps them visible.

01 / Connect

Your private network.

Tailscale Serve reaches a host’s loopback service over private HTTPS. Each host also requires its own scoped Studio pairing.

02 / Work

Native sessions.

The runtime uses the selected machine and account. Review the output and handle the agent’s approval requests before it continues.

03 / Continue

Evidence stays useful.

Keep project specs and task evidence in git with SpecWeave. Explicit handoff moves work when you choose; local checkpoints help recover it.

Evidence / 8 October 2026

Tested privately.
Described precisely.

The accepted fleet delivery recorded native Codex execution on three Macs, with source and artifact readback. The smoke test completed one marker-reading turn per host, sequentially.

Read the verification scope ↗

Evaluate the fit.

  • Start with one repository and one real workflow.
  • Check account ownership, approvals and reconnect behavior.
  • Measure accepted work and time spent recovering context.
  • Agree security, support and rollout needs before expanding.

These checks do not establish enterprise concurrency, production ROI, certification or a service-level agreement.

For engineering leads and platform teams

Start with a workflow.
Prove it with your team.

Discuss a team pilot ↗Architecture and first steps