Saltar al contenido principal
Versión: 0.24.0

Interface: ExtensionContribution

Defined in: core/extensions.ts:56

What an extension brings to a session. Every part is optional.

Properties​

PropertyTypeDescriptionDefined in
api?Record<string, unknown>What the session hands back to the host (e.g. the knowledge base's store), by name.core/extensions.ts:87
fileTools?string[]Built-in file tools it needs the session to have (Read, Glob, Grep…).core/extensions.ts:62
helpLines?string[]What it says about itself in this session (its commands, its folder), for the agent to tell the person (SessionFacts).core/extensions.ts:85
hooks?Partial<Record<HookEvent, HookCallbackMatcher[]>>Its hooks, by event, run after the kit's own: an internal extension's only (the memory hears the person's messages with UserPromptSubmit).core/extensions.ts:83
mcpServers?Record<string, McpServerConfig>MCP servers, by name (mcp__<name>__<tool>).core/extensions.ts:58
promptSection?stringA section of the system prompt, after the agent's own and the list of extensions.core/extensions.ts:60
readOnlyDirs?string[]Folders the file tools may read and search, never write (a sources folder).core/extensions.ts:64
readOnlyHintServers?string[]Its MCP servers whose tools that only read plan mode learns from the servers themselves (readOnlyHint), asked while the session runs: an installed extension whose manifest lists no readOnlyTools. A list in the manifest wins: its servers aren't here.core/extensions.ts:74
readOnlyTools?string[]Its MCP tools that only read: plan mode lets them through.core/extensions.ts:68
selfAskingTools?string[]Its MCP tools that ask the person themselves: interactive mode's step gate doesn't ask first.core/extensions.ts:76
toolLabels?Readonly<Record<string, ToolLabel>>How the chat shows its tools, by full name, in the kit's language: its line and how it counts in a folded group.core/extensions.ts:78
toolOnlyDirs?object[]Folders reached only through its own tools, never the file tools, and what to use instead.core/extensions.ts:66