Start with runtime diagnostics
Use joymux doctor --json to inspect readiness, the runtime endpoint, and protocol information. Confirm the installed build and supported enforcement surfaces before integration.
Give your agents a better execution environment.
Connect through hooks, the CLI, Unix socket, or SDKs. Give agents concurrent sessions, resumable output, workspace facts, and bounded context while each harness keeps its own reasoning and planning.
Execute through a session
Use joymux exec for structured process execution. Managed sessions provide explicit lifecycle state, output, cancellation, and resumable event reads.
Reconnect with evidence
Use session identifiers and event cursors to recover output. Integrations can consume structured state instead of scraping terminal history.
A BETTER ENVIRONMENT FOR AILess repeated work.
Less repeated work.
More useful execution.
Agents need more than a terminal. JoyMux gives them persistent execution, compact context, and shared workspace facts—so they spend less effort recovering state and repeating work.
Keep execution alive
Durable sessions separate the work from the client. Reconnect to the same execution history instead of rebuilding it from terminal output.
Persistent sessions · PTY workers · Event cursorsRun independent work in parallel
Concurrent process and PTY sessions keep input, output, and lifecycle state separate so independent jobs can progress together.
Concurrent sessions · Isolated streams · Structured stateSend the context that changed
Bounded delta views and explicit Context Capsules give agents compact catch-up information instead of repeatedly copying full histories.
Workspace deltas · Bounded context · Per-agent cursorsAvoid duplicate effort
Shared workspace facts and advisory warnings reveal overlapping edits, repeated tests, duplicate processes, and stale file state.
Workspace state · Handoff packets · Overlap warningsKeep output moving
Disk-backed output and resumable reads let slow clients catch up without blocking process output or keeping the full history in memory.
Bounded memory · Durable output · Resumable readsGive every harness the same foundation
Connect agents to a shared local execution protocol through hooks, CLI, or SDKs. Each harness keeps its own reasoning and planning.
Vendor-neutral runtime · Local APIs · Rust, Python & TypeScriptWhere the efficiency comes from: less history to resend, fewer tasks to reconstruct, and independent work that can run concurrently. Measure the actual effect on your workload.
Explore the runtimeInspect before you integrate.
# Inspect runtime readiness
joymux doctor --json
# Inspect the enforcement boundary
joymux security surfaces
# Run a managed process
joymux exec -- echo helloRun on a machine with JoyMux installed. Harnesses connect through hooks and the local Unix socket.
CONTROL WHAT COMES NEXTAI agents are getting more authority.