chore: add .opencode/dcp.jsonc with compress.protectTags enabled
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- json
- Domain
- tooling
Research direction
Read opencode.json and check where protectTags is currently set. Remove that top-level key and add .opencode/dcp.jsonc with the schema URL and compress.protectTags setting shown in the issue. Done means the DCP setting is in the project-level config and the invalid key is no longer in opencode.json.
Written by the indexing model from the issue text.
Description
Problem
Slash command files use <protect> tags to mark execution-critical sections (guardrails, checklists, mandatory gates) that must survive DCP context compression. However, these tags are inert without a DCP config file that enables them.
Additionally, the replicator repo currently has "protectTags": true at the top level of opencode.json, which causes:
Configuration is invalid at opencode.json
↳ Unrecognized key: protectTags
Fix
- Remove
"protectTags": truefromopencode.json - Add
.opencode/dcp.jsoncto the repo with:
{
"$schema": "https://raw.githubusercontent.com/Opencode-DCP/opencode-dynamic-context-pruning/master/dcp.schema.json",
"compress": {
"protectTags": true
}
}
This file should be committed to source control (project-level setting, not personal config).
Context
protectTagsis a DCP plugin config key undercompress, not an OpenCode core config key- Placing it in
opencode.jsoncauses the startup error shown above - The correct location is
.opencode/dcp.jsonc(ordcp.json) - Related: unbound-force/unbound-force#497, unbound-force/unbound-force#499
- Dominant language
- Go
- Stars
- 0
- Forks
- 9
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 18
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 unbound-force/replicator
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#95 ·
Maintainers usually reply within 1 day
-
bug github_actions
Difficulty 2/5 Under an hour Newbie friendliness 80/100
unbound-force/replicator#89 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#85 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#63 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
unbound-force/replicator#52 ·
Maintainers usually reply within 1 day
All issues in unbound-force/replicator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OneBusAway/maglev#2102 ·
Maintainers usually reply within 2 days
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day