Source reviewed 2026-11-08
What stays local. What connects.
This note covers the Cyberine application and plugin, not the retention policies of third-party services or a website hosting provider.
Local storage
Run history, including task and worker output, is stored under .local/runs/ in the working project by default. CYBERINE_RUNS_DIR can change that location. The cross-project registry lives under ~/.cyberine/runs/ by default; CYBERINE_HOME changes the home directory.
Provider API keys saved with cyberine auth are stored in ~/.cyberine/.env by default. On POSIX systems, the writer creates the file with mode 600 (owner read/write only) and attempts to tighten existing file permissions; a failure produces a warning. Windows uses filesystem access controls instead.
The web dashboard binds to 127.0.0.1:41700 by default. Changing its bind address or configuring a remote server changes that local boundary. Local storage does not mean work stays offline: configured providers, tools and integrations can receive it.
Providers and accounts
Tasks and the context needed to perform them go to the providers and CLIs you configure, under your own accounts and their terms. Provider charges and subscription limits remain yours. Cyberine does not resell model tokens or subscription quota.
Cyberine launches vendor CLIs under your own accounts. With an existing CLI login, the vendor CLI manages its credentials. An explicitly configured Claude token-file account is an exception: Cyberine reads that file and passes the token to the Claude CLI through a file descriptor (a private process input). The project policy forbids extracting subscription OAuth tokens (credentials for a provider login) to call provider APIs outside the vendor harness. Direct model calls use configured API credentials. Dashboard sign-in is separate from provider subscription authentication.
Network connections
The following connections are implemented in Cyberine itself, in addition to configured model and CLI execution. “On use” means a command or tool invocation triggers the request; an agent may invoke a tool while carrying out your task. It does not imply a separate confirmation before each request.
| Connection | Control | Destination and data |
|---|---|---|
| Update checks | Enabled by default; disable with CYBERINE_NO_UPDATE_CHECK=1. Results are cached for a day. | GET GitHub releases/latest for the checkout’s origin repository, or registry.npmjs.org for the installed package’s latest version. Sends the repository/package identifier and cyberine-update-check user agent, not run contents. |
| Tracing | Opt-in: set CYBERINE_OTEL_ENDPOINT; unset it to disable. | Exports OpenTelemetry traces (timed run records) to your collector’s /v1/traces. Includes run, step and agent IDs, workflow name, model/provider, timing, token counts, cost, status and an error classification. Prompt and response bodies are not exported by this module. |
| Web search | On use of web_search or research. Automatic backend selection uses an available Claude seat, then a configured Perplexity key, then a DeepSeek key. | Search queries go through the selected CLI, Perplexity /chat/completions, or DeepSeek /v1/tools/search. CYBERINE_WEB_SEARCH_BACKEND selects the backend. |
| Web page retrieval | On use of web_fetch. Direct retrieval is the default; CYBERINE_WEB_FETCH_BACKEND=deepseek selects the API backend and requires a key. | Direct HTTP/HTTPS requests and DNS lookups reach the requested website, including followed redirects. The DeepSeek backend sends the requested URL to /v1/tools/fetch on the configured DeepSeek origin. |
| Run and alert webhooks | Opt-in: CYBERINE_WEBHOOK_URL, a per-run override, or CYBERINE_ALERT_WEBHOOK_URL for alerts. | Posts run lifecycle data or alerts to your endpoint. Run payloads can include workflow name, detail and a summary of the winning output. |
| Telegram alerts | Opt-in: configure both CYBERINE_TELEGRAM_BOT_TOKEN and CYBERINE_TELEGRAM_CHAT_ID. | Sends alert message text to Telegram sendMessage; the default API host is api.telegram.org. CYBERINE_TELEGRAM_API_BASE can override it. |
| Shared memory | Opt-in: enable CYBERINE_CONTEXTQ or select CYBERINE_MEMORY_BACKEND=contextq or mcp. Explicit local/none selects no memory augmentation backend. | ContextQ receives saved context, run records and search queries. It defaults to localhost:38200; CYBERINE_CONTEXTQ_URL can point elsewhere. The MCP backend uses CYBERINE_MEMORY_MCP_SERVER or the ContextQ /mcp endpoint. |
| External tools | Opt-in: CYBERINE_MCP_SERVERS or CYBERINE_MCP_CONFIG. | MCP (external tool connection protocol) connects to configured HTTP servers or launches configured local server processes. Tool discovery and calls send their arguments to those servers; local processes can make their own network calls. |
| Remote server and message bus | Opt-in: CYBERINE_SERVER_URL or an SDK base URL; HTTP message bus requires CYBERINE_BUS_BACKEND=http and a hub URL. | The remote client sends tasks, working-directory paths and API requests to your Cyberine server. The bus sends messages and presence and reads events, inbox and roster from CYBERINE_BUS_HUB_URL, falling back to CYBERINE_SERVER_URL. |
| Dashboard sign-in | On use, after an operator configures a GitHub or Google OAuth provider. | The browser visits the provider’s authorization page. Cyberine exchanges the authorization code at GitHub /login/oauth/access_token or Google /token and requests GitHub /user and, when needed, /user/emails, or Google /v1/userinfo. This is dashboard identity, not a model subscription token. |
| Provider diagnostics | On use of provider key validation, model listing or doctor with a configured gateway. | Key validation sends a small model request to the configured provider. Model listing fetches Ollama /api/tags or the configured Ollama Cloud /models path. Doctor requests the configured gateway URL. |
| Explicit installation | On use of remote plugin installation or the confirmed account install-claude command. | Remote plugins are cloned with git from the supplied repository. Claude installation invokes the selected native installer or package manager, which contacts its download services. User-configured hooks, plugins, shell tools and vendor CLIs can make additional connections under their own configuration. |
Licence and price
Cyberine is free for individuals, for personal or commercial use, under its proprietary licence. This covers the current single-user CLI, TUI, chat REPL, Claude Code plugin, local web dashboard and worker lanes. The repository LICENSE contains the licence terms.
A team tier is planned. No team price is published here, and the planned team tier is not a shipped service. Provider API usage and subscriptions are separate from the price of Cyberine.