@subimpact/e 0.99.4 → 0.99.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +7 -0
- package/dist/bundle/chunks/{chunk-4GK5QWPL.js → chunk-34ZJK2EZ.js} +1 -1
- package/dist/bundle/chunks/{chunk-EWH2CBXL.js → chunk-YGYY5CGE.js} +2 -2
- package/dist/bundle/chunks/{virtual-modules-33PKUUYB.js → virtual-modules-GWKJPH7F.js} +1 -1
- package/dist/bundle/cli-runtime.js +1 -1
- package/dist/bundle/index.js +1 -1
- package/dist/bundle/rpc-entry.js +1 -1
- package/docs/cli.md +3 -62
- package/docs/configuration.md +0 -2
- package/docs/docs.json +0 -4
- package/docs/extensions.md +5 -25
- package/docs/llama-cpp.md +1 -1
- package/docs/models.md +4 -21
- package/docs/sdk.md +1 -6
- package/docs/security.md +0 -2
- package/docs/settings.md +4 -6
- package/package.json +1 -1
- package/docs/mcp.md +0 -248
|
@@ -1,2 +1,2 @@
|
|
|
1
1
|
import { createRequire as __piCreateRequire } from "node:module"; const require = __piCreateRequire(import.meta.url);
|
|
2
|
-
import{dist_exports as dist_exports3}from"./chunk-
|
|
2
|
+
import{dist_exports as dist_exports3}from"./chunk-34ZJK2EZ.js";import{all_exports,build_exports,compat_exports,compile_exports,dist_exports as dist_exports2,value_exports}from"./chunk-YGYY5CGE.js";import"./chunk-USJZMAIR.js";import{dist_exports}from"./chunk-SS3AAGL7.js";import"./chunk-S3GGRYIO.js";import"./chunk-VIV3CWXG.js";import"./chunk-DRQDKNXA.js";import"./chunk-TRDNDS6A.js";import"./chunk-7JGR3GZN.js";import"./chunk-A3JYRWB6.js";import"./chunk-4L3WN2XY.js";var oauth_exports={};var VIRTUAL_MODULES={typebox:build_exports,"typebox/compile":compile_exports,"typebox/value":value_exports,"@sinclair/typebox":build_exports,"@sinclair/typebox/compile":compile_exports,"@sinclair/typebox/value":value_exports,"@earendil-works/pi-agent-core":dist_exports2,"@earendil-works/pi-tui":dist_exports,"@earendil-works/pi-ai":compat_exports,"@earendil-works/pi-ai/compat":compat_exports,"@earendil-works/pi-ai/oauth":oauth_exports,"@earendil-works/pi-ai/providers/all":all_exports,"@earendil-works/pi-coding-agent":dist_exports3,"@mariozechner/pi-agent-core":dist_exports2,"@mariozechner/pi-tui":dist_exports,"@mariozechner/pi-ai":compat_exports,"@mariozechner/pi-ai/compat":compat_exports,"@mariozechner/pi-ai/oauth":oauth_exports,"@mariozechner/pi-ai/providers/all":all_exports,"@mariozechner/pi-coding-agent":dist_exports3};export{VIRTUAL_MODULES};
|
|
@@ -1,3 +1,3 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
2
|
import { createRequire as __piCreateRequire } from "node:module"; const require = __piCreateRequire(import.meta.url);
|
|
3
|
-
import{configureHttpDispatcher,main}from"./chunks/chunk-
|
|
3
|
+
import{configureHttpDispatcher,main}from"./chunks/chunk-YGYY5CGE.js";import"./chunks/chunk-USJZMAIR.js";import{APP_NAME}from"./chunks/chunk-SS3AAGL7.js";import"./chunks/chunk-S3GGRYIO.js";import"./chunks/chunk-VIV3CWXG.js";import"./chunks/chunk-DRQDKNXA.js";import"./chunks/chunk-TRDNDS6A.js";import"./chunks/chunk-7JGR3GZN.js";import"./chunks/chunk-A3JYRWB6.js";import"./chunks/chunk-4L3WN2XY.js";function setupCli(){process.title=APP_NAME,process.env.PI_CODING_AGENT="true",process.env.AI_AGENT="pi",process.emitWarning=(()=>{}),configureHttpDispatcher()}setupCli();main(process.argv.slice(2));
|
package/dist/bundle/index.js
CHANGED
|
@@ -1,2 +1,2 @@
|
|
|
1
1
|
import { createRequire as __piCreateRequire } from "node:module"; const require = __piCreateRequire(import.meta.url);
|
|
2
|
-
import{ShowImagesSelectorComponent,ThemeSelectorComponent}from"./chunks/chunk-
|
|
2
|
+
import{ShowImagesSelectorComponent,ThemeSelectorComponent}from"./chunks/chunk-34ZJK2EZ.js";import{AgentSession,AgentSessionRuntime,ArminComponent,AssistantMessageComponent,BashExecutionComponent,BorderedLoader,BranchSummaryMessageComponent,CURRENT_SESSION_VERSION,CompactionSummaryMessageComponent,CredentialSynchronizationError,CustomEditor,CustomMessageComponent,DEFAULT_COMPACTION_SETTINGS,DEFAULT_MAX_BYTES,DEFAULT_MAX_LINES,DefaultPackageManager,DefaultResourceLoader,DynamicBorder,ExtensionEditorComponent,ExtensionInputComponent,ExtensionRunner,ExtensionSelectorComponent,FooterComponent,InteractiveMode,LoginDialogComponent,ModelRegistry,ModelRuntime,ModelSelectorComponent,OAuthSelectorComponent,ProjectTrustStore,RpcClient,SessionManager,SessionSelectorComponent,SettingsManager,SettingsSelectorComponent,SkillInvocationMessageComponent,ThinkingSelectorComponent,ToolExecutionComponent,TreeSelectorComponent,UserMessageComponent,UserMessageSelectorComponent,VIRTUAL_MODEL_STATE_ENTRY,buildContextEntries,buildSessionContext,buildSessionProjection,calculateContextTokens,collectEntriesForBranchSummary,compact,convertToLlm,convertToPng,copyToClipboard,createAgentSession,createAgentSessionFromServices,createAgentSessionRuntime,createAgentSessionServices,createBashTool,createBashToolDefinition,createCodingTools,createEditTool,createEditToolDefinition,createEventBus,createExtensionRuntime,createFindTool,createFindToolDefinition,createGrepTool,createGrepToolDefinition,createLocalBashOperations,createLocalPowerShellOperations,createLsTool,createLsToolDefinition,createPowerShellTool,createPowerShellToolDefinition,createReadOnlyTools,createReadTool,createReadToolDefinition,createSyntheticSourceInfo,createWriteTool,createWriteToolDefinition,defineTool,detectSupportedImageMimeTypeFromFile,discoverAndLoadExtensions,estimateTokens,findCutPoint,findTurnStartIndex,formatDimensionNote,formatSize,formatSkillsForPrompt,generateBranchSummary,generateDiffString,generateSummary,generateSummaryWithUsage,generateUnifiedPatch,getLastAssistantUsage,getLatestCompactionEntry,getPowerShellConfig,getShellConfig,hasTrustRequiringProjectResources,isBashToolResult,isEditToolResult,isFindToolResult,isGrepToolResult,isLsToolResult,isPowerShellToolResult,isReadToolResult,isToolCallEventType,isWriteToolResult,loadProjectContextFiles,loadSkills,loadSkillsFromDir,main,migrateSessionEntries,parseArgs,parseFrontmatter,parseSessionEntries,parseSkillBlock,prepareBranchEntries,readStoredCredential,renderDiff,resizeImage,resolveCliModel,resolveModelScopeWithDiagnostics,runPrintMode,runRpcMode,serializeConversation,sessionEntryToContextMessages,shouldCompact,stripFrontmatter,truncateHead,truncateLine,truncateTail,truncateToVisualLines,withFileMutationQueue,wrapRegisteredTool,wrapRegisteredTools}from"./chunks/chunk-YGYY5CGE.js";import"./chunks/chunk-USJZMAIR.js";import{CONFIG_DIR_NAME,Theme,VERSION,getAgentDir,getDocsPath,getExamplesPath,getLanguageFromPath,getMarkdownTheme,getPackageDir,getReadmePath,getSelectListTheme,getSettingsListTheme,highlightCode,initTheme,keyHint,keyText,rawKeyHint}from"./chunks/chunk-SS3AAGL7.js";import"./chunks/chunk-S3GGRYIO.js";import"./chunks/chunk-VIV3CWXG.js";import"./chunks/chunk-DRQDKNXA.js";import"./chunks/chunk-TRDNDS6A.js";import"./chunks/chunk-7JGR3GZN.js";import"./chunks/chunk-A3JYRWB6.js";import"./chunks/chunk-4L3WN2XY.js";export{AgentSession,AgentSessionRuntime,ArminComponent,AssistantMessageComponent,BashExecutionComponent,BorderedLoader,BranchSummaryMessageComponent,CONFIG_DIR_NAME,CURRENT_SESSION_VERSION,CompactionSummaryMessageComponent,CredentialSynchronizationError,CustomEditor,CustomMessageComponent,DEFAULT_COMPACTION_SETTINGS,DEFAULT_MAX_BYTES,DEFAULT_MAX_LINES,DefaultPackageManager,DefaultResourceLoader,DynamicBorder,ExtensionEditorComponent,ExtensionInputComponent,ExtensionRunner,ExtensionSelectorComponent,FooterComponent,InteractiveMode,LoginDialogComponent,ModelRegistry,ModelRuntime,ModelSelectorComponent,OAuthSelectorComponent,ProjectTrustStore,RpcClient,SessionManager,SessionSelectorComponent,SettingsManager,SettingsSelectorComponent,ShowImagesSelectorComponent,SkillInvocationMessageComponent,Theme,ThemeSelectorComponent,ThinkingSelectorComponent,ToolExecutionComponent,TreeSelectorComponent,UserMessageComponent,UserMessageSelectorComponent,VERSION,VIRTUAL_MODEL_STATE_ENTRY,buildContextEntries,buildSessionContext,buildSessionProjection,calculateContextTokens,collectEntriesForBranchSummary,compact,convertToLlm,convertToPng,copyToClipboard,createAgentSession,createAgentSessionFromServices,createAgentSessionRuntime,createAgentSessionServices,createBashTool,createBashToolDefinition,createCodingTools,createEditTool,createEditToolDefinition,createEventBus,createExtensionRuntime,createFindTool,createFindToolDefinition,createGrepTool,createGrepToolDefinition,createLocalBashOperations,createLocalPowerShellOperations,createLsTool,createLsToolDefinition,createPowerShellTool,createPowerShellToolDefinition,createReadOnlyTools,createReadTool,createReadToolDefinition,createSyntheticSourceInfo,createWriteTool,createWriteToolDefinition,defineTool,detectSupportedImageMimeTypeFromFile,discoverAndLoadExtensions,estimateTokens,findCutPoint,findTurnStartIndex,formatDimensionNote,formatSize,formatSkillsForPrompt,generateBranchSummary,generateDiffString,generateSummary,generateSummaryWithUsage,generateUnifiedPatch,getAgentDir,getDocsPath,getExamplesPath,getLanguageFromPath,getLastAssistantUsage,getLatestCompactionEntry,getMarkdownTheme,getPackageDir,getPowerShellConfig,getReadmePath,getSelectListTheme,getSettingsListTheme,getShellConfig,hasTrustRequiringProjectResources,highlightCode,initTheme,isBashToolResult,isEditToolResult,isFindToolResult,isGrepToolResult,isLsToolResult,isPowerShellToolResult,isReadToolResult,isToolCallEventType,isWriteToolResult,keyHint,keyText,loadProjectContextFiles,loadSkills,loadSkillsFromDir,main,migrateSessionEntries,parseArgs,parseFrontmatter,parseSessionEntries,parseSkillBlock,prepareBranchEntries,rawKeyHint,readStoredCredential,renderDiff,resizeImage,resolveCliModel,resolveModelScopeWithDiagnostics,runPrintMode,runRpcMode,serializeConversation,sessionEntryToContextMessages,shouldCompact,stripFrontmatter,truncateHead,truncateLine,truncateTail,truncateToVisualLines,withFileMutationQueue,wrapRegisteredTool,wrapRegisteredTools};
|
package/dist/bundle/rpc-entry.js
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
2
|
import { createRequire as __piCreateRequire } from "node:module"; const require = __piCreateRequire(import.meta.url);
|
|
3
|
-
import{configureHttpDispatcher,main}from"./chunks/chunk-
|
|
3
|
+
import{configureHttpDispatcher,main}from"./chunks/chunk-YGYY5CGE.js";import"./chunks/chunk-USJZMAIR.js";import{APP_NAME}from"./chunks/chunk-SS3AAGL7.js";import"./chunks/chunk-S3GGRYIO.js";import"./chunks/chunk-VIV3CWXG.js";import"./chunks/chunk-DRQDKNXA.js";import"./chunks/chunk-TRDNDS6A.js";import"./chunks/chunk-7JGR3GZN.js";import"./chunks/chunk-A3JYRWB6.js";import"./chunks/chunk-4L3WN2XY.js";process.title=`${APP_NAME}-rpc`;process.env.PI_CODING_AGENT="true";process.env.AI_AGENT="pi";process.emitWarning=(()=>{});configureHttpDispatcher();main(["--mode","rpc",...process.argv.slice(2)]);
|
package/docs/cli.md
CHANGED
|
@@ -13,7 +13,6 @@ pi update [target] [options]
|
|
|
13
13
|
pi list
|
|
14
14
|
pi config [options]
|
|
15
15
|
pi auth <check|print-api-key|print-bearer-token> [options]
|
|
16
|
-
pi mcp <list|login|logout> [options]
|
|
17
16
|
```
|
|
18
17
|
|
|
19
18
|
<a id="modes"></a>
|
|
@@ -138,48 +137,7 @@ Default enabled tools are `read`, `bash`, `edit`, and `write`, unless `defaultTo
|
|
|
138
137
|
| `find` | Find paths using glob patterns |
|
|
139
138
|
| `ls` | List directory contents |
|
|
140
139
|
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
| Built-in extension | Purpose |
|
|
144
|
-
|---|---|
|
|
145
|
-
| `codemode` | Run JavaScript that calls the other tools, for example in parallel with `Promise.allSettled`; only the script's output reaches the model |
|
|
146
|
-
| `tool_search` | Search tools that are not declared to the model (`codemode` and `deferred` exposure, such as MCP tools) and declare the matches for the next call |
|
|
147
|
-
|
|
148
|
-
### Enable codemode
|
|
149
|
-
|
|
150
|
-
To turn on `codemode` for every session, add it to the default tools in `~/.pi/agent/settings.json` or a project's `.pi/settings.json`:
|
|
151
|
-
|
|
152
|
-
```json
|
|
153
|
-
{
|
|
154
|
-
"defaultTools": ["+codemode"]
|
|
155
|
-
}
|
|
156
|
-
```
|
|
157
|
-
|
|
158
|
-
This keeps `read`, `bash`, `edit`, and `write` and adds `codemode`. For one invocation, list every tool, since `--tools` replaces the selection:
|
|
159
|
-
|
|
160
|
-
```sh
|
|
161
|
-
pi --tools read,bash,edit,write,codemode
|
|
162
|
-
```
|
|
163
|
-
|
|
164
|
-
Codemode is useful without MCP: scripts can run several tool calls in parallel, filter large output before it reaches the model, and call classifier models such as TypeSafe's Jev through `models.classify()` (see [Classifier models](models.md#use-classifier-models)).
|
|
165
|
-
|
|
166
|
-
### How codemode works
|
|
167
|
-
|
|
168
|
-
Codemode scripts run in a QuickJS sandbox that can only reach the other tools, through `tools.<name>(args)`; `ALL_TOOLS` lists them. Output comes from `text(value)`, `image(dataUrlOrImageContent)`, `console.*`, and a top-level `return value`; `exit()` ends the script early. The result starts with `Script completed` or `Script failed`, the wall time, and the output; a failed script keeps its partial output, followed by `Script error:` and the error.
|
|
169
|
-
|
|
170
|
-
A script may start with an options line such as `// @options: {"max_output_tokens": 2000, "timeout_ms": 60000}`. `max_output_tokens` (default 10000) limits the output: longer output keeps its start and end, and the full text is written to a temp file whose path is included in the result. `timeout_ms` is a hard deadline, unset by default.
|
|
171
|
-
|
|
172
|
-
While `codemode` is active, `codemode.mode` in [settings](settings.md#tools) decides how the other tools are presented. With `on` (default) declared tools keep being declared and their descriptions show how to call them from scripts. With `only` they are hidden from the model and listed in the `codemode` description instead, so the model calls them through scripts.
|
|
173
|
-
|
|
174
|
-
The `codemode` description lists the callable tools with their TypeScript declarations, grouped by namespace (for example one MCP server). Tools with `deferred` exposure, which includes MCP tools with the default `codemode` exposure, are not listed and do not affect the description, so it stays the same while MCP servers connect. Declarations share a budget of 3000 estimated tokens (`codemode.inlineBudget` in [settings](settings.md#tools)). Scripts find the rest with `await searchTools(query, { limit, namespace })`, which ranks tools with BM25, and `await describeTool(name)`, or by filtering `ALL_TOOLS`. `await describeNamespace(name)` returns a namespace's description, its instructions (for MCP servers, the server instructions), and the names of its tools.
|
|
175
|
-
|
|
176
|
-
Tools with an output schema resolve to structured values: `bash` to `{ output, truncated, full_output_path?, exit_code, wall_time_seconds }`, also for non-zero exit codes, and MCP tools to their `CallToolResult`. Other tools resolve to their text output. The `output` of `bash` is not limited to the 2000 lines or 50KB the model sees: it holds up to 1 MiB, and longer output keeps its first and last 512 KiB around an omission marker, with `truncated` set and the full output in `full_output_path`.
|
|
177
|
-
|
|
178
|
-
`store(key, value)` and `load(key)` keep JSON values across `codemode` calls: each successful script that stores values appends a `codemode-store` custom entry to the session, so resumed sessions keep the values and each branch sees only the values written on its path. Scripts can also use `models`: `getModelsOfType`, `getAvailableOfType`, and `getModelOfType` list the model catalog, and `classify(model, context)` runs a classifier model with the session's credentials, at most four at a time per script.
|
|
179
|
-
|
|
180
|
-
### Tool search
|
|
181
|
-
|
|
182
|
-
`tool_search` is off by default; enable it with `"defaultTools": ["+tool_search"]` or `--tools`. It uses the same ranking as `searchTools()` over tools that are not declared yet and declares the matches for the next model call. Loaded tools are recorded in the session like other tool changes, so they stay declared on that branch.
|
|
140
|
+
No built-in extension adds tools. The only built-in extension is `builtin:llama.cpp`, which is on by default and registers local models and the `/llama` command, but no tools.
|
|
183
141
|
|
|
184
142
|
<a id="resource-options"></a>
|
|
185
143
|
|
|
@@ -192,9 +150,9 @@ pi --extension ./review.ts
|
|
|
192
150
|
See [Configuration](configuration.md) for conventional directories and project trust, [Settings](settings.md#resources) for configured paths, and [Pi Packages](packages.md) for package sources.
|
|
193
151
|
|
|
194
152
|
- `-e`, `--extension <path>`<br>
|
|
195
|
-
Loads an extension file or directory, or a built-in extension such as `builtin:
|
|
153
|
+
Loads an extension file or directory, or a built-in extension such as `builtin:llama.cpp`, and is repeatable.
|
|
196
154
|
- `-ne`, `--no-extensions`<br>
|
|
197
|
-
Disables discovered, configured, and built-in extensions. Explicit `-e` paths still load, so `pi -ne -e builtin:
|
|
155
|
+
Disables discovered, configured, and built-in extensions. Explicit `-e` paths still load, so `pi -ne -e builtin:llama.cpp` loads only the built-in llama.cpp extension.
|
|
198
156
|
- `--skill <path>`<br>
|
|
199
157
|
Loads a skill file or directory and is repeatable.
|
|
200
158
|
- `-ns`, `--no-skills`<br>
|
|
@@ -310,20 +268,3 @@ Authentication commands require `--provider <provider>` or `--model <model>`. Se
|
|
|
310
268
|
| `--min-expiry <duration>` | `print-bearer-token` | Require remaining token lifetime using `ms`, `s`, `m`, or `h`, such as `30m` |
|
|
311
269
|
|
|
312
270
|
Credential-printing commands write secrets to stdout.
|
|
313
|
-
|
|
314
|
-
## MCP commands
|
|
315
|
-
|
|
316
|
-
These commands work outside a session, so agents can run them through `bash`. See [MCP Servers](mcp.md).
|
|
317
|
-
|
|
318
|
-
| Command | Description |
|
|
319
|
-
|---|---|
|
|
320
|
-
| `pi mcp add <server> [options] -- <command> [args...]` | Add or replace a stdio server in `mcp.json`; `--env KEY=VALUE` (repeatable) and `--cwd <dir>` set its environment and working directory. Arguments after the command are passed to it |
|
|
321
|
-
| `pi mcp add <server> [options] --url <url>` | Add or replace a streamable HTTP server; `--header KEY=VALUE` (repeatable), `--bearer-token-env-var <NAME>` (sends `Authorization: Bearer ${NAME}`), `--oauth-client-id`, `--oauth-client-secret`, `--oauth-callback-port`, and `--oauth-client-name` configure authentication |
|
|
322
|
-
| `pi mcp remove <server>` | Remove a server from `mcp.json`; stored OAuth credentials are kept |
|
|
323
|
-
| `pi mcp list [--json]` | Connect to every enabled server and print its state, tools, and errors; exit with `1` when a config entry is invalid or an enabled server is not connected |
|
|
324
|
-
| `pi mcp login <server> [--timeout <seconds>]` | Sign in to an OAuth server: open the authorization page and wait for the browser (default 300 seconds); a terminal also accepts the pasted redirect URL |
|
|
325
|
-
| `pi mcp logout <server>` | Delete the stored OAuth credentials of a server |
|
|
326
|
-
|
|
327
|
-
`add` and `remove` change `~/.pi/agent/mcp.json`, or `.pi/mcp.json` in the current directory with `--local` (`-l`). `add` also takes `--exposure <mode>` (see [Exposure](mcp.md#exposure)) and `--description <text>` and does not connect; run `pi mcp list` to check the server.
|
|
328
|
-
|
|
329
|
-
Project `.pi/mcp.json` files are only read for projects that are already trusted.
|
package/docs/configuration.md
CHANGED
|
@@ -12,7 +12,6 @@ The agent directory is shown as `<agent-dir>` below. Set its location with the `
|
|
|
12
12
|
|---|---|
|
|
13
13
|
| `<agent-dir>/settings.json` | User-level [settings](settings.md), including preferences, defaults, resource paths, and Pi package declarations. |
|
|
14
14
|
| `<agent-dir>/keybindings.json` | Custom terminal UI and application [keybindings](keybindings.md). |
|
|
15
|
-
| `<agent-dir>/mcp.json` | [MCP servers](mcp.md) available in every project. |
|
|
16
15
|
| `<agent-dir>/models.json` | [Compatible endpoints, models, and model overrides](models.md#configure-a-compatible-endpoint). |
|
|
17
16
|
| `<agent-dir>/auth.json` | Saved API keys and OAuth credentials. |
|
|
18
17
|
| `<agent-dir>/AGENTS.override.md`, `AGENTS.md`, `AGENTS.MD`, `CLAUDE.md`, or `CLAUDE.MD` | User instructions applied across working directories. |
|
|
@@ -28,7 +27,6 @@ The agent directory is shown as `<agent-dir>` below. Set its location with the `
|
|
|
28
27
|
| Path | Responsibility |
|
|
29
28
|
|---|---|
|
|
30
29
|
| `.pi/settings.json` | Project-level [settings](settings.md), resource paths, and Pi package declarations. |
|
|
31
|
-
| `.pi/mcp.json` | Project [MCP servers](mcp.md). |
|
|
32
30
|
| `.pi/SYSTEM.md` | Replaces the system prompt for the project. |
|
|
33
31
|
| `.pi/APPEND_SYSTEM.md` | Adds project-specific instructions to the system prompt. |
|
|
34
32
|
| `.pi/extensions/` | Project extensions. |
|
package/docs/docs.json
CHANGED
package/docs/extensions.md
CHANGED
|
@@ -80,7 +80,6 @@ Automatic retries, recovery, compaction, or queued work can continue afterward.
|
|
|
80
80
|
| Persist non-context session data | `pi.appendEntry()` |
|
|
81
81
|
| Change active tools, model, or thinking level | Session control methods on `pi` |
|
|
82
82
|
| Add a model provider | `pi.registerProvider()` |
|
|
83
|
-
| Add an MCP server | `pi.registerMcpServer()` |
|
|
84
83
|
| Route each request to a model | [`pi.registerVirtualModel()`](virtual-models.md) |
|
|
85
84
|
| Add terminal rendering | Renderer registration and `ctx.ui` |
|
|
86
85
|
| Communicate with another extension | `pi.events` |
|
|
@@ -143,7 +142,7 @@ Use sequential execution when tools share mutable in-memory state.
|
|
|
143
142
|
File-mutating tools should wrap the complete read-modify-write operation with `withFileMutationQueue()`.
|
|
144
143
|
Truncate large model-facing results and tell the model where to read the complete output.
|
|
145
144
|
|
|
146
|
-
Declare `outputSchema` and return a matching `structuredContent` when the result is data. The model still receives `content`; programmatic callers
|
|
145
|
+
Declare `outputSchema` and return a matching `structuredContent` when the result is data. The model still receives `content`; programmatic callers receive `structuredContent` instead of the text. Tools without `outputSchema` are passed to programmatic callers as their text content. To report a failure that still carries data, return the result with `isError: true` instead of throwing: the model sees an error, and programmatic callers still receive `structuredContent`.
|
|
147
146
|
|
|
148
147
|
A tool can run other tools with `ctx.executeTool(name, args, { signal, onUpdate })`. Nested calls go through argument validation and the `tool_call` and `tool_result` handlers like model-issued calls, and emit `tool_execution_start`, `tool_execution_update`, and `tool_execution_end`; all of these events carry `parentToolCallId`, and their `toolCallId` is assigned by pi as `<parent id>/<n>`. These ids do not appear as tool calls or tool results in the transcript. Nested calls do not add transcript entries: their results only reach the calling tool, which reports them itself, for example through `onUpdate` and `details`. The session keeps a bounded record of them (name, arguments, status, duration, error; never results) as `nestedCalls` on the calling tool's result message. It is used for compaction file lists and shown in HTML exports. Arguments over 8 KiB per call or 32 KiB per tool result are omitted, at most 256 calls are kept, and `complete: false` marks a record that lost anything. The `usage` of nested results, at every depth, is added to the calling tool's result `usage`, so a tool reports only its own usage, not that of the tools it called. `ctx.tools` lists the tools `ctx.executeTool()` can call. `tool_result` handlers that redact `content` should also replace `structuredContent`; replacing only `content` drops it.
|
|
149
148
|
|
|
@@ -151,19 +150,17 @@ See [`hello.ts`](../examples/extensions/hello.ts), [`todo.ts`](../examples/exten
|
|
|
151
150
|
|
|
152
151
|
### Tool exposure
|
|
153
152
|
|
|
154
|
-
`exposure` controls how the model reaches a tool. "Callable" means callable from other tools through `ctx.executeTool()` (`ctx.tools`)
|
|
153
|
+
`exposure` controls how the model reaches a tool. "Callable" means callable from other tools through `ctx.executeTool()` (`ctx.tools`):
|
|
155
154
|
|
|
156
155
|
- `direct` (default): declared to the model while active, and callable while active.
|
|
157
156
|
- `model-only`: declared to the model while active, never callable. Use it for tools that orchestrate other tools or ask the user.
|
|
158
|
-
- `codemode`: callable whenever registered, and listed by the `codemode` tool. Not declared to the model unless activated explicitly.
|
|
159
|
-
- `deferred`: like `codemode`, but codemode tools do not list it; `tool_search` can find and activate it.
|
|
160
157
|
- `hidden`: registered but unreachable. Re-register a tool with `exposure: "hidden"` to withdraw it, since tools cannot be unregistered.
|
|
161
158
|
|
|
162
|
-
`namespace: { name, description, instructions }` groups related tools
|
|
159
|
+
`namespace: { name, description, instructions }` groups related tools. `description` summarizes the group; `instructions` holds longer usage guidance and is not listed.
|
|
163
160
|
|
|
164
161
|
Registering a `direct` or `model-only` tool activates it; the other exposures are not activated on registration. The active set (`pi.getActiveTools()`, `pi.setActiveTools()`) is the set of tools declared to the model. `pi.getAllTools()` reports each tool's `exposure`, `namespace`, and `annotations`.
|
|
165
162
|
|
|
166
|
-
`annotations` are hints about what a tool does
|
|
163
|
+
`annotations` are hints about what a tool does: `readOnlyHint`, `destructiveHint`, `idempotentHint`, and `openWorldHint`. Missing hints take the defaults: a tool is not read-only, and may be destructive and reach an open world. The hints are not verified, but a permission extension can use them to decide which calls to confirm. This confirms the calls Codex asks approval for:
|
|
167
164
|
|
|
168
165
|
```typescript
|
|
169
166
|
pi.on("tool_call", async (event, ctx) => {
|
|
@@ -177,7 +174,7 @@ pi.on("tool_call", async (event, ctx) => {
|
|
|
177
174
|
});
|
|
178
175
|
```
|
|
179
176
|
|
|
180
|
-
A tool that orchestrates other tools can adjust what the model sees while it is active with `prepareLoadout(loadout)`. It runs whenever the active tools change and receives the declared tools, the callable tools, and every registered tool with its exposure and namespace. It returns replacement `descriptions` for declared tools (including its own) and `hiddenDeclarations`: active tools whose declarations requests leave out while they stay active and callable.
|
|
177
|
+
A tool that orchestrates other tools can adjust what the model sees while it is active with `prepareLoadout(loadout)`. It runs whenever the active tools change and receives the declared tools, the callable tools, and every registered tool with its exposure and namespace. It returns replacement `descriptions` for declared tools (including its own) and `hiddenDeclarations`: active tools whose declarations requests leave out while they stay active and callable. A tool can implement the same behavior under a different name using only this hook, `exposure`, and `ctx.executeTool()`.
|
|
181
178
|
|
|
182
179
|
### Activate tools dynamically
|
|
183
180
|
|
|
@@ -185,23 +182,6 @@ Register every tool first, keep optional tools inactive, and use `pi.setActiveTo
|
|
|
185
182
|
|
|
186
183
|
Pi records the initial prompt and tool set in the transcript's first system message, then appends tool and prompt changes before the next model request. Providers that cannot represent the transition receive a complete transcript checkpoint, which can invalidate the cached prefix.
|
|
187
184
|
|
|
188
|
-
### MCP servers
|
|
189
|
-
|
|
190
|
-
`pi.registerMcpServer(name, config)` adds an MCP server for the current session. `config` has the shape of an `mcpServers` entry in [`mcp.json`](mcp.md): `command`, `args`, `env`, and `cwd` for stdio servers, `url`, `headers`, and `oauth` for HTTP servers, plus `exposure`, `toolExposure`, `description`, `enabled`, and `timeout`.
|
|
191
|
-
|
|
192
|
-
```typescript
|
|
193
|
-
pi.registerMcpServer("jira", { url: "https://mcp.example.com/jira", exposure: "codemode" });
|
|
194
|
-
pi.unregisterMcpServer("jira");
|
|
195
|
-
```
|
|
196
|
-
|
|
197
|
-
Servers registered while the extension loads connect when the session starts, together with the `mcp.json` servers; servers registered later connect right away, and `pi.unregisterMcpServer()` closes the connection and makes the server's tools unreachable. Registrations are not saved: register again on every load, for example based on the extension's own settings. A server in `mcp.json` with the same name takes precedence, and `/mcp` shows the override. Registering the same name again replaces the extension's earlier registration; names registered by another extension, invalid names, and invalid configs throw.
|
|
198
|
-
|
|
199
|
-
The built-in MCP support connects registered servers. When nothing does, because another extension replaced it (see [MCP](mcp.md#other-mcp-extensions)), each registration is reported as an extension error. Other MCP extensions can connect registered servers too: read them with `pi.getMcpServers()` on `session_start` and handle the `mcp_servers_change` event for later changes.
|
|
200
|
-
|
|
201
|
-
<a id="extensioncontext"></a>
|
|
202
|
-
<a id="extensioncommandcontext"></a>
|
|
203
|
-
<a id="use-extension-context"></a>
|
|
204
|
-
|
|
205
185
|
### Context and session changes
|
|
206
186
|
|
|
207
187
|
`ExtensionContext` provides the working directory, mode, UI, session manager, model runtime, abort signal, context usage, and controls for compaction and shutdown.
|
package/docs/llama-cpp.md
CHANGED
|
@@ -88,7 +88,7 @@ If the router disconnects, `/llama` shows **Retry** and **Close**. Retry reconne
|
|
|
88
88
|
|
|
89
89
|
## Classification
|
|
90
90
|
|
|
91
|
-
Every model listed for chat is also listed as a classifier model with the same ID and the `llama-cpp-classify` API. Classifier models answer typed `choice`, `bool`, and `score` questions about JSON state, like TypeSafe's Jev models.
|
|
91
|
+
Every model listed for chat is also listed as a classifier model with the same ID and the `llama-cpp-classify` API. Classifier models answer typed `choice`, `bool`, and `score` questions about JSON state, like TypeSafe's Jev models. Both are inert catalog entries in Pi: Pi cannot invoke them; scripts that need `classify()` do not run in Pi. See [Classifier models](models.md#use-classifier-models).
|
|
92
92
|
|
|
93
93
|
The model does not generate an answer. Each question becomes one chat prompt: the state, every question of the request, the state again, and then the question with its answers under single-token labels. Labels are letters for a choice (up to 62 options), `Yes`/`No` for a bool, and digits for a score (up to 10 levels). The second copy of the state is read with the questions in view, which improved accuracy on JevBench with small models. Pi reads the probabilities of the labels as the next token and normalizes them. A choice returns every option's probability and a confidence of `(n * peak - 1) / (n - 1)`; a score returns the expected level.
|
|
94
94
|
|
package/docs/models.md
CHANGED
|
@@ -100,7 +100,9 @@ Choose the conservative end of any published range. A model without a lifetime f
|
|
|
100
100
|
|
|
101
101
|
Compatibility settings should describe verified differences in the endpoint's request or response behavior. Do not enable them based only on an endpoint advertising OpenAI or Anthropic compatibility.
|
|
102
102
|
|
|
103
|
-
|
|
103
|
+
<a id="use-classifier-models"></a>
|
|
104
|
+
|
|
105
|
+
## Classifier models
|
|
104
106
|
|
|
105
107
|
Classifier models do not chat. They answer typed questions about JSON state: pick one of several choices, answer yes or no, or give a score, each with probabilities. Pi includes TypeSafe's Jev model from these providers:
|
|
106
108
|
|
|
@@ -114,26 +116,7 @@ Classifier models do not chat. They answer typed questions about JSON state: pic
|
|
|
114
116
|
|
|
115
117
|
Chat models on a [llama.cpp router](llama-cpp.md#classification) are also listed as classifier models.
|
|
116
118
|
|
|
117
|
-
Classifier models
|
|
118
|
-
|
|
119
|
-
```js
|
|
120
|
-
const jev = await models.getModelOfType("classifier", "typesafe", "jev-latest");
|
|
121
|
-
const result = await models.classify(jev, {
|
|
122
|
-
state: { message: "The change works, thanks." },
|
|
123
|
-
questions: {
|
|
124
|
-
approved: {
|
|
125
|
-
type: "bool",
|
|
126
|
-
instructions: "Does the user approve of the result?",
|
|
127
|
-
criteria: { true: "Approval", false: "No approval" },
|
|
128
|
-
},
|
|
129
|
-
},
|
|
130
|
-
});
|
|
131
|
-
return result.answers;
|
|
132
|
-
```
|
|
133
|
-
|
|
134
|
-
When the service reports token counts, as all System One services do, `result.usage` carries them with their cost. Pi adds the usage of a script's classifier calls to the `codemode` tool result, so it counts toward the session cost in the footer and `/session`. The cost uses the model's catalog price; models without one, such as TypeSafe's direct `jev-latest`, report tokens at no cost.
|
|
135
|
-
|
|
136
|
-
Extensions call classifiers through `ctx.modelRegistry.classify()`, without codemode. [Virtual models](virtual-models.md#route-requests) can use them to route requests; see the `jev-router.ts` example.
|
|
119
|
+
Classifier models remain catalog entries but Pi cannot invoke them: there is no classifier tool and no `classify()` in the extension API. They do not appear in `/model`. Scripts that need `classify()` do not run in Pi.
|
|
137
120
|
|
|
138
121
|
## Add a custom provider
|
|
139
122
|
|
package/docs/sdk.md
CHANGED
|
@@ -109,11 +109,7 @@ Use `DefaultResourceLoader` when you want standard discovery with selected overr
|
|
|
109
109
|
|
|
110
110
|
<a id="inlineextension"></a>
|
|
111
111
|
|
|
112
|
-
Inline extension factories can be supplied through `DefaultResourceLoader`. Give one an `InlineExtension` name only when it needs a stable name in diagnostics and startup output. A named inline extension with `replaceable: true` is left out when another extension registers a tool, command, or flag with a name it registers during loading, instead of both loading with a conflict. The CLI's built-in
|
|
113
|
-
|
|
114
|
-
<a id="codemode-mcp"></a>
|
|
115
|
-
|
|
116
|
-
The CLI loads `codemode`, `tool_search`, and MCP as built-in extensions. SDK sessions do not; add `createCodemodeExtension()`, `createToolSearchExtension()`, and `createMcpExtension()` to the `extensionFactories` of `DefaultResourceLoader`. `codemode` and `tool_search` are registered inactive: enable them through the `defaultTools` setting (`["+codemode", "+tool_search"]` keeps the other default tools), or let the MCP extension activate them: `codemode` for servers with `codemode` exposure, `tool_search` for servers with `deferred` exposure. The MCP extension connects its servers on `session_start`, so call `session.bindExtensions()`. See [Codemode and MCP](../examples/sdk/14-codemode-mcp.ts).
|
|
112
|
+
Inline extension factories can be supplied through `DefaultResourceLoader`. Give one an `InlineExtension` name only when it needs a stable name in diagnostics and startup output. A named inline extension with `replaceable: true` is left out when another extension registers a tool, command, or flag with a name it registers during loading, instead of both loading with a conflict. The CLI's built-in llama.cpp extension is replaceable. A named entry with `builtin: true` is not an inline extension: it supplies the code of the `builtin:<name>` extension, which loads like a configured extension file. It loads by default, is listed in `pi config`, and is disabled by `-builtin:<name>` in the `extensions` setting or by `noExtensions`; `additionalExtensionPaths: ["builtin:<name>"]` loads it explicitly. It loads after project trust is resolved, so it cannot handle `project_trust`. The CLI's built-in extensions use it.
|
|
117
113
|
|
|
118
114
|
See the focused examples for [models](../examples/sdk/02-custom-model.ts), [tools](../examples/sdk/05-tools.ts), [extensions](../examples/sdk/06-extensions.ts), and [full control](../examples/sdk/12-full-control.ts).
|
|
119
115
|
|
|
@@ -134,7 +130,6 @@ See the focused examples for [models](../examples/sdk/02-custom-model.ts), [tool
|
|
|
134
130
|
| [Sessions](../examples/sdk/11-sessions.ts) | Control session persistence and restoration |
|
|
135
131
|
| [Full control](../examples/sdk/12-full-control.ts) | Replace default discovery and state services |
|
|
136
132
|
| [Session runtime](../examples/sdk/13-session-runtime.ts) | Replace the active session safely |
|
|
137
|
-
| [Codemode and MCP](../examples/sdk/14-codemode-mcp.ts) | Add the `codemode`, `tool_search`, and MCP extensions |
|
|
138
133
|
|
|
139
134
|
<a id="exports"></a>
|
|
140
135
|
|
package/docs/security.md
CHANGED
|
@@ -37,7 +37,6 @@ Project trust does not limit what tool calls can access or affect. After Pi star
|
|
|
37
37
|
Pi requires a project-trust decision when it finds any of these resources from the current working directory:
|
|
38
38
|
|
|
39
39
|
- `.pi/settings.json`
|
|
40
|
-
- `.pi/mcp.json`
|
|
41
40
|
- `.pi/extensions`, `.pi/skills`, `.pi/prompts`, or `.pi/themes`
|
|
42
41
|
- `.pi/SYSTEM.md` or `.pi/APPEND_SYSTEM.md`
|
|
43
42
|
- project `.agents/skills` in the current directory or an ancestor directory
|
|
@@ -47,7 +46,6 @@ A bare `.pi` directory does not require project trust.
|
|
|
47
46
|
Granting project trust allows Pi to load:
|
|
48
47
|
|
|
49
48
|
- project settings
|
|
50
|
-
- project MCP servers from `.pi/mcp.json`
|
|
51
49
|
- extensions, skills, prompt templates, themes, and system-prompt files under `.pi`
|
|
52
50
|
- missing packages configured through project settings
|
|
53
51
|
- project-local and project-package extensions
|
package/docs/settings.md
CHANGED
|
@@ -38,16 +38,14 @@ See [Choose a Model](models.md) for model selection and thinking controls.
|
|
|
38
38
|
| Setting | Type | Default | Description |
|
|
39
39
|
|---|---|---|---|
|
|
40
40
|
| `defaultTools` | `string[]` | `read`, `bash`, `edit`, `write` | Tools enabled at startup. Plain names replace the defaults; `+name` adds a tool and `-name` removes one. An empty array disables all built-in tools but not extension or SDK tools. |
|
|
41
|
-
| `codemode.mode` | `"on"` \| `"only"` | `"on"` | How the `codemode` tool presents tools while it is active. `on`: declared tools get their `codemode` declaration appended to their description, and `codemode` lists only tools that are not declared. `only`: `codemode` lists every tool scripts can call, and active built-in and extension tools are hidden from the model, so it reaches them through `codemode`. |
|
|
42
|
-
| `codemode.inlineBudget` | number | `3000` | Estimated tokens (characters / 4) the `codemode` tool's description may spend on tool declarations. Tools that do not fit are left out and found with `searchTools()`. `0` lists only namespaces. |
|
|
43
41
|
|
|
44
|
-
Available built-in tools are `read`, `bash`, `powershell`, `edit`, `write`, `grep`, `find`, and `ls`. `defaultTools` can also name
|
|
42
|
+
Available built-in tools are `read`, `bash`, `powershell`, `edit`, `write`, `grep`, `find`, and `ls`. `defaultTools` can also name extension tools registered inactive.
|
|
45
43
|
|
|
46
|
-
A list of only `+name` and `-name` entries changes the inherited selection instead of replacing it. For example, this enables `
|
|
44
|
+
A list of only `+name` and `-name` entries changes the inherited selection instead of replacing it. For example, this enables `grep` next to the default tools:
|
|
47
45
|
|
|
48
46
|
```json
|
|
49
47
|
{
|
|
50
|
-
"defaultTools": ["+
|
|
48
|
+
"defaultTools": ["+grep"]
|
|
51
49
|
}
|
|
52
50
|
```
|
|
53
51
|
|
|
@@ -157,7 +155,7 @@ Resource paths in user settings resolve from the agent directory. Paths in proje
|
|
|
157
155
|
|
|
158
156
|
Resource arrays support glob exclusions with `!pattern`, exact inclusion with `+path`, and exact exclusion with `-path`. Pi loads resources listed in both user-level and project settings.
|
|
159
157
|
|
|
160
|
-
The built-in
|
|
158
|
+
The built-in extension is named `builtin:llama.cpp` in `extensions`. It loads by default; `-builtin:llama.cpp` disables it. A `+builtin:<name>` or `-builtin:<name>` entry in project settings overrides the user setting. `pi config` lists it under Built-in. `--no-extensions` disables it too, and `-e builtin:<name>` loads it explicitly.
|
|
161
159
|
|
|
162
160
|
## Updates, telemetry, and warnings
|
|
163
161
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@subimpact/e",
|
|
3
|
-
"version": "0.99.
|
|
3
|
+
"version": "0.99.5",
|
|
4
4
|
"description": "Minimal terminal coding harness. Fork of earendil-works/pi (MIT) with the MCP, codemode, and tool-search built-ins removed; compatibility with the classical pi extension/package ecosystem.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"piConfig": {
|