Cybersin

Cybersin is a Rust-based prompt compiler and durable agent runtime that turns typed prompt sources into optimized, routable, cacheable artifacts. It gives agent developers one CLI for deterministic builds, regression evals, sandboxed execution, resumable sessions, cost tracing, and profile-guided optimization.

Getting Started

Prerequisites

• Git
• A current stable Rust toolchain (rustup, rustc, and cargo)

Docker is only required for the container-backed sandbox tests; the quickstart below uses the local SQLite runtime.

Build and run the sample project

Clone the repository and build the workspace:

git clone https://github.com/blokboy/cybersin.git
cd cybersin
cargo build --workspace

Check and compile the included research-team project:

./target/debug/cybersin check fixtures/ic1-research-team
./target/debug/cybersin build fixtures/ic1-research-team \
  --profile release \
  --frozen

Run the compiled project. The runtime automatically creates and uses the SQLite database at .cybersin/cybersin.db.

./target/debug/cybersin \
  --db .cybersin/cybersin.db \
  run \
  --stub \
  --dist fixtures/ic1-research-team/dist \
  --session-id quickstart \
  --agent research-team

Inspect the compiled routing, token counts, traces, and observed cost:

./target/debug/cybersin \
  --db .cybersin/cybersin.db \
  explain researcher fixtures/ic1-research-team \
  --plain

Run the sample project's recorded regression suite:

./target/debug/cybersin eval gate fixtures/ic1-research-team

Interactive shell and help

Run cybersin with no arguments from an interactive terminal to open the Ratatui application shell. The first workflow is prompt conversion: enter a multiline raw prompt, keep or change the standalone conversion model, optionally set an output path, and run the same conversion pipeline used by cybersin convert. Live conversion uses OpenRouter and requires OPENROUTER_API_KEY.

Use cybersin -help, cybersin -h, or cybersin --help to print CLI help and exit. Bare cybersin in a non-interactive context fails clearly instead of waiting on terminal UI input.

Live tool execution

Custom tools declared with run: and an optional container image: are compiled into dist/tools.json; files under the project's tools/ directory are packaged into dist/tools/. DLQ retries and approved calls execute those commands in the selected Docker sandbox:

./target/debug/cybersin \
  --dist fixtures/ic1-research-team/dist \
  --sandbox-backend docker \
  dlq retry '<call-id>'

Network egress allowlisting is not implemented yet. A tool whose agent declares a non-empty sandbox.egress fails closed before a container is started. The web_search built-in is recognized but likewise fails clearly until a search provider is configured.

For the full product design and command surface, see cybersin-spec.md.