Start with the goal that matches what you are trying to do.
- README — what WebCodex does and how to choose a setup
- Unified installation — persistent main-node and multi-computer setup; check deployment validation before choosing an installer
- Runtime installation and CLI join — headless Linux Runner setup and package update/recovery
- Desktop installation — release-specific Windows/macOS installation and OpenAI Secure Tunnel details
- Using Desktop — projects, device invitations, connections, activity, and service controls
- Desktop Runtime compatibility — Runtime selection, diagnostics, updates, and rollback
- Runtime Console — browser activity, projects, Sessions, and Agent communication
- Full Setup — CLI, existing Server, Linux, and advanced regular Server + Runner setup
- AI-assisted setup — have an AI agent configure WebCodex using ordinary user language
- MCP — ChatGPT, Claude, and other MCP clients
- Session continuity — save context, continue across accounts/windows, and delegate model API reviews
- Quick Trial — temporarily try one repository with one
webcodex sharecommand
- Deployment — systemd/Docker, multi-user self-hosting, and long-lived operations
- Windows + OpenAI Secure MCP Tunnel deep dive — independent Windows Server/Runner, Tunnel setup, and real troubleshooting notes
- Runner — Runner operations reference
- CLI — full command, configuration, and credential reference
- MCP — Bearer, query-token fallback, OAuth, private tunnel, and MCP protocol reference
- Authentication — detailed credential and authority boundaries
- Deployment — stable HTTPS origins, self-hosting, and production networking
- Troubleshooting — ChatGPT/MCP Host, installation, connection, runtime, and Runner problems
- Security — safe operating guidance and security model
- Architecture — how the major components fit together
- Coding Workflow — task bootstrap, guidance, validation, and closeout
- Native Tool Plugins — add Runner-local tools with any executable language and no MCP SDK
- Computer Use roadmap — semantic-first desktop automation direction and validation priorities
- Browser/CDP runtime architecture — first-class Browser domain, authority, lifecycle, stale fencing, and Phase 1 limits
- Contributing — issue evidence, focused fixes, validation, and pull requests
- Desktop development — run Desktop from source and build/test local platform packages
- Sponsorship and project support — community sponsorship, infrastructure support, partnerships, and recognition principles
The references below cover repository policy and maintainer/internal contracts. The contract pages intentionally contain protocol fields, compatibility names, and implementation invariants that ordinary users should not need to learn.
- AGENTS.md — repository instructions for coding/AI agents
- Maintenance — maintenance queue, dependency cadence, PR/CI expectations, and bilingual-doc policy
- Testing — testing strategy
- Release checklist — release readiness
- Compatibility policy — supported published formats, upgrade bridges, and named protocol consumers
- Architecture decisions
- Tool contract guidelines — model-facing selection, authority, effects, continuation, and recovery
- Durable Agent runtime — durable identity and asynchronous work architecture
- Durable Agent/Conversation/Wake contract — current communication implementation
- Runtime host context — Runner-configured planning context and runtime diagnostics
- Job reliability and Runner concurrency — restart recovery, observation semantics, shared Job capacity, and tool-description requirements
- Tool request tracing — maintainer forensic payload/correlation contract
- Authority model
- Session model
- Manual multi-window collaboration
- Runtime API guidelines
- Release process