Skip to content

docs: fix remaining operator-doc mismatches vs code - #224

Merged
molty3000 merged 4 commits into
mainfrom
cursor/docs-accuracy-3fe1
Sep 9, 2026
Merged

docs: fix remaining operator-doc mismatches vs code#224
molty3000 merged 4 commits into
mainfrom
cursor/docs-accuracy-3fe1

Conversation

@jkyberneees

@jkyberneees jkyberneees commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Adversarial accuracy pass over the remaining operator docs (MCP.md was already rewritten in #223), plus the three wiring gaps that pass uncovered.

Docs that had drifted

  • odek continue sandbox — no --no-sandbox flag; project sandbox: false ignored. Override is trusted "sandbox": false or ODEK_SANDBOX=false. ODEK_NO_SANDBOX=1 does not override a sandboxed session. Continue pins the session bit; it is not a new default-on like run/repl/serve.
  • Docker missingrun/repl implicit default-on degrades; serve and a sandboxed continue hard-fail.
  • non_interactive, approvals, events, plan UI, memory search, serve.log, compose nested Docker, SDK []session.Message, go install @latest, schedule delegate_tasks — as in earlier commits.

Implementation gaps closed in this PR

  • Serve / Telegram compactionresolved.Compaction is now copied onto odek.Config (was library default off while config/API showed on). Serve also accepts --no-compaction.
  • Telegram TrustallowTrustForClass now calls danger.TrustShortcutAllowed, so persistence and unread_exec cannot be session-trusted (forged Trust is denied).

Small code/docs-adjacent extras from the accuracy pass

  • odek init local template no longer includes operator-only subagent / schedules.max_concurrent / catchup.
  • Plan tool schema description matches validation (unknown id/status).
  • Config.EventHandler comment lists the subagent event types.

Last review (this revision)

Dropped leftover “continue is default-on” wording in SANDBOXING / CHEATSHEET / CONFIG / GETTING_STARTED, tightened the compaction assignment pin, and pointed go install at v2.11.2.

Left as documented limitations (not this PR)

Budgets still apply only to odek run / odek subagent. Telegram still does not start a sandbox container.

Open in Web Open in Cursor 

Correct claims that had drifted from current behavior: continue sandbox
pinning (no --no-sandbox flag; project sandbox:false ignored),
non_interactive enum, Telegram trust/friction vs TTY, schedule floor,
serve @-resources and compaction wiring, event data fields, plan UI
polling, memory search defaults, serve.log rotation, and the local init
template so odek init stays warning-free.

Co-authored-by: admin <admin@21no.de>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 9, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
odek b387733 Commit Preview URL

Branch Preview URL
Sep 09 2026, 10:08 AM

@jkyberneees
jkyberneees marked this pull request as ready for review September 9, 2026 09:15
cursoragent and others added 3 commits September 9, 2026 09:31
ODEK_NO_SANDBOX does not override a sandboxed continue pin (only
ODEK_SANDBOX=false / trusted config set SandboxExplicit first). Sandboxed
resume and odek serve hard-fail without Docker. Schedule still registers
delegate_tasks. Web UI friction is typed approve + 1.5s; Telegram Trust
is still offered for persistence/unread_exec.

Co-authored-by: admin <admin@21no.de>
Serve and Telegram now copy resolved.Compaction onto odek.Config so
rolling compaction matches run/repl/schedule. Serve accepts
--no-compaction. Telegram Trust uses danger.TrustShortcutAllowed, so
persistence and unread_exec cannot be session-trusted.

Co-authored-by: admin <admin@21no.de>
Continue pins the session sandbox bit; it is not a new default-on like
run/repl/serve. Tighten the compaction wiring pin to the assignment line
and point go install at the forthcoming v2.11.2 tag.

Co-authored-by: admin <admin@21no.de>
@molty3000
molty3000 merged commit 118eb45 into main Sep 9, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants