sim-one-alpha

Configuration Reference

SIM-ONE Alpha separates non-secret runtime configuration from credentials and service secrets.

Source-Build Configuration Files

File	Purpose
`src/core/config/gorombo.config.json`	Source seed for models, storage, memory, schedules, gateway settings, and capabilities
`.gorombo/sim-one-alpha/gorombo.config.json`	Generated copy loaded by the built server
`.env`	Provider keys, connector tokens, service credentials, and deployment overrides

Keep secrets out of gorombo.config.json. Do not commit .env or copy secret values into an agent workspace, issue, or chat transcript. Run the runtime build after changing the source seed; the build replaces the generated copy. The packaged onboarding flow will manage installed configuration under ~/.gorombo/ when release assets are published.

Applying Configuration

The pre-release CLI does not include configuration or service-management subcommands. Edit non-secret JSON and secret environment values directly, then restart the gateway through the process or service manager that launched it. The gateway loads configuration at startup.

Configuration Shape

The runtime configuration declares schema version 1.

{
  "version": 1,
  "models": {
    "primary": "minimax-m3-cloud",
    "backup": "codex-brain"
  },
  "storage": {
    "flueDatabasePath": ".gorombo/db/flue.sqlite",
    "sessionDatabasePath": ".gorombo/db/sessions.sqlite"
  },
  "memory": {
    "enabled": true,
    "backend": "sqlite",
    "defaultLimit": 10,
    "maxContextTokens": 1500,
    "enableSemanticNotes": true,
    "retentionDays": 30,
    "archiveDeleteDays": 365,
    "maxChecklistDepth": 5
  },
  "gateway": {
    "mode": "service",
    "port": 3940
  },
  "capabilities": []
}

Unknown application-owned blocks can be preserved, but the runtime validates the required version and model selection plus typed storage, gateway, and capability fields.

Models

models.primary is required. models.backup is optional and must select a different model card. The registry validates both selected cards and their credentials at startup. The backup card is currently configuration metadata; the runtime does not automatically fail over to it when the primary model fails.

Model card	Required credentials
`minimax-m3-cloud`	`OLLAMA_API_KEY` or `OLLAMA_CLOUD_API_KEY`
`deepseek-v4-pro-cloud`	`OLLAMA_API_KEY` or `OLLAMA_CLOUD_API_KEY`
`qwen3-5-cloud`	`OLLAMA_API_KEY` or `OLLAMA_CLOUD_API_KEY`
`kimi-k2.7-code-cloud`	`OLLAMA_API_KEY` or `OLLAMA_CLOUD_API_KEY`
`codex-brain`	`CODEX_BRAIN_LOCAL_API_URL` and `CODEX_BRAIN_LOCAL_API_KEY`

Ollama Cloud defaults to https://ollama.com/v1. CODEX_BRAIN_LOCAL_API_URL must include the OpenAI-compatible /v1 base path.

Model cards own provider identifiers, context limits, output limits, and credential names. Provider secrets do not belong in model cards.

Startup fails closed for an unknown card, duplicate primary and backup cards, or missing credentials for a selected model.

Gateway

{
  "gateway": {
    "mode": "service",
    "port": 3940
  }
}

Supported modes are dev, terminal, and service. The port must be an integer from 1 to 65535.

Set API_SECRET for non-loopback gateway clients. Local terminal requests from the loopback interface do not require the header. Requests carrying forwarding headers are treated as external.

Storage

{
  "storage": {
    "flueDatabasePath": ".gorombo/db/flue.sqlite",
    "sessionDatabasePath": ".gorombo/db/sessions.sqlite",
    "vectorStorePath": ".gorombo/vector"
  }
}

Source-build data	Default location
Flue runtime state	`.gorombo/db/flue.sqlite`
Connector and logical session data	`.gorombo/db/sessions.sqlite`
Structured memory	`.gorombo/db/structured-memory.sqlite`
Protocols	`.gorombo/db/protocols.sqlite`
Runtime capabilities	`~/.gorombo/db/capabilities.sqlite`
Schedules and run history	`.gorombo/db/schedules.sqlite`
Semantic retrieval data	`.gorombo/vector/`

Relative paths resolve from the source checkout working directory. The capability store separately defaults to the user’s home directory. The packaged release contract places installed runtime data under ~/.gorombo/. These files are runtime-managed; back up every active location and do not edit SQLite records directly.

Structured Memory

The memory block controls durable checklists, todos, session notes, retention, and retrieval limits.

Field	Purpose
`enabled`	Enables structured memory
`backend`	Durable backend; `sqlite` is the product default
`defaultLimit`	Default number of retrieved records
`maxContextTokens`	Maximum structured-memory context returned to the agent
`enableSemanticNotes`	Enables semantic note retrieval
`retentionDays`	Active-record retention period
`archiveDeleteDays`	Archived-record deletion horizon
`maxChecklistDepth`	Maximum checklist nesting depth

Deployment overrides use GOROMBO_MEMORY_*, including:

GOROMBO_MEMORY_BACKEND
GOROMBO_MEMORY_SQLITE_PATH
GOROMBO_MEMORY_DEFAULT_LIMIT
GOROMBO_MEMORY_MAX_CONTEXT_TOKENS
GOROMBO_MEMORY_RETENTION_DAYS
GOROMBO_MEMORY_ARCHIVE_DELETE_DAYS
GOROMBO_MEMORY_MAX_CHECKLIST_DEPTH

Providers And Services

Web Research

Web research uses the configured Ollama key by default.

GOROMBO_WEB_SEARCH_PROVIDER
OLLAMA_WEB_SEARCH_BASE_URL
OLLAMA_WEB_SEARCH_TIMEOUT_MS
GOROMBO_RAG_MAX_CONTEXT_TOKENS
GOROMBO_RAG_WEB_FETCH_TOP_K

Embeddings And Retrieval

The embedding chain uses model-card-defined cloud embeddings when configured, then the bundled local ONNX model, then an optional model-card-defined local Ollama endpoint.

OLLAMA_LOCAL_BASE_URL
OLLAMA_LOCAL_API_KEY
GOROMBO_EMBEDDING_MODEL_PATH
GOROMBO_EMBEDDING_TIMEOUT_MS

The current runtime does not read embedding-model-name environment overrides. Cloud and local Ollama embedding model identifiers come from the bundled model cards.

Configure the vector database with storage.vectorStorePath in gorombo.config.json. The current runtime does not read a vector-store environment override.

Image Generation

RUNPOD_API_KEY
RUNPOD_API_BASE_URL
RUNPOD_IMAGE_MODELS_PATH
GOROMBO_IMAGE_OUTPUT_DIR

TELEGRAM_BOT_TOKEN
TELEGRAM_WEBHOOK_SECRET_TOKEN
TELEGRAM_ADMIN_USER_IDS
TELEGRAM_APPROVED_USER_IDS
TELEGRAM_BOT_USERNAME
TELEGRAM_MENTION_PATTERNS

See Connectors And Pairing.

Approvals And Managed Authentication

GOROMBO_APPROVAL_ROOT
GOROMBO_GITHUB_AUTH_ROOT

Approval and managed-auth roots must remain outside Coding Worker project workspaces. The default managed GitHub profile is stored under ~/.gorombo/auth/github/.

Runtime Capabilities

Runtime capabilities can be seeded in gorombo.config.json, but the SQLite capability registry becomes authoritative after installation.

Each capability record includes:

id
kind
name
description
source
sourceRef
version
enabled
config

Valid kinds are skill, tool, worker, and mcp. Use the product CLI for normal capability management rather than editing the configuration array.

Validation

After changes, restart the gateway through its launcher and verify an end-to-end terminal response.

See Troubleshooting when configuration or credential validation fails.

This site is open source. Improve this page.