The Symbiont app icon

The Symbiont app, for the software house and its developers.

The app is where the software house works: it manages the systems and their maps, the access keys, the clients, the stand-ins and the team. Your clients do not need to install any software: they consult their systems on the web.

Mac

Download for Mac · Apple silicon Mac · Intel

Open the .dmg file and drag Symbiont to the Applications folder. The processor type is shown under Apple menu → About This Mac: “Chip Apple M…” indicates Apple silicon, “Processor Intel” indicates Intel.

Windows beta

Download for Windows

Open Symbiont-Setup, which installs the app for the current user. On first launch, Windows may report that the publisher is unknown; in that case, choose More info → Run anyway.

Linux beta

AppImage .deb (Debian, Ubuntu)

AppImage: make the file executable (chmod +x Symbiont-*.AppImage) and open it. The .deb package: sudo apt install ./symbiont_*_amd64.deb. For 64-bit computers (x86_64).

30-day free trial, no credit card required.

Three steps

From installation to work, in a few minutes.

  1. 1

    Download and installation

    The app is available for Mac; in beta for Windows and Linux.

  2. 2

    Sign-in

    Sign in with the Symbiont account. A software house that is new to Symbiont creates the account from the sign-in window with Create the account, and then turns on two-step sign-in.

  3. 3

    Prepare This Computer

    With this function, Symbiont downloads the systems, connects them, restores the development keys from the vault, the encrypted store of keys, and sets up the coding assistant.

After installing

What the app contains, and what it installs on the computer.

In the app

All of the software house's work, in a single window

  1. Systems: every project with its application infrastructure, its status indicator, map, tasks, keys and checks.
  2. Clients: the people at the client company, the emergency keys, the emergency stand-in and the access log.
  3. Stand-ins and Team: who looks after the systems during an absence, and the team members who join or leave, with the access that must be closed.
  4. This Computer: the systems' folders, dbc, the connection with the coding assistant and the local agent.
  5. ⌘K (Ctrl K on Windows and Linux) searches systems, keys, tasks and commands, even offline.

Clients and their consultants use the website app.getsymbiont.com, without installing any software.

The list of systems in the app, grouped by client (Ferri Digital, Acme Logistics, Northwind Viaggi, Ottica Bianchi), with each system's status indicator, tasks and last push.
On the computer

Every operation is described first and waits for confirmation

  1. dbc, Symbiont's program for the terminal, is included in the app: the This Computer section installs and updates it by copying it from there.
  2. The coding assistant (Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI) receives the Symbiont skills and, in each project, the instructions to describe the system while it builds it.
  3. The systems' folders: those already on the computer are recognised by their repository; the others are downloaded with git into ~/Symbiont-projects (or into another folder of choice).
  4. Development keys are restored from the vault into the project's .env file, which is excluded from git. The values never pass through the app or the AI.
  5. The local agent runs, in the background, the checks and tasks that require this computer.
Coding assistants

The functions available with each assistant.

The skills follow the open Agent Skills format; every assistant also reads the Symbiont block in the project's instructions file. The operations log and secret blocking require hooks, that is, commands the assistant runs automatically: they are available in Claude Code and, for shell commands only, in Codex.

AssistantDetected bySkills installed inProject instructionsLog, secret blocking, manifest check
Claude Codeclaude or ~/.claude~/.claude/skills (or $CLAUDE_CONFIG_DIR/skills)AGENTS.md; also CLAUDE.md if the project has oneYes: hooks in .claude/settings.json
OpenAI Codex CLIcodex or ~/.codex~/.agents/skillsAGENTS.mdShell commands only: hooks in .codex/hooks.json, active once approved in Codex with /hooks
Cursor~/.cursor~/.agents/skillsAGENTS.mdNo: run dbc manifest check before finishing
Gemini CLIgemini or ~/.gemini~/.agents/skillsGEMINI.mdNo
GitHub Copilot CLIcopilot or ~/.copilot~/.agents/skills (Copilot in VS Code reads ~/.copilot/skills instead)AGENTS.mdNo

Other assistants: most of them read the Symbiont block in AGENTS.md. Text outside the block's markers is never modified.

For the terminal

This installation is not needed to use the app, which already includes dbc, Symbiont's program for the terminal. It is intended for a server, for continuous integration (CI) or for a computer on which the app is not installed. The script downloads the correct build, checks its SHA-256 fingerprint and installs it in ~/.local/bin/dbc (Windows: %LOCALAPPDATA%\Symbiont\bin\dbc.exe).

macOS AND LINUX
curl -fsSL https://getsymbiont.com/install.sh | sh

If the script reports that the folder is not on the PATH, add it to the shell's startup file and open a new terminal.

WINDOWS · POWERSHELL
irm https://getsymbiont.com/install.ps1 | iex

The script adds the folder to the current user's PATH; the command is available in a new PowerShell window.

The main commands: dbc connect links a folder to a system, dbc manifest push sends the description, dbc skills install connects the coding assistant, dbc vault pull-env --env dev restores the keys from the vault, dbc update updates dbc. dbc --help lists them all.