Task Tool Invocation
Subagent type: worker
Task description: Investigate Worker /chat code
Context
You are a specialized subagent invoked by another agent within an ongoing Factory session.
You operate in your own context window but your work directly supports the parent workflow.
Your Subagent Identity
Your core identity and specialized capabilities are defined by the following system prompt:
---BEGIN SUBAGENT SYSTEM PROMPT---
Worker Droid
You are a general-purpose worker agent. Complete your assigned task precisely and report results.
Key guidelines:
- Complete the task and return what the caller asked for, in the format they specified.
- Report concrete actions taken and their outcomes
- Note any blockers or required follow-ups
---END SUBAGENT SYSTEM PROMPT---
Mission
Follow the instructions from your subagent system prompt and the task below.
Complete only what is explicitly requested. Stop immediately once the task is done.
Non-negotiable rules
- Stay strictly within scope. Do not add features, investigations, or commentary beyond the task.
- Do not pursue tangents or make proactive suggestions outside the described work.
- If something is unclear or blocked, report it instead of guessing or expanding scope.
- NEVER run destructive
rm -rf commands (e.g. rm -rf /, rm -rf ~). Commands targeting only /tmp are allowed.
Task
Execute the following assignment precisely and efficiently. Do not perform any other work.
---BEGIN TASK FROM PARENT AGENT---
Goal: Produce a deterministic refactor map for the Cloudflare Worker so an implementation feature can be scoped precisely. Read-only investigation. No edits, no commits.
Repo root: /Users/gaganarora/Desktop/my projects/teachr.live-wt-mission-1
Files to read in full:
- worker/src/routes/chat.ts
- worker/src/index.ts
- worker/src/routes/transcribe-token.ts (for env-var pattern reference, do not modify)
- worker/src/routes/tts.ts (for passthrough pattern reference, do not modify)
- worker/wrangler.toml
- worker/.dev.vars.example
- worker/package.json
- worker/tsconfig.json
- worker/tests/passthrough.test.ts (and any other files in worker/tests/)
- worker/scripts/ (whatever is there)
- worker/README.md
Then produce a single markdown report and write it to:
/Users/gaganarora/.factory/missions-tmp/m2-investigation/worker-refactor-map.md
(create the directory if it does not exist; mkdir -p with quoted path)
The report MUST contain these sections, in order, with exact code citations (file:line ranges):
A. Current /chat upstream contract
- Exact upstream URL and HTTP method
- Exact auth header(s) sent (e.g., x-api-key, anthropic-version)
- Whether request body is forwarded as-is, mutated, or constructed
- Whether response body is forwarded as a stream (ReadableStream piped) or buffered
- Cite the exact lines that prove passthrough discipline (no .text/.json/.arrayBuffer)
B. Current Env type and config surface
- The Env interface fields (with types)
- Which env var holds the upstream API key today
- Where wrangler.toml and .dev.vars.example reference these names
- Any other env vars that flow through /chat
C. Current passthrough test coverage
- For each test in worker/tests/passthrough.test.ts: name, what it asserts, and which lines exercise the upstream-specific assumptions (e.g., "asserts upstream is api.anthropic.com")
- Identify which assertions are upstream-agnostic (carry over) and which are upstream-specific (must change)
D. Refactor delta for Z.ai swap
For each change required, cite exact file:line:
- URL change (from → to)
- Auth header change (from → to)
- Env var rename (from → to) and every site that references it
- Default model literal change site (where "claude-..." or model id lives, → "glm-5.1")
- Any request-body shape work the Worker must do (the brief says NONE — verify by reading; if Worker constructs body today, flag it as a violation of pure passthrough that must be removed)
- Any response-body shape work the Worker does today (must be NONE)
- Test changes required, with old assertion → new assertion mapping
E. Risks and surprises
- Any code in /chat that today depends on Anthropic-specific bytes/headers and would silently misbehave with OpenAI-shape SSE
- Any retry, timeout, or error-mapping logic that bakes in Anthropic semantics
- Anything else a worker should know before touching this code
F. Concrete F1 scope
A bulleted list of exact files the F1 worker will modify, with a one-line summary per file. No more, no less.
G. Verification commands the F1 worker can run
- npm install path
- npm test path (the exact command run from worker/ )
- Local wrangler dev command (with port if any)
- A curl one-liner that exercises /chat against wrangler dev (placeholder for ZAI_API_KEY)
Constraints:
- Cite line numbers. Do not paraphrase code without citation.
- If a file is missing or empty, say so explicitly.
- All shell paths in your report must be double-quoted (the repo path has spaces).
- Final response to me MUST include the absolute path of the report file you wrote AND a 5-bullet executive summary inline. Nothing else inline; the depth lives in the file.
---END TASK FROM PARENT AGENT---
Reporting requirements
- Summarize the concrete actions you took and their outcomes.
- If you wrote output to any files, clearly list every file path so the caller can retrieve them.
- Note any blockers, uncertainties, or required follow-ups.
- Provide key outputs or findings relevant to the task, nothing more.
