Skip to content

Core concepts

APEX stores task ownership, procedures, authoring rules, and configuration in different files. Knowing which file owns a decision makes changes easier to review.

An agent definition describes a role, selected model, allowed tools, and handoff targets. Its body defines the task, expected output, and stop conditions. Main agents live under .github/agents/; helpers live under _subagents/.

You select main agents in Copilot Chat. Production main agents use disable-model-invocation: true. A helper allowlist must not turn a main agent into a nested worker.

A skill provides a procedure and supporting reference material in .github/skills/{name}/SKILL.md. References and templates load when the task needs them. A skill does not choose a different agent or grant permission to use tools.

Discovery depends on the client, configuration, and skill metadata. If a required skill did not load, the agent must read it explicitly rather than assume the procedure is already in context.

Instruction files under .github/instructions/ describe rules for a declared file scope. Their applyTo patterns express intended matching behavior. A matching authoring file does not prove that the instruction attached during every runtime operation.

Keep essential approval, output, security, and stop rules in the main agent’s instructions. Use validators where a rule can be checked deterministically, and verify runtime behavior separately.

FilePurpose
tools/registry/agent-registry.jsonAgent paths, roles, and source metadata
.github/skills/apex-workflow-engine/templates/workflow-graph.jsonStep dependencies, gates, artifacts, and review defaults

The Architecture Explorer displays metadata generated from the product revision pinned by this site. It does not query a running agent session.

The product’s root AGENTS.md introduces repository structure, commands, conventions, and workflow boundaries. Follow its references for detailed domain procedures rather than copying them into each agent.

The product’s .github/copilot-instructions.md supplies repository-wide guidance and links to the relevant customization files. This documentation repository has its own instructions for writing and validation. They are not interchangeable.

Tools perform operations such as reading a file, running a validator, or querying Azure pricing. Tool availability and authentication are distinct from authorization for a particular action.

The configured integrations include workspace stdio Azure MCP (including retail pricing), hosted Azure Resource Manager MCP for cost queries, and GitHub MCP. The old custom Python pricing server is not the current integration.

See MCP integration for configuration and access requirements, and skills and instructions for authoring guidance.