Repository navigation
Agents
form.ext's engine does every step a person does, so agents make extensions the same way: from a starter, through Check and Preview, to a signed package in the app.
./formext cli covers the path: docs and templates (what each app offers), new NAME --app formcut --starter panel, read, write and manifest, validate (Check), preview (a snapshot of what a host would load), package (--anyway past code-lint errors), import (a folder or a .formpkg), keys, sign, verify, entry, run-in-app (add to or remove from dev.json), publish (the submission folder, --formportal to send it on) and submit (the folder in form.ext-registry's layout, the registry's checks, and the git and gh commands for the pull request; --checkout names a local clone of the registry). ./formext cli --help lists every command. Answers are short text, or JSON with --json; failures exit non-zero with the reason in plain words. It uses a running engine with the same data folder, or runs in-process. The desktop app's frozen engine takes the same commands (formext-engine cli ...).
./formext mcp serves MCP on stdio. .mcp.json registers it for Claude Code in this repository, .codex/config.toml for Codex and .cursor/mcp.json for Cursor. Its tools are the command line's commands under the same names (run_in_app with an underscore), and its resources formext://docs/<topic> serve the contract, the SDK source, the schema, the example and each app's API page. What an agent does appears in the open window at once through the engine's live events.
./formext claude starts Claude Code in the repository with formext (and formMCP when found) connected. ./formext agents install registers the MCP servers and copies the skills for your account in Claude Code, Codex and Cursor (--dry-run shows the changes; files are backed up first). ./formext agents status reports what it found. ./formext agents sync regenerates the tool reference and mirrors .claude/skills to .agents/skills; --check exits 1 on drift.
formMCP (formmcp mcp) is the family hub that reaches every installed Form app's tools. It is a separate app; when it is missing its entry shows as unavailable and the formext server still works.
-
.claude/skills/formext-harness: using form.ext through MCP to make an extension for any Form app, from choosing the app's API calls to a signed package. -
.claude/skills/formext-hosts: for each of the twelve host apps, what an extension can do, which host skill explains the app and how to test live through Run in App and formMCP. - Host skills copied byte for byte from the apps (
formvis-driving,formcut-mcp,formwav-harnessand the others), with their source commits in.claude/skills/HOSTS.md. -
.claude/skills/formext-skillset: changing form.ext's own code (the panes, the engine modules, the contract kit rules).
The Studio's bottom panel has Terminal, Claude Code and Chat tabs. They run in the open project's folder with these servers and skills, over local-only routes (127.0.0.1, session-guarded).
Every host with an MCP server or command line also offers extensions_list and extension_command (contract section 8), so an agent can run an extension's commands in the app, under the same consent rules as a person.