Skip to main content

Configure extensions

Current Phonton CLI releases inspect local .phonton records. They do not provide a public extension installer command in the v0.19.0 binary, so this page describes the file-based workflow.

Run commands from the root of the workspace that should receive the .phonton records.

Inspect a pack first​

Clone the repo when you want to review an extension before copying it:

git clone https://github.com/phonton-dev/phonton-review-gate-extension

Then copy the extension records into a workspace.

Windows PowerShell:

Copy-Item -Recurse .\phonton-review-gate-extension\.phonton .\.phonton
phonton extensions doctor

macOS or Linux:

cp -R phonton-review-gate-extension/.phonton ./.phonton
phonton extensions doctor

Inspect what loaded:

phonton extensions list
phonton extensions skills --json
phonton extensions steering --json
phonton extensions profiles --json

MCP records​

MCP records live in .phonton/mcp.toml or .phonton/mcp.d/*.toml.

After adding a manifest, inspect the configured servers and preview one server's capabilities:

phonton extensions mcp --json
phonton mcp list
phonton mcp capabilities github --yes

Capability preview is not a permission grant. It records negotiated tools and proposed sandbox permission rules for review, then actual tool calls still use the approval path.

Configure user scope​

Use user scope when a text-only skill or steering rule should follow you across repositories:

Copy-Item -Recurse .\.phonton $HOME\.phonton
phonton extensions doctor

Workspace scope is better for team rules because the repo carries the extension files and review output can point back to the workspace source.

Repository rule​

Each public extension should have its own GitHub repository. The website directory links to those repos instead of hosting multiple extension packs in the website source tree.