snowspeeder/pi-web
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify Pi-compatible agent profiles

Browse Source
This commit is contained in:
Federico Jaramillo Martinez
2026-07-14 00:30:09 +02:00
parent 8b5ccc2fd9 a1f749cdb6
commit ca07e48c0a
38 changed files with 1282 additions and 160 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/server/sessions/sessionService.ts
+4 -3
View File
@@ -25,15 +25,16 @@ export type SessionRouteLookup = string | SessionRouteRef;
/**
* Route-facing session contract for PI WEB's HTTP/WebSocket API.
*
* Keep this surface neutral: implementations may be backed by the native Pi SDK,
* an out-of-process agent bridge, or another daemon. Pi-specific lifecycle hooks
* such as auth-change handling and daemon shutdown stay on the concrete service.
* Keep transport concerns separate from the bundled Pi SDK implementation so
* routes remain testable. Pi-specific lifecycle hooks such as auth-change
* handling and daemon shutdown stay on the concrete service.
*/
export interface SessionRouteService {
list(cwd: string): Promise<ClientSession[]>;
start(cwd: string): Promise<ClientSession>;
messages(ref: SessionRouteLookup, page?: { before?: number; limit?: number }): Promise<unknown[] | ClientMessagePage>;
status(ref: SessionRouteLookup): Promise<ClientSessionStatus>;
clearQueue(ref: SessionRouteLookup): Promise<ClientSessionStatus>;
availableModels(ref: SessionRouteLookup): Promise<ClientSessionModel[]>;
setModel(ref: SessionRouteLookup, provider: string, modelId: string): Promise<ClientSessionStatus>;
cycleModel(ref: SessionRouteLookup, direction: "forward" | "backward"): Promise<ClientSessionStatus>;