Developers
Project development, extension authoring, protocol integration, and standalone Evolver.
Develop projects in EvoX, author extensions, or integrate experience reuse into your own agent. Choose by deliverable: project development focuses on code and verification, extensions on tool contracts, and protocol integration on identity, execution state, and evidence.
Start with your goal
| Goal | Start here | Deliverable |
|---|
| Complete a task in an existing project | Develop in a project | A bounded code diff, verification records, and handoff notes |
| Inspect code changes | Code review and changes | Findings tied to files and lines, with supporting evidence |
| Turn repeatable work into a skill | Build skills | A skill with triggers, steps, and acceptance criteria |
| Add external tools to EvoX | Connect MCP tools | Discoverable, callable tools with explicit side effects |
| Inspect agent lifecycle extensions | Hooks | Configuration sources, event matching, and execution diagnostics |
| Let other agents reuse experience | Recipes and experience reuse | Traceable selection, execution, and outcome reporting |
| Run Evolver independently in a project or service | Installation and first run | A diagnosed and verified environment with a defined shutdown path |
Follow one path in order
- Develop your own project in Desktop: Develop in a project → use the terminal and worktrees as needed → review the diff and verify. Standalone Evolver installation is not a prerequisite.
- Build an extension or integrate experience: choose skills, MCP, or Hooks first. Use Evolver Proxy to expose experience to another agent. Complete a minimal invocation before adding writes, publishing, or resident operation.
- Operate Evolver or maintain source: installation and first run → review and validation → resident operation → maintenance. Consult repository boundaries when changing product source and release maintenance when producing installers.
Retain evidence for the chosen path: diffs and tests for projects, inputs, outputs, and failure cases for extensions, and status, logs, and shutdown checks for runtime instances. Follow your deliverable without configuring every technical capability first.
Development workflows
Projects provide task and code context. The integrated terminal runs commands, Git worktrees isolate working directories, and code review inspects the resulting diff. Check existing changes before defining write scope and verification commands; a completion message does not replace actual artifacts.
Extensions and protocols
Skills describe how to work, MCP exposes callable tools, and Hooks run configured handlers on agent events. Check inputs, permissions, and side effects separately; installing an extension does not authorize every operation.
Evolver Proxy exposes experience tools to other agents. This is the opposite direction from connecting MCP tools to EvoX. GEP schemas define assets; A2A and task network integration covers Hub identity, tasks, and submission protocols. Start with the Proxy for experience search and reuse.
Independent operation and product settings
Standalone Evolver has a separate path covering installation, review, queues, identity, strategy, publishing, and persistence. Configure the Desktop-managed environment separately from the independent CLI. Model, personalization, connection, and system settings belong in Configuration basics.
Before changing source
Use Architecture and source repositories to identify whether a deliverable belongs to Desktop, the core runtime, Evolver, or the website. Verify through the owning source, tests, and release artifacts; a documentation demo does not prove a product implementation.
With complete execution records, use Experience distillation to author Genes, Skills, or Recipes. To consume existing experience, start with Recipe reuse.
Standalone operations and release maintenance
For your own Evolver runtime, start with Nodes and runtime instances and Runtime policy and budgets, then review Network tasks. Installer producers use Software release maintenance. Desktop users can go directly to Administration.
