new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

AI SDK · Providers · all subjects

codex-app-server/options

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Codex App Server settings interface

CodexAppServerSettings interface includes: codexPath (optional string), cwd (optional string), approvalMode (optional 'never' | 'on-request' | 'on-failure' | 'untrusted'), sandboxMode (optional 'read-only' | 'workspace-write' | 'danger-full-access'), reasoningEffort (optional 'none' | 'low' | 'medium' | 'high'), threadMode (optional 'persistent' | 'stateless'), mcpServers (optional Record<string, McpServerConfig>), verbose (optional boolean), logger (optional Logger or false), onSessionCreated (optional callback function), env (optional Record<string, string>), baseInstructions (optional string), and resume (optional string for thread ID to resume).

Codex App Server thread modes

Two thread modes are available: 'persistent' (default) which reuses the same thread across calls to maintain context, and 'stateless' which creates a fresh thread for each call.

Codex App Server per-call setting overrides

Settings can be overridden per call using providerOptions with the key 'codex-app-server'. For example, reasoningEffort and threadMode can be set individually for each streamText call.

Give your agent this brain