[worker-image] Remove the unproduced Anthropic API-key carrier branch
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- devops
Research direction
Read containers/workers/openkit-worker-shim around line 51 and containers/worker-runtimes/smoke.sh around line 28. Find every producer or carrier handling for ANTHROPIC_API_KEY, remove that handling, and retain the smoke test’s assertion that the carrier is absent. Qualify the sanitized launcher with the carrier absent; do not add a replacement carrier or launcher exception.
Written by the indexing model from the issue text.
Description
Audit question Q-134.
The image smoke requires the carrier to be absent, but the sanitized launcher still tests it and conditionally copies ANTHROPIC_API_KEY.
Evidence: containers/workers/openkit-worker-shim:51 and containers/worker-runtimes/smoke.sh:28.
Remove that conditional branch and any remaining producer/carrier handling; retain the absence assertion.
Declared runtime-env delivery remains with Agent Manifest And AEP Resolution; add no replacement carrier or launcher exception.
The image and Pi specifications in this batch apply the supplied Q-134 settlement. Qualify the sanitized launcher with the carrier absent.
Found by the independent documentation audit; answered by coordinator and consultant consensus under the engineer's delegation of 2026-10-30 (record docs/audits/20261030-independent_doc_audit_answers_p4.md). v0.1.0.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 3h 54m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lingkaix/openkit
-
bug doc-audit
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug doc-audit
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug doc-audit
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug doc-audit
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in lingkaix/openkit
Similar issues
-
bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
PhyberApex/kuroshiro#1687 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/monaco-editor#5563 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 86/100
awslabs/visual-asset-management-system#937 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100