mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-27 11:20:42 +01:00
Harold KimandPaperclip
98df214917
When reusing a Codex sandbox, the workspace-restore step now performs an auth-merge check before adopting the sandbox's auth.json. The merge fails closed when: - host or sandbox Codex auth is unusable (missing token or account) - the subscription payload shapes differ between host and sandbox - subscription account identities do not match Additional hardening: node absence on PATH during the embedded decision script now exits non-zero instead of silently falling through. Co-change comments link parseAuth (the embedded script) to hasUsableAuthPayload (codex-home.ts) so a future auth-format change cannot silently diverge between the two implementations. Co-Authored-By: Paperclip <noreply@paperclip.ing>
3.8 KiB
3.8 KiB
Thinking Path
- Paperclip is the open source app people use to manage AI agents for work
- [Which subsystem or capability is involved]
- [What problem or gap exists]
- [Why it needs to be addressed]
- This pull request ...
- The benefit is ...
Linked Issues or Issue Description
What Changed
Verification
Risks
For core feature work, check
ROADMAP.mdfirst and discuss it in#devbefore opening the PR. Feature PRs that overlap with planned core work may need to be redirected — check the roadmap first. SeeCONTRIBUTING.md.
Model Used
Checklist
- I have included a thinking path that traces from project context to this change
- I have specified the model used (with version and capability details)
- I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work
- I have searched GitHub for duplicate or related PRs and linked them above
- I have either (a) linked existing issues with
Fixes: #/Closes #/Refs #OR (b) described the issue in-PR following the relevant issue template - I have not referenced internal/instance-local Paperclip issues or links (only public GitHub
#NNN/github.com/paperclipai/paperclipURLs) - My branch name describes the change (e.g.
docs/...,fix/...) and contains no internal Paperclip ticket id or instance-derived details - I have run tests locally and they pass
- I have added or updated tests where applicable
- I have updated relevant documentation to reflect my changes
- I have considered and documented any risks above
- All Paperclip CI gates are green
- Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- I will address all Greptile and reviewer comments before requesting merge