Antigravity

Code Config’s managed Antigravity launch uses a separate home folder for the run. Your regular configuration remains outside that launch folder.

Before you start

Set up and sign in to the coding app on this computer. Connect Code Config and choose a toolkit. Coding-app accounts and models explains importing an existing account folder.

Open your project

In the Code Config app, choose the project, toolkit, Antigravity in a terminal, and account, then launch.

For the exact CLI identifier used by the installed build, run:

csc launch --help

The launch checks for toolkit updates before starting the app. The CLI uses the project or workspace default unless you choose another toolkit.

Check your tools

Find a selected skill, agent, or command in the app and try it. Complete any skill-activation request from the coding app. A successful launch does not bypass the app’s own approvals.

Check command arguments carefully after conversion. Read the launch notes for fields and tool names that could not be translated.

What Code Config changes

Skills, agents, command files, and combined instructions are placed in the launch’s app configuration tree. Antigravity uses its own skills folder, rather than the shared .agents/skills/ tree described for other apps.

Rules and context files are combined into the app’s instruction file. Output styles become sections in that file, not replacements for the app’s system prompt. Agents are converted with supported descriptions, model choices, and tool lists; unknown tool-name translations are reported.

For converted commands, $ARGUMENTS becomes {{args}}, shell snippets use the app’s shell syntax, and file references use its file-reference syntax. Numbered arguments such as $1 are left unchanged and reported; rewrite commands that depend on them. A command already in the app’s format is placed without that conversion.

Limitations

Configure MCP servers and hooks in your own app settings. The launch copies those settings rather than adding toolkit servers or hook bundles. Setting up a toolkit credential does not register a server in this app.

Code Config does not install extensions or apply repository settings files for this target. Workflows and marketplace entries are not written as configuration. Command allowlists, argument hints, and command-specific model choices may have no equivalent and are reported.

Next

Compatibility and setup.