Files
roboco/docs/rag/architecture/config-reference.md
T
3ccc723cd4 v0.17.0 — Wave 3: sandbox DB, DB isolation, mobile UI, cloud auth, X account, roadmap engine (#303)
* feat(sandbox): throwaway per-agent Postgres/Redis sandbox containers

Orchestrator-provisioned sibling containers per agent spawn
(SandboxProvisioner, roboco/runtime/sandbox.py). Per-project opt-in via
projects.sandbox_services (migration 057); master switch
ROBOCO_SANDBOX_DB_ENABLED, default-off, armed in the NAS compose only.

When active, ROBOCO_TEST_DB_* / ROBOCO_TEST_REDIS_* point at the sandbox
and the prod-creds gate-env injection is suppressed (sandbox replaces,
never coexists). Sandbox lifetime tracks the agent container: teardown at
every removal path, orphan janitor at startup + each reaper tick with a
grace window for mid-flight spawns. The pre-spawn stale-clear spares the
just-provisioned sandbox; provision pre-clears stale same-named
containers from a crash-missed teardown.

Panel: per-project sandbox-service switches in the edit dialog + feature
flag card entry.

* docs: CLAUDE.md entry for the sandboxed dev DB/Redis subsystem

* feat(security): isolate prod Postgres/Redis from agent containers (roboco_data network)

Second user-defined bridge roboco_data carries postgres+redis only; the
orchestrator is multi-homed (default + data). Spawned agents and their
sandbox sidecars stay on roboco_default and can no longer resolve or
reach roboco-postgres:5432 / roboco-redis:6379 (redis has no auth —
membership is its only containment). Normal bridge, so host-published
ports (15432/16379) keep working. Applied to both build composes and
the registry compose; docker-compose.yml re-synced byte-identical with
docker-compose.yaml (it had drifted by the sandbox flag block).

ROBOCO_DB_NETWORK_ISOLATED (config default false, armed alongside the
topology) suppresses the legacy _append_gate_env prod-creds injection:
under isolation those creds dead-end, and unreachable creds are worse
than none. DB-needing projects opt into sandbox_services instead. The
flag is deliberately not a panel feature flag - it must travel with the
compose networks: stanzas.

Preserved by construction: agent<->agent A2A and orchestrator->agent SDK
polls on :9000, MCP->orchestrator on :8000, ollama reachability, docker
exec/inspect (daemon socket), host port publishing.

* feat(panel): full mobile responsiveness pass

Shared primitives: useIsMobile (useSyncExternalStore, hydration-safe,
memoized matchMedia subscribe), ResponsiveTable table->card switch below
md (single subtree mounted, no duplicated interactive rows), scrollable
snap TabsList in the base primitive (justify-center-safe so the first
tab stays reachable on overflow), persistent md:hidden bottom tab bar
(Overview/Tasks/Kanban/Chat, safe-area padded).

Applied: card lists for tasks/projects/products/work-sessions/sessions
+ the three raw metrics tables; CEO approval queue / release proposal /
playbook review action rows stack on narrow; command-center reorders
approvals above the fold on mobile; task-header metadata wraps;
Communications + A2A become URL-driven single-pane drill-downs below lg
(fixes the unconstrained-height ScrollArea bug) with dvh heights;
recharts label density/radius adapts via useIsMobile; git diff viewer
gets mobile font + wrap toggle; vh->dvh sweep; chat composers get
safe-area-inset padding; dashboard main p-4 md:p-6 + pb-20 for the bar.

Verified at 375px on the built app: bottom bar, drawer, approval-first
overview, swipeable kanban tab strip. All gates green (eslint, tsc,
vitest 249, next build 24/24 routes).

* feat(auth): cloud auth via FastAPI Users (default-off, single-user cookie session)

ROBOCO_CLOUD_AUTH_ENABLED (default off) lets the panel/API be exposed
beyond localhost without changing the CEO's local no-login flow while
off — get_agent_context and the WS gate are byte-for-byte unchanged in
off-mode. On: header-trust dies for humans — any agent-role claim (ceo
or a privileged PM/board role) with no valid HMAC token or session
cookie is 401, closing the header-spoof hole on the host-published
:8000 port for every role. The agent-fleet HMAC path and the system
self-PATCH keep working unmodified in both modes.

Single seeded CEO user (migration 058 users table, UserTable), no
registration router — idempotent env-driven upsert at startup by PK.
Cookie transport (httponly/secure/samesite=lax) + a JWTStrategy bound
to a fingerprint of the current password hash (rotating the password
invalidates every prior session). Sliding 30-day session: every
authenticated request re-mints the cookie, so an active session never
expires — no unexpected logouts.

Panel: (auth)/login page + proxy.ts (Next 16 rename of middleware; probes
/auth/status over the docker-internal URL, fails open to off) gate the
dashboard; client.ts gets withCredentials + 401->/login. nginx unchanged.

Review hardening: broadened the on-mode rejection from ceo-only to every
non-CEO role without a valid token (was only closed when
ROBOCO_AGENT_AUTH_REQUIRED was also armed); Next-16 proxy.ts rename to
clear the middleware deprecation warning.

* feat(x): RoboCo X account engine — HoM drafts, per-post CEO approval (default-off)

ROBOCO_X_ENGINE_ENABLED (default off, inert without creds). Mirrors the
ReleaseManagerEngine held-artifact shape: XEngine drafts a post when a
release publishes (via a draft_release_post seam on ReleaseProposalService
.approve) and drafts replies to meaningful mentions (dedicated poll loop,
x_seen_mentions dedup ledger, per-cycle/open caps). Drafting is
local-model-only, clamped to 280 chars. Nothing auto-posts — every tweet
is a held task (source x_post/x_reply, confirmed_by_human=False,
Secretary-owned, dispatcher-skipped) the CEO edits/approves/rejects in a
panel queue.

The four OAuth 1.0a secrets live Fernet-encrypted in a singleton
x_credentials row (migration 059, all-or-nothing, API returns only
has_credentials); decryption is server-side, agents never hold creds or
egress. Hand-rolled OAuth 1.0a HMAC-SHA1 signer, no new dependency;
NullXClient makes the unconfigured path a graceful no-op.

XPostService.approve (CEO-only) is the sole caller of post_tweet.

Review hardening: closed a double-post race — the approve path now
re-reads committed task state inside the Redis lock and commits COMPLETED
before releasing, so a concurrent approve that acquires the lock after the
winner released can't re-post (SET-NX is non-waiting, and the route-level
commit landed after the lock dropped). Added a regression test.

* feat(roadmap): board roadmap engine — PO proposes themed cycles, CEO approves per-item (default-off)

ROBOCO_ROADMAP_ENGINE_ENABLED (default off). Weekly, RoadmapEngine opens
ONE held exploration task (source=board_roadmap, confirmed_by_human=False,
Product-Owner-assigned), deduped to one open cycle. A dedicated one-shot
_dispatch_roadmap_exploration spawns the PO solo (not the two-reviewer
board path, which would also spawn HoM + fire Approve-&-Start). The PO
explores read-only (git/KB/metrics/releases/charter/web) and makes one
propose_roadmap call (PO-only content verb) authoring a themed cycle —
goal + 3-7 item drafts — persisted as a roadmap_cycle marker (no table,
no migration; head stays 059).

The CEO acts per-item in the panel roadmap queue: approve materializes a
BACKLOG task (source=roadmap, no assignee — never auto-starts), reject
records a reason; all-items-terminal completes the exploration task.
RoadmapService is idempotent per item. Dispatchers skip board_roadmap.

Includes a real SQLAlchemy dirty-check fix (deep-copy the JSON marker
before mutating, or the in-place edit + reassign compares equal to its
own baseline and the UPDATE is skipped).

Review hardening: create_task_from_draft now honors a draft-declared
source only from a {prompter, roadmap} whitelist — drafts are
LLM-authored, so an unbounded source could impersonate a privileged
origin (release_manager would even wedge that engine's dedup).

* chore(release): 0.17.0

Wave 3 — six default-off subsystems: sandboxed dev DB/Redis, prod
Postgres/Redis network isolation, full mobile UI pass, cloud auth
(FastAPI Users), the RoboCo X account engine, and the board roadmap
engine. Plus the waves 1+2 work already on master since 0.16.0.

Version bumped across the canonical set (config.py, __init__.py,
pyproject.toml, panel/package.json, uv.lock); CHANGELOG [Unreleased]
cut to [0.17.0]; docs/map delta added.

Compose: every optional feature armed :-true in the NAS composes, OFF
in the user-facing registry compose. Two opt-in exceptions default off
(CLOUD_AUTH — needs email/password/secret + TLS, would otherwise fail
startup; ROUTING_STRICT — fail-closed spawning). DB_NETWORK_ISOLATED
stays on in both (coupled to the roboco_data topology).

* chore(compose): arm cloud_auth + routing_strict ON in the NAS composes

Every feature defaults ON in the NAS composes per policy — these two
were wrongly left off. Both keep the ${VAR:-true} form so the operator
controls the real runtime via .env: cloud auth needs
ROBOCO_CLOUD_AUTH_EMAIL/_PASSWORD/_SECRET + TLS set there before a boot
(else startup fails loud), and routing_strict is fail-closed. Registry
compose keeps both off.

* fix(ci): reflow board.md prose (quality gate) + document v0.17.0 env creds

The roadmap section added hard-wrapped prose that failed the markdown
prose gate; reflowed (token-invariant). Also brought .env.example
current: cloud auth (now armed — needs SECRET or startup fails), routing
strict, the X engine (panel-entered OAuth), and web research.

* fix(ci): reduce cyclomatic complexity of five wave-3 blocks (xenon gate)

The wave-3 subagents introduced C-rank functions the CI xenon gate
rejects (my per-item reviews ran ruff/mypy/pytest but not xenon):
- sandbox.janitor_sweep -> extract _list_labeled_sandboxes /
  _list_live_agent_containers / _prune_grace
- x_client.fetch_mentions -> extract _parse_mention_items
- x_engine.run_cycle -> extract _process_mentions
- orchestrator._dispatch_pm_work -> extract the source-skip into a
  MODULE-level _is_held_ceo_source (module, not method, so the
  wholesale-mocked dispatcher unit tests exercise the real logic)
- auth/seed.ensure_seed_user -> extract _apply_seed_updates (module avg -> A)

Behavior-preserving; full suite green (11902), xenon clean.

* fix(ci): declare pyjwt + fastapi-users-db-sqlalchemy as direct deps (deptry)

The cloud-auth code imports jwt and fastapi_users_db_sqlalchemy directly
but they were only transitive deps (via fastapi-users), which deptry
(quality gate, DEP003) rejects. Declared explicitly; deptry roboco/ clean.
Missed originally because local make quality stopped at earlier gates
before reaching deptry.

* feat(x): gate mention replies behind ROBOCO_X_REPLIES_ENABLED (default off)

Per CEO decision: the X engine should only post about releases by
default. Reading mentions needs a paid X API tier, so the mention-reply
half is now a deliberate opt-in on top of release posting.

New default-off flag x_replies_enabled gates the mentions poll loop
(_x_mentions_poll_loop) and XEngine.run_cycle; release-post drafting
(the release-proposal approve hook) is unaffected and still runs when
x_engine_enabled + credentials are set. Added to FEATURE_FLAGS + the
panel card. Tests: release posting works with replies off; run_cycle +
the poll loop are no-ops with replies off.

* fix: 401 only redirects to /login when cloud auth is on; panel-token strips .env quotes

Two bugs that together dead-ended login in secure mode:
- client.ts redirected to /login on ANY 401, so a mismatched panel
  token (header-trust/secure mode, cloud auth off) bounced the user to a
  login page whose backend route isn't mounted -> 404. Now it probes
  /auth/status (bare fetch, no interceptor re-entry) and only redirects
  when cloud_auth_enabled.
- make panel-token read the .env secret with grep|cut without stripping
  surrounding quotes, so a quoted ROBOCO_AGENT_AUTH_SECRET produced a
  token signed with the quotes included — which never verifies against
  the orchestrator (docker-compose/pydantic unquote the secret). Now
  strips surrounding single/double quotes.

* fix: git-log 500 on '|' in commit message; X queue shows an empty state

- GET /api/git/log 500'd (ValueError: Invalid isoformat) when a commit
  SUBJECT contained a '|' (e.g. the 'curl|sh' lockdown commit): the
  fixed '|' field delimiter let the subject's pipe shift the split so
  author+date collapsed into one field. Switched to \x1f (Unit
  Separator), which can't appear in commit content. Regression test with
  a piped subject.
- The X Post Queue returned null when empty, so there was no visible
  place for the X drafts. It now renders a discoverable empty state
  pointing at Settings -> X credentials.

* docs: bring docs/rag + docs/map current for v0.17.0 (waves 1-3)

Agent-facing RAG corpus and codebase map updated for every feature in
the 0.17.0 span, code-verified:
- wave 3: sandbox DB, DB network isolation, cloud auth, X engine
  (+ x_replies_enabled sub-flag), board roadmap engine — new RAG
  architecture pages + role/tool/config-reference updates; new symbols,
  migrations 057-059, panel surfaces, and the get_agent_context
  dual-path across the map slices.
- waves 1-2: A2A live view + switchboard, prompter memory
  (search_past_tasks), Secretary edit access + PM-lighter scope, the
  PR-gate auto-submit turn cut (ROBOCO_PR_GATE_AUTO_SUBMIT_ENABLED).
- correctness fix: api-routes-schemas.md no longer claims the A2A admin
  routes are reachable by any authenticated agent — they carry a
  _require_ceo gate (wave 2c).

docs/internal, _front.md deltas, and the frozen _complete_map.md
snapshot untouched.

* fix(rag): atomic upsert for indexed-doc tracking (kills e2e segfault)

The indexed-document tracking write used check-then-insert in two paths
(IndexedDocumentRepository.upsert_batch and the file-source
_upsert_doc_record). Under concurrent indexing both callers saw no row
and both inserted, so the second violated uq_indexed_doc_source and
poisoned its transaction — surfacing in CI as the intermittent
_checkin_failed SIGSEGV on the failed connection's pool checkin.

Both paths now use INSERT ... ON CONFLICT DO UPDATE against the
constraint: coalesce keeps an existing title/preview when the new value
is empty (matching the old guards) and metadata is jsonb-merged. The
batch dedupes within itself first (ON CONFLICT can't touch a row twice
in one statement). expire_all after the Core upsert keeps same-session
ORM reads consistent with the merged DB row.

---------

Co-authored-by: Renn F <rennf93@users.noreply.github.com>
2026-07-03 19:24:00 +02:00

18 KiB

Configuration Reference

Environment variables for RoboCo (prefix: ROBOCO_).

API Server

Variable Default Description
ROBOCO_HOST 127.0.0.1 API host (0.0.0.0 for containers)
ROBOCO_PORT 8000 API port
ROBOCO_DEBUG false Debug mode
ROBOCO_ENVIRONMENT development development/staging/production

Database

Variable Default Description
ROBOCO_DATABASE_HOST localhost PostgreSQL host
ROBOCO_DATABASE_PORT 5432 PostgreSQL port
ROBOCO_DATABASE_USER roboco Database user
ROBOCO_DATABASE_PASSWORD roboco Database password
ROBOCO_DATABASE_NAME roboco Database name

Redis

Variable Default Description
ROBOCO_REDIS_HOST localhost Redis host
ROBOCO_REDIS_PORT 6379 Redis port
ROBOCO_REDIS_DB 0 Redis database

Workspaces

Variable Default Description
ROBOCO_WORKSPACES_ROOT /data/workspaces Root for agent workspaces
ROBOCO_WORKSPACE_AUTO_CLONE true Auto-clone on first access
ROBOCO_WORKSPACE_CLONE_TIMEOUT 300 Clone timeout (seconds)

RAG/Embeddings

Variable Default Description
ROBOCO_DEFAULT_EMBEDDING_MODEL qwen3-embedding:0.6b Embedding model
ROBOCO_EMBEDDING_DIMENSIONS 1024 Embedding dimensions
ROBOCO_RAG_CHUNK_STRATEGY fixed fixed/semantic/hierarchical/contextual
ROBOCO_RAG_CHUNK_SIZE 512 Base chunk size
ROBOCO_RAG_CHUNK_SIZE_DOCS 1536 Chunk size for docs
ROBOCO_RAG_CHUNK_SIZE_JOURNALS 1024 Chunk size for journals
ROBOCO_RAG_CHUNK_OVERLAP 128 Chunk overlap
ROBOCO_RAG_USE_HYBRID_SEARCH true BM25 + vector search
ROBOCO_RAG_USE_CROSS_ENCODER true Neural reranking
ROBOCO_RAG_AUTO_UPDATE_ENABLED true Auto-update indexes
ROBOCO_RAG_AUTO_UPDATE_INTERVAL 300 Update interval (seconds)

LLM

Variable Default Description
ROBOCO_LOCAL_LLM_MODEL glm-5.2:cloud Local LLM for RAG
ROBOCO_LOCAL_LLM_BASE_URL http://roboco-ollama:11434/v1 OpenAI-compat API
ROBOCO_OLLAMA_BASE_URL http://roboco-ollama:11434 Native Ollama API

Grok provider (xAI)

Agents whose provider is GROK run xAI's official grok CLI. Auth is the host SuperGrok subscription (mounted ~/.grok), not a metered API key.

Variable Default Description
ROBOCO_HOST_GROK_DIR ~/.grok Host dir holding auth.json, mounted into Grok agents; the orchestrator auto-refreshes the ~6h token in place. Set up once with grok login.
ROBOCO_GROK_CLI_MODEL grok-build Grok CLI model id
ROBOCO_GROK_AGENT_IMAGE roboco-agent-grok:latest Image for Grok delivery agents
ROBOCO_GROK_REASONING_EFFORT (blank) Per-run reasoning-effort override; blank = the grok CLI default
ROBOCO_GROK_IDLE_KILL_SECONDS 900 Kill + evict a Grok container that has been ACTIVE-yet-idle (no gateway verb) this long
ROBOCO_GROK_MAX_COST_USD 0.0 Per-agent Grok cost ceiling (USD); 0 disables

Feature flags

Env-gated subsystems. Most are default-off; ROBOCO_OVERLOAD_BREAK_ENABLED, ROBOCO_RESEARCH_ENABLED, ROBOCO_PROVISIONING_ENABLED, and ROBOCO_PR_GATE_AUTO_SUBMIT_ENABLED ship default-on. Each takes effect on the next backend restart; the panel's Settings → Feature Flags card toggles the panel-exposed ones (roboco/services/settings.py's FEATURE_FLAGS) without hand-editing env — a few security/topology flags below are env-only by design and are called out as such.

Variable Default Description
ROBOCO_CONVENTIONS_ENABLED false Architectural Conventions Standard: auto-scaffold .roboco/conventions.yml, inject the architecture map, attach baseline constraints, and block i_am_done / pr_pass on block-level placement and hygiene violations. Off = fully inert.
ROBOCO_TOOLCHAIN_MATCH_ENABLED false Provision each agent workspace with the target project's Python (resolved from its requires-python / .python-version) and block delivery gates when the suite cannot be executed under it. Off = today's behavior.
ROBOCO_OVERLOAD_BREAK_ENABLED true Park a provider on a persistent model-API overload (HTTP 529 / 500 / 503) the same way a 429 is parked — queue its spawns and probe until it recovers — instead of crash-retrying into the overload. Off = crash-retry behavior.
ROBOCO_PR_GATE_AUTO_SUBMIT_ENABLED true PR-gate turn cut: when every child of an assembled parent is terminal, run the real submit_up / submit_root system-side as the owning PM (_try_auto_submit) instead of spawning the PM for that turn — the submit's substance (freshness rebase, integrity check, PR open) is deterministic gate code. A gate rejection falls back to the classic PM closure spawn; the PM keeps the judgment turns (merge, revision). Each auto-submit leaves a task.auto_submitted audit row. Off = every closure spawns the PM to submit.
ROBOCO_SPAWN_PREFLIGHT_ENABLED false Refuse to spawn a non-human delivery role absent from GATEWAY_ENABLED_ROLES (no manifest → can never claim → would respawn on the same task forever); refuse + alert the overseer once instead. Inert in practice (all delivery roles are gateway-enabled). Armed on the NAS composes.
ROBOCO_NOTIFICATION_SPAWN_COOLDOWN_SECONDS 600 Cross-tick damper for notification-triggered spawns (escalation/approval/audit/a2a — task-less, so the readiness gate and respawn breaker never see them): one spawn per (agent, notification) per window; the notification stays pending so the next window retries. 0 = legacy every-tick respawn.
ROBOCO_SANDBOX_DB_ENABLED false Sandboxed per-agent-spawn test DB/Redis: throwaway postgres:16-alpine / redis:8-alpine sibling containers, per-project opt-in. See "Sandboxed Dev DB/Redis" below and docs/rag/architecture/sandbox-db.md.
ROBOCO_X_ENGINE_ENABLED false The X (Twitter) engine: draft release/mention posts, ALL held for per-post CEO approval. See "X (Twitter) Engine" below and docs/rag/architecture/x-engine.md.
ROBOCO_ROADMAP_ENGINE_ENABLED false The board roadmap engine: weekly Product-Owner-authored cycle, CEO approves each item individually into BACKLOG. See "Board Roadmap Engine" below.

The company-in-a-box subsystems toggle the same way: web research (ROBOCO_RESEARCH_ENABLED, default on — see "Web Research" below), the strategy engine (ROBOCO_STRATEGY_ENGINE_ENABLED, default off), and pitch provisioning (ROBOCO_PROVISIONING_ENABLED, default on but inert without a token/org configured).

Web Research

Pluggable external search/fetch for the Board + PM roles (cell_pm, main_pm, product_owner, head_marketing). Calls flow agent → roboco-search MCP → /api/research/*ResearchService → provider; the provider key lives only in the server-side process — it is never injected into an agent container, and agents never egress (the provider's own API does). See docs/rag/tools/research-tools.md for the web_search / web_fetch tool contract.

Variable Default Description
ROBOCO_RESEARCH_ENABLED true Master switch. Ships default-on (unlike most feature flags): the roboco-search MCP server is mounted for the four research roles unless explicitly disabled. Panel-toggleable. Both NAS composes also set ROBOCO_RESEARCH_ENABLED:-true explicitly (redundant with the code default, but keeps the deploy's env self-documenting).
ROBOCO_RESEARCH_PROVIDER tavily Adapter: tavily (LLM-native cited results + extract), brave (independent index, no fetch endpoint), exa (neural search + contents), or null (always-empty stub). Swapping providers is a config change only.
ROBOCO_RESEARCH_API_KEY (unset) API key for the selected provider. Server-side only. Unset ⇒ graceful NullProvider (empty results, never a hard fail).
ROBOCO_RESEARCH_MAX_RESULTS 5 Hard cap (1-20) on web_search results per call.
ROBOCO_RESEARCH_FETCH_MAX_CHARS 20000 Hard cap on characters web_fetch returns; content past this is truncated.
ROBOCO_RESEARCH_TIMEOUT_SECONDS 15.0 Per-request timeout for outbound provider HTTP calls.
ROBOCO_RESEARCH_DAILY_QUOTA_PER_AGENT 50 Max web_search + web_fetch calls per agent per UTC day. Tracked in Redis; fails open (allows the call) if Redis is unreachable.

Self-Healing CI loop

RoboCo watching its own repo's CI. All default-off / dormant.

Variable Default Description
ROBOCO_SELF_HEAL_ENABLED false Master switch (detect + notify the CEO); off = the loop never runs and no CI is fetched
ROBOCO_SELF_HEAL_ORIGINATE_ENABLED false Second opt-in: also open a PENDING fix task on a regression — CEO-gated, never auto-started/merged/deployed
ROBOCO_SELF_HEAL_PROJECT_SLUG (empty) The registered project that IS RoboCo itself — the only repo it watches and fixes; empty = no-op
ROBOCO_SELF_HEAL_CI_WORKFLOW (empty) GitHub Actions workflow to scope the CI signal to (e.g. ci.yml); empty = latest across all workflows
ROBOCO_SELF_HEAL_INTERVAL_SECONDS 1800 Seconds between assessment passes
ROBOCO_SELF_HEAL_MAX_OPEN_TASKS 3 Rolling cap on concurrently-open self-heal tasks
ROBOCO_SELF_HEAL_MAX_PER_CYCLE 1 Max fix tasks originated per cycle

Autonomous maintenance

The fan-out generalizations of self-heal — they watch any opted-in project, not just RoboCo's own. All default-off; neither ever auto-merges (every task rides the normal delivery + PR-review gate). Per-project opt-in lives on the project row (set in the panel's edit-project dialog), not in env.

Variable Default Description
ROBOCO_CI_WATCH_ENABLED false Master switch for multi-repo CI-watch; off = the loop never runs. Per-project opt-in via projects.ci_watch_enabled
ROBOCO_CI_WATCH_DEFAULT_WORKFLOW ci.yml Workflow file the CI signal is scoped to when a project sets no ci_watch_workflow
ROBOCO_CI_WATCH_INTERVAL_SECONDS 1800 Seconds between CI-watch passes
ROBOCO_CI_WATCH_MAX_OPEN_TASKS 3 Rolling cap on concurrently-open ci_watch tasks
ROBOCO_CI_WATCH_MAX_PER_CYCLE 1 Max ci_watch fix tasks originated per cycle
ROBOCO_DEP_UPDATE_ENABLED false Master switch for the dependency-update bot; off = the loop never runs. Per-project opt-in via projects.dep_update_command
ROBOCO_DEP_UPDATE_INTERVAL_SECONDS 604800 Seconds between dependency-update passes (default weekly)
ROBOCO_DEP_UPDATE_MAX_OPEN_TASKS 3 Rolling cap on concurrently-open dep_update tasks
ROBOCO_DEP_UPDATE_MAX_PER_CYCLE 1 Max dep_update tasks originated per cycle
ROBOCO_RELEASE_MANAGER_ENABLED false Master switch for the gated release manager; off = the loop never runs. Even on it only PROPOSES — the CEO approves before any publish
ROBOCO_RELEASE_MIN_COMMITS 8 Minimum unreleased commits since the last tag before a release is proposed (a feat/security change also qualifies)
ROBOCO_RELEASE_MANAGER_INTERVAL_SECONDS 3600 Seconds between release-readiness assessment passes
ROBOCO_ORG_MEMORY_ENABLED false Master switch for the org-memory loop (distill at completion, index journals, auto-inject lessons/playbooks); off = legacy capture, no inject
ROBOCO_ORG_MEMORY_TOP_K 3 Max institutional-memory items injected into a briefing on claim
ROBOCO_ORG_MEMORY_MIN_SCORE 0.6 Cosine-similarity floor for injected memory; below it nothing is injected
ROBOCO_IMAGE_PRUNE_ENABLED true Background sweep prunes dangling (<none>) Docker images from agent-image rebuilds (only dangling; ~6h throttle). Always-on safety net, not a feature flag
ROBOCO_IMAGE_PRUNE_INTERVAL_SECONDS 21600 Minimum seconds between dangling-image prune passes

Sandboxed Dev DB/Redis

Per-agent-spawn throwaway Postgres/Redis, replacing (never coexisting with) the legacy prod-creds gate-env injection for an opted-in project. Default-off; see docs/rag/architecture/sandbox-db.md.

Variable Default Description
ROBOCO_SANDBOX_DB_ENABLED false Master switch. Off = spawning behaves exactly as today (the legacy _append_gate_env prod-creds injection, itself gated by ROBOCO_TOOLCHAIN_MATCH_ENABLED). Only projects with their sandbox_services column set (migration 057) participate even when on.

X (Twitter) Engine

Drafts release-announcement and mention-reply posts, ALL held for per-post CEO approval — nothing ever posts automatically. Default-off; see docs/rag/architecture/x-engine.md.

Variable Default Description
ROBOCO_X_ENGINE_ENABLED false Master switch. Off = no draft is originated and no X API call is ever made. Even on, posting requires stored credentials (panel-entered) AND an explicit per-post CEO approval.
ROBOCO_X_REPLIES_ENABLED false Sub-switch for the mention-reply half. Off (even with the engine on) = the engine only drafts release-announcement posts; it never polls mentions or drafts replies. Reading mentions needs a paid X API tier, so replies are a deliberate opt-in on top of release posting.
ROBOCO_X_MENTIONS_INTERVAL_SECONDS 1800 Seconds between mentions-poll passes (only when X_REPLIES_ENABLED).
ROBOCO_X_MENTIONS_MAX_PER_CYCLE 5 Max held reply proposals the mentions poll may originate in one cycle.
ROBOCO_X_MENTIONS_MIN_ENGAGEMENT 0 Minimum like+reply+retweet count for a mention to count as "meaningful" (the engagement half of the mention filter; the other half rejects bare retweets and near-empty text).
ROBOCO_X_MAX_OPEN_POSTS 10 Rolling cap on concurrently-open held X posts/replies (both sources combined); the engine originates nothing more past it.
ROBOCO_X_ACCOUNT_USER_ID (empty) Numeric X user id of the account's own account. Empty resolves it once per mentions cycle via GET /2/users/me (one extra call).
ROBOCO_X_REQUEST_TIMEOUT_SECONDS 15.0 Per-request timeout for outbound X API HTTP calls.

Board Roadmap Engine

Weekly, the Product Owner explores the company's projects and proposes a themed cycle of roadmap item drafts; the CEO approves or rejects each one individually. Default-off; approved items land in BACKLOG and nothing auto-starts. See docs/rag/architecture/company-layer.md.

Variable Default Description
ROBOCO_ROADMAP_ENGINE_ENABLED false Master switch. Off = no exploration cycle is originated and the Product Owner is never spawned for this.
ROBOCO_ROADMAP_INTERVAL_SECONDS 604800 Seconds between roadmap-exploration cycles (default weekly).
ROBOCO_ROADMAP_MIN_ITEMS_PER_CYCLE 3 Minimum roadmap item drafts a themed cycle must propose.
ROBOCO_ROADMAP_MAX_ITEMS_PER_CYCLE 7 Maximum roadmap item drafts a themed cycle may propose.

No dedicated migration — a cycle is marker-backed (orchestration_markers on the held exploration task), not a new table.

Cloud Auth

Not a panel feature flag — unlike the flags above, ROBOCO_CLOUD_AUTH_ENABLED is env-only (deliberately absent from roboco/services/settings.py's FEATURE_FLAGS, so it can't be flipped on for a deployment that isn't behind TLS). Lets the panel/API be exposed beyond localhost without changing the CEO's local no-login flow while off. See docs/rag/architecture/cloud-auth.md.

Variable Default Description
ROBOCO_CLOUD_AUTH_ENABLED false Master switch. Off: get_agent_context behaves byte-for-byte as today (header-trust). On: no registration router is mounted — exactly one user, seeded from cloud_auth_email / cloud_auth_password. Fails loud at startup (raises before the app boots) if true without ROBOCO_CLOUD_AUTH_SECRET set.
ROBOCO_CLOUD_AUTH_EMAIL (unset) Email for the single seeded CEO login user.
ROBOCO_CLOUD_AUTH_PASSWORD (unset) Password for the single seeded user. Hashed at startup; never stored in plain text.
ROBOCO_CLOUD_AUTH_SECRET (unset) Session-signing secret for the login cookie's JWT. Required when enabled — generate with python -c 'import secrets; print(secrets.token_hex(32))'.
ROBOCO_CLOUD_AUTH_COOKIE_MAX_AGE 2592000 Session cookie lifetime in seconds (30 days). Sliding: every authenticated request re-mints + re-sets the cookie, so an active session never expires — only genuine inactivity past this window logs out.

The session cookie is secure-only (cookie_secure=True in roboco/api/auth/backend.py) — arm this flag only behind TLS, or the browser will silently refuse to send the cookie and login will appear to fail.

DB Network Isolation

Not a panel feature flagROBOCO_DB_NETWORK_ISOLATED must travel with the compose file's networks: stanzas (it describes topology, not a runtime-toggleable behavior), so it is env-only like ROBOCO_CLOUD_AUTH_ENABLED.

Variable Default Description
ROBOCO_DB_NETWORK_ISOLATED false Set true by the compose files that put postgres/redis on the data-only roboco_data network agents never join. Suppresses the legacy _append_gate_env prod-creds injection (unreachable creds are worse than none) — DB-needing projects use the sandbox opt-in instead.

Security

Variable Default Description
ROBOCO_ENCRYPTION_KEY (required) Fernet key that encrypts secrets at rest (e.g. per-project git tokens, the x_credentials OAuth 1.0a singleton row). Generate with Fernet.generate_key().
ROBOCO_AGENT_AUTH_SECRET (required) HMAC secret the orchestrator signs each agent's X-Agent-Token with.
ROBOCO_AGENT_AUTH_REQUIRED false When true, every request must carry a valid agent token (secure mode).
ROBOCO_PANEL_AGENT_TOKEN (unset) The control panel's CEO token, injected by nginx in secure mode. Get it with make panel-token.

ROBOCO_ENCRYPTION_KEY also encrypts the x_credentials row (the four X/Twitter OAuth 1.0a secrets) — the same key, one more consumer.