sscoble/pi-mono
1
0
Fork 0
mirror of https://github.com/badlogic/pi-mono.git synced 2026-11-05 23:37:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

fix(coding-agent): make model refresh cancellation caller-owned

Browse source 
Add generation-safe catalog publication, cancellable auth and storage operations, locally consistent credential mutations, and cache-first interactive model flows.
This commit is contained in:
Mario Zechner 2026-08-04 00:00:12 +02:00
parent b06dc76fd7
commit fed6009cc9
86 changed files with 3426 additions and 870 deletions
Download patch file Download diff file Expand all files Collapse all files

23
packages/coding-agent/docs/sdk.md
View file

@ -452,7 +452,7 @@ for (const provider of modelRuntime.getProviders()) {
}
// Runtime API key override (not persisted to disk)
modelRuntime.setRuntimeApiKey("anthropic", "sk-my-temp-key");
await modelRuntime.setRuntimeApiKey("anthropic", "sk-my-temp-key");
// Custom credential and model locations
const customRuntime = await ModelRuntime.create({
@ -469,6 +469,24 @@ const { session } = await createAgentSession({
});
```
`login()`, `logout()`, `setRuntimeApiKey()`, and `removeRuntimeApiKey()` resolve after the affected provider's cached/built-in catalog, composition, and availability snapshot are locally consistent. They do not wait for remote catalog freshness. If credentials were committed but local synchronization fails, they reject with the exported `CredentialSynchronizationError`; inspect its `providerId`, `operation`, `credential`, and `cause` fields instead of retrying the credential mutation blindly.
Public model/auth operations and `ModelRuntime.create({ signal })` accept optional abort signals and are unbounded when omitted. SDK applications own deadline policy for remote catalog freshness:
```typescript
const signal = AbortSignal.timeout(15_000);
const result = await modelRuntime.refresh({
providers: ["anthropic"],
signal,
});
if (result.aborted) console.warn("Catalog refresh timed out; using cached models");
for (const [providerId, error] of result.errors) {
console.warn(`Could not refresh ${providerId}:`, error);
}
```
A failed or timed-out network refresh does not undo a successful credential operation. `refresh()` starts a new provider generation, so it does not wait behind an older stalled refresh and stale generations cannot publish afterward.
> See [examples/sdk/09-api-keys-and-oauth.ts](../examples/sdk/09-api-keys-and-oauth.ts)
### System Prompt
@ -938,7 +956,7 @@ const modelRuntime = await ModelRuntime.create({
modelsPath: "/custom/agent/models.json",
});
if (process.env.MY_KEY) {
modelRuntime.setRuntimeApiKey("anthropic", process.env.MY_KEY);
await modelRuntime.setRuntimeApiKey("anthropic", process.env.MY_KEY);
}
// Inline tool
@ -1144,6 +1162,7 @@ AgentSessionRuntime
// Auth and Models
ModelRuntime // implements pi-ai Models and owns credential storage
ModelRegistry // synchronous extension compatibility facade
CredentialSynchronizationError
resolveCliModel
resolveModelScopeWithDiagnostics