[workers] Give Workers a neutral identity across the four runtimes

Aperta
  • Qualcosa non va?
#191 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, typescript
Ambito
ai, infrastructure

Direzione di ricerca

Start with the Pi host's native resource loader and prompt path in packages/pi-runtime-host/src/host.ts (around lines 641, 714, 717 and 397), and the stock image in containers/workers/Dockerfile:284. The first step is qualifying each pinned runtime's effective stock identity, which the issue says must precede any edit, and it needs owner acceptance in docs/specs/20260716-pi_worker_adapter.md and docs/specs/20260721-worker_execution_environment_images.md. Done means a fresh home on each runtime receives a neutral identity through its qualified mechanism, with retained homes left untouched.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Summary

Qualify the stock identity of Codex, Pi, OpenCode and DeepSeek, then deliver one domain-neutral Worker identity through each runtime's native prompt mechanism. A source audit establishes a Pi coding-assistant fallback in the locally installed package; that installed version differs from the current repository pin, and the other three stock prompts remain unqualified.

Category

bug

Area

Worker runtime native prompts and image defaults

Observed behavior and evidence

Pi's host constructs its native resource loader without a system-prompt override (packages/pi-runtime-host/src/host.ts:641), reloads it (packages/pi-runtime-host/src/host.ts:714), passes it to the native session (packages/pi-runtime-host/src/host.ts:717) and prompts that session (packages/pi-runtime-host/src/host.ts:397). The stock image deploys this host (containers/workers/Dockerfile:284).

A source audit traced the fallback in upstream package @earendil-works/pi-coding-agent, locally installed version 0.99.1: dist/core/resource-loader.js discovers a native SYSTEM.md, dist/core/agent-session.js passes the loader's prompt into session prompt construction, and dist/core/system-prompt.js supplies a coding-assistant identity when no custom prompt is present. The repository host's native-loader-to-session path is the consumption seam cited above. Current source pins version 1.0.2 (packages/pi-runtime-host/package.json:19), so the inspected 0.99.1 bytes do not qualify the current stock pin. A custom image, trusted project prompt or retained home can also change the effective identity; no deployed prompt exchange was captured.

Codex, DeepSeek and OpenCode stock prompts were not qualified by this source audit. The audited Pi result does not establish their identities or prove that every deployed Worker receives the same prompt. The maintainers explicitly deferred neutral Worker identity across all four runtimes and named the Worker environment and runtime communication owners for amendment (docs/decisions/20261010-tasks_are_general_work.md:10).

Impact

The audited Pi fallback frames legal document comparison and invoice processing as coding. A neutral Task request alone does not qualify the runtime's own identity. Consistent general-work defaults across all four current stock runtimes remain a post-release requirement.

Suggested fix

First inspect and qualify each current pinned runtime's effective stock identity and its actual native prompt producer-to-consumer path, including Pi's version 1.0.2. Deliver one neutral Worker identity as an ordinary default through each runtime's qualified native mechanism. For Pi, qualify the native SYSTEM.md default path identified by the audit against the current pin. Avoid assuming that all runtimes use the same file or selector.

Accept the neutral-identity criteria in the Worker Execution Environment Images and Worker Runtime Communication Model owners before implementation, as required by the maintainers' decision. Preserve user-authored prompt precedence under the adapter owners; Pi's native precedence is explicit (docs/specs/20260716-pi_worker_adapter.md:74). Follow the existing image-default boundary (docs/specs/20260721-worker_execution_environment_images.md:90) and never synchronize or reseed retained homes to apply a new default (docs/specs/20260721-worker_execution_environment_images.md:92). No new prompt-profile schema is needed. Any proposed change to native precedence or retained-home policy requires a separate accepted owner amendment.

Acceptance criteria

  • Maintainers accept the neutral-identity criteria in the Worker environment and runtime communication owners before implementation.
  • Qualification records each of the four pinned runtimes' effective stock identity and the native mechanism that actually delivers its prompt.
  • A fresh uncustomized home on each stock runtime receives the neutral Worker identity through that mechanism; the consumed prompt supports general work without assuming code, tests, Git or a code host.
  • Legal document comparison and invoice-summary requests retain their requested objective under each runtime's default identity; another runtime's result cannot substitute for this proof.
  • A user-authored native prompt retains its precedence, and updating the stock image leaves retained home bytes untouched without reseeding.
  • Missing or unsafe native default sources fail qualification visibly rather than being counted as delivered merely because an image contains a prompt file.

References

  • packages/pi-runtime-host/src/host.ts:397
  • packages/pi-runtime-host/src/host.ts:641
  • packages/pi-runtime-host/src/host.ts:714
  • packages/pi-runtime-host/src/host.ts:717
  • containers/workers/Dockerfile:284
  • packages/pi-runtime-host/package.json:19
  • docs/decisions/20261010-tasks_are_general_work.md:10
  • docs/specs/20260716-pi_worker_adapter.md:74
  • docs/specs/20260721-worker_execution_environment_images.md:90
  • docs/specs/20260721-worker_execution_environment_images.md:92

Filed from the v0.1.0 acceptance-program inventory.

Lingua principale
TypeScript
Stelle
0
Fork
1
Merge medio
3h 54m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di lingkaix/openkit

Tutte le issue di lingkaix/openkit

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.