Skip to main content
Documents the Stack 0.2.0-dev.20260702.3 hosted-ops surface. Mutating cloud actions still require explicit confirmation.
Hosted ops brings Synth cloud state into the local cockpit without making Stack a second backend. Stack reads owner routes and stackd runtime snapshots; it does not read backend databases, raw Redis keys, or compatibility projections.

Surfaces

Cockpit controls

Press x to switch the Agent Bridge into remote mode. Focus Remote SMR or Hosted Optimizers with Tab, then use:

MCP tools

Agents should start with stack_status, then use Stack MCP tools such as:
  • stack_list_live_smrs
  • stack_list_remote_projects
  • stack_list_factories
  • stack_list_hosted_optimizer_runs
  • stack_message_live_run
  • stack_message_factory_project
  • stack_wake_factory
  • stack_control_factory
  • stack_meta_thread_bind_smr_run
  • stack_remote_sync_request
  • stack_remote_gardener_pass
Every live mutation goes through the backend owner route for that resource and requires explicit operator intent.

Remote gardener

The remote gardener is an auxiliary actor for local to cloud relationship management. It can narrate hosted state, record safe next actions, and request push/pull receipts. It does not make the laptop own cloud scheduling.

Limits

Stack hosted ops requires Synth auth. Signed out users see connect prompts and can keep using local mode. Use Connect Synth to unlock hosted features. Next: Stack MCP and Hosted inference.