Works with the agents and runtimes you already use.
sys9 doesn't ask you to switch agent loops. Keep your runtime — sys9 brings the memory, compute, data and session tools around it. The entries below describe technical integrations or ways to connect services, not commercial partnerships or endorsements.
The ecosystem sys9 plugs into.
Support and setup differ by product and runtime. Follow the linked product guides for authentication, installation and feature availability.
Claude Code
A managed runtime in smith9 and a supported runtime in chord9. owl9 captures its native sessions, mem9 adds shared memory, and db9 installs an agent skill.
Explore setup →Codex
A managed runtime in smith9 and a supported runtime in chord9. owl9 captures its native sessions, mem9 adds shared memory, and db9 installs an agent skill.
Explore setup →OpenCode
A managed runtime in smith9. owl9 provides an OpenCode plugin, mem9 plugs in through the OpenCode plugin SDK, and db9 installs an agent skill.
Explore setup →Gemini CLI
A managed runtime in smith9. Configure a Gemini provider, then run Sessions and Turns like any other smith9 runtime.
Explore setup →OpenClaw
mem9 ships an OpenClaw memory plugin for persistent memory that outlives resets and restarts.
Explore setup →Hermes Agent
mem9 ships a memory provider plugin for Hermes Agent, with its own setup and activation flow.
Explore setup →DeepSeek Harness
mem9 ships a native DeepSeek Harness bundle with recall, ingest, and memory tools.
Explore setup →Pi
A managed runtime in smith9, with a Pi session-capture extension in owl9. Pi in chord9 is Experimental and must be enabled in account preferences before starting new Pi sessions.
Explore setup →Any agent with a shell
sys9 is a CLI first. Any agent or IDE assistant that can run commands can drive run9, drive9, db9, and the services with the credentials you provide; no dedicated plugin is required or implied.
Explore setup →Set up native session capture.
owl9 provides native integrations for Claude Code, Codex, OpenCode, and Pi.
Install the CLI, configure your space and set up the runtime before enabling collection.
The public owl9-plugins repository contains the integration source.
# Install the launcher. npm install -g @sys9/cli # Replace the placeholder with your own unique space. # Enter a private-space secret at the prompt. sys9 owl set space '<your-unique-space-id>' --secret - sys9 owl setup claude-code OWL9_ENABLE=1 claude
Claude Code must already be installed and authenticated. Configure the space secret before its first upload; adding a secret later does not make an open space private.
Building an agent or runtime? Let's integrate.
If your tool runs agents, sys9 can give it memory, compute, data, and observability. We'd like to hear from you.