quickstart.md

type	Reference
title	OpenWiki quickstart
description	Task entrypoints for current native conversations, account routing, product scope and evidence.
tags	decodex architecture
sources	id resource openwiki-source-d700ef551f46158044378d8f repo://apps/decodex-cli/src/lib.rs id resource openwiki-source-ec2c431b14759817413ba09e repo://apps/decodex-gpui/src/agent_graph.rs id resource openwiki-source-51a4755f3c4ddd78511e5c8e repo://apps/decodex-gpui/src/agent_tree.rs id resource openwiki-source-14193a66abfb7d3230f476bf repo://automations/portfolio.toml id resource openwiki-source-cc0439b23243c3697ba49199 repo://crates/decodex-protocol/src/lib.rs id resource openwiki-source-f4724776aade804ebf838e2e repo://crates/decodex-runtime/src/account_service.rs id resource openwiki-source-a67672a943dfe221574b2501 repo://crates/decodex-runtime/src/shared_auth_coordinator.rs id resource openwiki-source-601aed9bf7f72a4b5d4a6e78 repo://database/src/migrations.rs id resource openwiki-source-3b57179b92b257bc3fff51a1 repo://scripts/macos/stage_decodex_app.sh
generated	by at codex 2026-10-17T07:29:15.006Z
verified	by at openwiki/0.7.2 2026-10-17 07:29:15 UTC

OpenWiki quickstart

Decodex is a local workspace above Codex app-server. The primary Agent can discuss work, act directly, or coordinate other agents. Codex owns native conversation execution. Decodex owns local work relationships, account policy, recovery and presentation. “Chief” in older filenames and records is the former Agent name.

Start by task

Task	Read first
Understand service, clients and storage	Runtime architecture
Trace Agent coordination and native children	Agent coordination
Change conversation layout, loading or motion	Conversation presentation, Desktop workspace
Change input, branches, drafts, read state, export or recap	Conversations and recovery
Change model, effort, Goal, search or native launch defaults	Models and settings
Handle an approval or provider question	Approvals and ownership
Use native skills or understand plugin and connection ownership	Tools and integrations
Change dictation, live voice or voice preferences	Subscription voice
Import OAuth/PAT accounts or diagnose routing and activation	Accounts and routing
Diagnose storage	Local database
Decide which upstream capabilities belong here	Product scope
Review an upstream change	Upstream maintenance
Choose checks and understand their limits	Commands, acceptance boundaries
Improve tests without weakening contracts	Test quality
Maintain documentation	Wiki maintenance

Current boundaries

• decodex serve is the service and SQLite product-state owner. GPUI and CLI use typed local clients. The bundled helper is decodex, not decodexd.
• The protocol crate’s CURRENT_VERSION and the embedded migration ledger define compatibility. Read these owners instead of copying version numbers into operational instructions.
• The Agent graph presents dependencies and reports; the separate tree presents parent ownership. Historical Factory diagrams do not define the current desktop.
• Account Route is synchronous and service-owned. Shared-auth liveness, exact source identity and readback govern completion. Same-account refresh adopts a valid non-older native winner instead of restoring a losing token.
• Unknown submission outcomes require exact receipts or native history. They do not authorize replay. Unavailable conversations keep readable history.
• Local plugin management and embedded MCP HTML widgets are retired. Codex owns configuration and native execution; Decodex retains tool observations, native forms and readable history.
• The checked-in automation portfolio marks the upstream maintainer ACTIVE. This is configuration evidence, not scheduler readback. Documentation generation does not enable automations, install an app or publish a release.

Build and evidence

Use stable Rust and the repository-owned commands. macOS packaging uses the selected Xcode installation or an explicit DEVELOPER_DIR. A unit test, native fixture, signed desktop check, merge and installation prove different things. Keep version-specific limits visible.

Maintain documentation through OpenWiki. Consolidate by current system behavior and reader tasks; do not recreate a page for each retired document. Previous plans and revision-specific receipts remain in Git history. They are not a current work queue.