Compaction secret redaction matches argument names, not values

Open
#1,221 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
security

Research direction

Read .github/meta/harness-review-followups.md and packages/opencode/src/session/compaction.ts:62-75, starting with isSensitiveArgName and the compaction ledger flow. Trace how arguments enter synthetic prompts after tool output pruning. Done means sensitive values in URLs or free text are protected through allowlisted metadata and value-level detection, rather than argument-name matching alone.

Written by the indexing model from the issue text.

Description

Deferred from the v0.10.0 release review. Self-disclosed in .github/meta/harness-review-followups.md.

Compaction redacts sensitive tool arguments by argument name (isSensitiveArgName, packages/opencode/src/session/compaction.ts:62-75). A secret that appears in a value rather than a recognisably-named argument — inside a URL, or in free text — is not matched.

Because the compaction ledger is replayed into later synthetic prompts, an unmatched secret can be re-sent after the tool output it came from has been pruned.

Name-based matching cannot close this. It needs allowlisted metadata plus value-level secret detection.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.