GitHub Copilot
GitHub Copilot is available in VS Code, JetBrains IDEs, and the terminal via the gh copilot extension. devai:install configures it with workspace instructions and MCP server registration.
Prerequisites
Section titled “Prerequisites”- GitHub Copilot subscription active on your GitHub account
- VS Code with the GitHub Copilot extension, or a JetBrains IDE with the Copilot plugin
marko/devaiinstalled (see Installation)
What devai:install writes
Section titled “What devai:install writes”Running marko devai:install with Copilot detected produces the following files:
.github/copilot-instructions.md # Workspace-level guidelines for Copilot Chat.vscode/mcp.json # MCP server registration (marko mcp:serve)AGENTS.md # Shared guidelines file (devai-managed marker block)Copilot does not implement LSP registration and no skills are distributed for Copilot.
copilot-instructions.md
Section titled “copilot-instructions.md”The .github/copilot-instructions.md file is read by Copilot Chat for every workspace session. The installer writes merged Marko guidelines inside a <!-- BEGIN/END marko:devai --> marker block, so your own edits outside the markers survive re-runs (see Editing generated files):
- Module structure and naming conventions
- Available MCP tools
- Project-specific guidelines from every installed package’s
resources/ai/guidelines.md
MCP registration
Section titled “MCP registration”The .vscode/mcp.json file registers marko mcp:serve as an MCP server using the servers key (not mcpServers). Each entry includes a type field for the transport. Copilot Chat’s agent mode can call tools like find_event_observers and validate_module when answering questions about your project.
AGENTS.md
Section titled “AGENTS.md”devai:install writes the shared AGENTS.md guidelines inside a <!-- BEGIN/END marko:devai --> marker block: created if absent, and on later runs only the marked region is refreshed, so content you add outside the markers is preserved. Remove the markers to take full ownership — devai then leaves the file alone. See Editing generated files.
Manual verification
Section titled “Manual verification”- Open your project in VS Code with Copilot enabled.
- Open Copilot Chat and ask:
What Marko MCP tools are available? - In agent mode, ask:
Search Marko docs for "dependency injection"—search_docsshould run and return results if a docs driver is installed. - Check that
.github/copilot-instructions.mdexists and.vscode/mcp.jsonuses theserverskey.
Agent-specific tips
Section titled “Agent-specific tips”- Agent mode: MCP tool calls require Copilot Chat to be in agent mode (
#agent). Switch to it by clicking the agent icon in the chat panel. gh copilot: The terminal extension does not yet support MCP. Guidelines fromcopilot-instructions.mdare not loaded in the terminal context.