Cybros is a self-hosted agent system. Nexus provides the server-side kernel: accounts, conversations, durable execution, model access, tools, approvals and usage accounting. rho is its first agent application, with a browser interface, Telegram integration, an ACP server and a command-line interface. Runners execute tools on the machine or in the container where they are installed.
Source is available at jasl/cybros.ai.
Cybros follows a rolling release: source installations follow main, and the
Docker stack uses the published latest images. Interfaces and database schemas
can still change incompatibly. Back up an installation before upgrading and
check the upgrade guidance.
With Docker and Compose v2 already running, run this in a terminal with curl:
curl -fsSL https://raw.githubusercontent.com/jasl/cybros.ai/main/install/stack/install.sh | shThe installer pulls Nexus and rho images, starts PostgreSQL and prints the rho URL. Open rho and choose Connect to Nexus. Create the first owner account directly if needed; the default installation requires no setup secret. Approve the application connection, and return to rho automatically. The bundled Agent and private Runner connect as part of that authorization. Model configuration follows login. Linux amd64 and arm64, including Docker Desktop on macOS, are supported without host Ruby or JavaScript runtimes. Configure a model provider using your API key, a supported subscription authorization, or a credentialless endpoint.
Follow Getting started through your first conversation. Use the stack guide for LAN access, persistent data, updates and backups. To run rho against an existing Nexus on another machine, see the host installer or rho deployment guide.
Give this prompt to Codex or another coding agent with terminal access to the machine where you want to run Cybros:
Help me install Cybros (Nexus + rho) on this machine and reach my first conversation.
Use the public source and guides at https://github.com/jasl/cybros.ai on main,
or my existing checkout. Follow the rolling installation instructions.
Read docs/getting-started.md and install/stack/README.md first. Check that Docker
is running and Compose v2 is available; help me resolve missing prerequisites.
Use the documented stack installer with local-only access and the default
installation directory unless I specify otherwise. Preserve existing settings
and data. In a noninteractive shell, pass --yes to the documented installer.
Open the ordinary rho URL. Guide me through Connect to Nexus, direct first-owner
creation, application authorization and the return to rho Settings. The default
installation requires no setup secret or extra terminal step. If the operator
explicitly configured NEXUS_SETUP_SECRET, use the private instructions shown by
./cybros instructions for that optional check.
For a home-server deployment, use the documented explicit LAN HTTP mode if I
choose it; ordinary users should not need an SSH tunnel.
Let me create the Nexus account and enter provider credentials directly in the
browser. Keep private setup links and other secrets out of chat and shared logs;
no secrets.env lookup is needed. Existing registrations reconnect through the
same OAuth approval flow; logging in to a connected instance preserves its work.
Check service health, rho's connection and available models as setup progresses.
Give me the installation directory and saved browser URLs, and walk me through
the first-conversation guide. Report any remaining steps clearly; service health
alone does not prove that a model request works.
- Technical manual: installation, daily use, operations and API reference.
- Using rho: conversations, runners, approvals, schedules and troubleshooting.
- Model settings: provider connections, model visibility and optional pricing.
- Build an agent integration: identity, API calls and execution ownership.
- Ruby SDK: API clients and agent framework.
- Local verification and evaluation runbook.
- Rolling release workflow: verification and public source updates.
| Directory | Responsibility |
|---|---|
nexus/ |
Rails kernel, model gateway and Human administration UI |
agents/rho/ |
rho daemon, clients, runner and extensions |
sdks/ruby/ |
cybros_agent Ruby SDK |
cmctl/ |
Human operator CLI for Nexus settings |
install/ |
Host installer, Docker images and combined stack |
e2e/ |
Cross-project tests and evaluation tooling |
docs/ |
Technical manual |
An installation has one Account containing its human and agent members, runners and tools providers. Workspace access controls support collaboration within that account. A runner's working directory is an execution setting, not a filesystem sandbox; give a runner the host permissions and mounts appropriate for its work.
The repository defaults to MIT. Nexus has its own O'Saasy license; subdirectory and third-party licenses take precedence for their contents.