Continue native reference
Start with the Continue setup. Output keys are listed under output settings.
Native mappings
Rule activation
- A scoped rule matches its scope directory plus its
globsorpaths, and gets noalwaysApply. See file-pattern limits for directory rules. - A rule with no directory scope keeps
globs,alwaysApply, anddescription. - A comma-separated
globsstring becomes an array, because Continue reads a string as one pattern. x-continue.regexworks only withoutscope.
Skills
- Written to
.continue/skills/<name>/SKILL.md. Bundled files are copied unchanged. - The IDE extension and
cnread this folder and.claude/skills/. They do not merge names across the two, so with theclaudetarget each skill shows up twice. - Continue requires
nameanddescriptionand offers the other files on demand (loadMarkdownSkills.ts). - A skill has only
nameanddescription, and every skill is offered to the model. None can be kept user-only, sodisable-model-invocationis dropped with a note and commands are skipped.invokablebelongs to prompts, not skills.
MCP
- Each file is a Continue block (
name,version,schema: v1) with the server in anmcpServers:list. A flat single-server file does not load. - Stdio gets
command,args,env,cwd. Remote getstype,url,requestOptions. Remoteenvis dropped with a note. type: httpbecomestype: streamable-http, the only Streamable HTTP value Continue's schema accepts.sseandstreamable-httpstay as they are.headersmoves torequestOptions.headers.import continuereverses both changes.- Every transport keeps
connectionTimeout(milliseconds). - Remote
requestOptionskeepstimeout,verifySsl,caBundlePath,proxy,clientCertificate,headers. - An explicit native header wins a duplicate key.
x-continueoverrides each matching top-level option. - No file is written, with a note, for
type: ws(Continue has no websocket transport) or for an entry missingcommand(stdio) orurl(remote). Either would make Continue reject the whole file.
Assistants
- With
outputs.continue.assistants-dirset, each agent also gets<dir>/<name>.yaml:name,version(default0.0.1),schema: v1, and the body as oneprompts: [{name, description, prompt}]entry (Continue reference). - Continue's source loads YAML from
.continue/assistants,.continue/agents, and.continue/configsat the workspace root as local profiles (ConfigHandler.ts). A folder set here with one of those paths loads as a local profile. Continue's docs do not describe a workspace folder, so this rests on the source only. - Each file is also a standalone
config.yamlforcn --config <dir>/<name>.yamlor the IDE's config picker. It has no models or rules, so your defaults apply. - The rule form (
.continue/rules/agent-<name>.md) is written either way.
Import
agnostic-ai import continue reads .continue/rules/ and sorts each file into a spec kind by filename prefix.
- Native
globsandregexvalues (strings or arrays, empty arrays and patterns with commas included) are kept underx-continue. - Scope: a subfolder named after a project directory sets the rule's scope, so the rule matches that directory plus its patterns.
- A scoped
regexor scoped emptyglobsarray is reported as unsupported. To filter by file only, omitscopeand keep the source file outside any folder that sets scope. - Native activation:
x-continue.globsandx-continue.regexkeep activation exactly, as long as there is no portablescope. A rule in a subfolder stays there, even when the folder names no project directory. An explicitscopeswitches to scope plus patterns, with its selector limits. - Skills: read from
.continue/skills/with bundled files. - MCP: read from
.continue/mcpServers/. That means*.yamlblocks with one server, and.jsonfiles (read as JSONC) with anmcpServersmap or one server named after the file. - A duplicate or unsafe MCP name fails before any spec is written. Connection options survive import and sync.
- Sync removes
.continue/rules/skill-<name>.mdfiles that older versions wrote. Import still reads such a rule as a skill.
Secrets
- MCP import replaces literal
envand header values with${NAME}references and tells you which variables to set. - Continue's
${{ secrets.NAME }}comes back as${NAME}. - Sync writes Continue's secret syntax in stdio
envandargsand in remoteurlandrequestOptions.headers,x-continueoverrides included. - The IDE reads secrets from a project
.env,.continue/.env, or~/.continue/.env. The CLI also reads process environment variables. See Continue's secrets guide and secret resolution. - Keep those files out of Git.