Build with Magic Coder
The “Build with Magic Coder” section is for extending the agent — building hooks, plugins, MCP integrations, custom subagents, and the like. Most of these surfaces are still in design or implementation today, but a few are already real.
What works today
Section titled “What works today”- Authoring skills — write a
SKILL.mdunder<workspace>/.magic/skills/or~/.magic/skills/and it appears as a slash command. See Skills. - Authoring rules — write Markdown rules under
<workspace>/.magic/rules/or~/.magic/rules/to give the agent guidance loaded either always or on demand. See Rules.
What’s coming
Section titled “What’s coming”- Hooks — run shell commands at lifecycle points (session start, before tool use, after edit, etc.).
- Plugins and Create plugins — packaging custom commands and tools as installable bundles.
- Plugin marketplace — discover and install plugins published by the community or by your team.
- MCP servers — connect external tool servers via the Model Context Protocol.
- Custom subagents — Magic Coder already dispatches ad-hoc subagents when a task calls for it; declarative definitions are coming soon.
- Skills authoring — cloud-managed and shareable skill distribution beyond local files.
- Output styles and Status line — surface customization.
- Sandboxing — opt-in execution boundaries beyond the current trust/permission model.
- Scheduled prompts and Push external events — driving Magic Coder from outside the user’s keyboard.
- Programmatic usage — using Magic Coder from scripts, CI, and SDKs.
Where day-to-day docs live
Section titled “Where day-to-day docs live”The user-facing surface is documented under Using Magic Coder. For extension authors, this section will keep filling in over the next few releases.
If a feature you need is on this page and you’d like to use it ahead of public availability, ask in your BridgeApp workspace.