SymbioSymbioBack to siteEarly Access
Private beta documentation

Use Symbio.
Keep the context.

Practical guidance for working across local shells, remote infrastructure, files and agent context from one workspace.

Getting started

Create your first workspace.

Symbio is currently distributed through the private beta on macOS, Windows and Linux.

  1. 01

    Request access

    Join the private beta from the main site and install the build supplied with your invitation.

  2. 02

    Choose a project

    Open a local folder. It becomes the shared home for your files, terminals and agent session.

  3. 03

    Open a shell

    Start locally or connect a saved SSH host, then decide whether that terminal should enter agent context.

Private beta
Public package-manager commands are not documented yet. Use the installer and release notes included with your invitation.
Workspace

Orchestrate with Multishell.

Keep local shells, remote sessions and long-running processes visible in one grid.

  1. 01

    Build the grid

    Add panes for the shells and processes involved in the task, then arrange them around your workflow.

  2. 02

    Select targets

    Choose the terminals that should receive a broadcast instead of sending every command everywhere.

  3. 03

    Attach context

    Enable Context only on the panes the agent needs. Unselected shells remain outside the model request.

Note
Treat broadcast groups and agent context as separate controls: a terminal can receive commands without being shared with the model.
SSH

Work on remote machines.

Save connection details once, move between hosts quickly and let the agent act on selected remote terminals.

Saved connections

Organise hosts, users, identity files and jump boxes in the remote-access manager.

Remote terminal context

Expose an SSH pane to the agent so it can inspect and execute commands on that machine.

Reconnect status

See connection state and return to interrupted remote work without rebuilding the workspace.

Remote files

Browse the connected file tree beside your terminals and agent session.

Files

Browse and edit code.

Use the same file workflow for local projects and connected SSH hosts.

  1. 01

    Open the explorer

    Navigate the project tree and select a file from the local workspace or remote host.

  2. 02

    Edit with CodeMirror

    Review and change code without leaving Symbio or losing the surrounding terminal context.

  3. 03

    Share intentionally

    Attach only the relevant files or folders to the Neural Graph before asking the agent to reason about them.

Agent

Choose the right level of autonomy.

The mode defines what the agent may do. Context defines what it can see.

ASKAnswer and explainNo workspace changes.
PLANPropose before actingReview the steps before execution.
BUILDExecute the taskWork across selected panes, files and hosts.

Choose your provider

Use OpenAI, Anthropic, Google, Groq, local models or an OpenAI-compatible provider.

Use the command palette

Discover available agent and workspace actions with platform-appropriate shortcuts shown in the app.

Context

Build a Neural Graph.

Compose model context visually instead of sharing an entire workspace by default.

  1. 01

    Add neurons

    Create nodes from notes, terminals, files, folders, URLs, images or PDFs.

  2. 02

    Connect related sources

    Group and link neurons so the graph captures how information belongs together.

  3. 03

    Select agent context

    Enable the neurons required for the task and inspect the final context before running the agent.

Context control
More context is not always better. Smaller, intentional graphs reduce noise and make agent behaviour easier to understand.
Connections

Add capabilities with MCP.

Connect external tools to the graph while keeping control over which operations the agent may use.

  1. 01

    Open the connection catalog

    Choose an existing MCP connection or connect a supported account or local service.

  2. 02

    Review allowed tools

    Inspect read and write capabilities, then enable only the operations needed by the workflow.

  3. 03

    Add the MCP neuron

    Place the connection in a context group and enable it when the agent should use those tools.

Permissions
Read operations can run directly. Write operations should remain visible and require approval where the connected service supports it.
In development

Teach workflows with Tools Studio.

Tools Studio is being built to turn natural-language instructions into reusable agent capabilities.

Describe the tool

Explain its goal, expected inputs, ordered steps, constraints and successful output.

Shape the workflow

Review the generated instructions and refine how the agent should perform the task.

Enable intentionally

Choose when the new capability is available and which workspace context it may use.

Reuse consistently

Let the agent follow the same approved process whenever that tool is selected.

Product status

See what is shipping next.

View roadmap