feat: support custom pi model configs, with registry-resolvable model IDs and distinct model error codes (#450)

This commit is contained in:
ezl-keygraph authored and GitHub committed 2026-09-08 14:54:37 +05:30
1 parent 4b8131fdd5
commit d41d52f17d
20 files changed
+441 -124

No files matched your search

+7
View File
@@ -407,6 +407,7 @@ export interface WorkerOptions {
containerName: string;
envFlags: string[];
config?: { hostPath: string; containerPath: string };
modelsConfig?: { hostPath: string; containerPath: string };
promptsDir?: string;
outputDir?: string;
workspace: string;
@@ -469,6 +470,12 @@ export function spawnWorker(opts: WorkerOptions): ChildProcess {
args.push('-v', `${opts.config.hostPath}:${opts.config.containerPath}:ro`);
}
// pi model config. The mount is the only signal the worker gets: it detects the file at
// this fixed path, so nothing about --models-config travels through the environment.
if (opts.modelsConfig) {
args.push('-v', `${opts.modelsConfig.hostPath}:${opts.modelsConfig.containerPath}:ro`);
}
// Customer-copy destination. The workflow surfaces only final report artifacts here.
if (opts.outputDir) {
args.push('-v', `${opts.outputDir}:/app/output`);