Support DCP config in $OPENCODE_CONFIG_DIR #112
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t-pruning into rewrite-to-use-experimental.chat.messages.transform
Collaborator
|
Hey, this is definitely a good idea, I didn't know even know $OPENCODE_CONFIG_DIR existed. I'm in the middle of a big rewrite due to #5207 getting merged in opencode so I'm going to hold off on this PR until that's done, but i'll definitely get to this after. |
Contributor
Author
|
Perfect! not in a hurry for it, I'll just wait ;) thanks! |
…-and-config-update implement nudge and config update
…nts-to-use-plugin Disallow subagents to use plugin
…-unused-reason-param refactor: remove unused reason parameter from buildAnalysisPrompt
…-unused-reason-param fix: simplify prune tool schema for OAuth plugin compatibility
The nudge counter now correctly resets to zero when prune is used and only counts tools invoked since the last prune. Previously, the counter could become inaccurate across session reloads. Also increased tool cache size to 1000.
…er-reset fix: properly reset nudge counter after prune tool is used
…beta.2 v1.0.0-beta.2 - Fix nudge counter reset
Collaborator
|
Hey @didacog, if you want I can merge this if you rebase it from the dev branch and PR into dev as well, otherwise I'll try to implement it in the next few days :) |
didacog
force-pushed
the
feature/custom-config-path
branch
from
1cd7cfe to
c517f0c
Compare
Contributor
Author
…ool-pruning fix: prevent protected tools from being pruned
…prompt-transform Add system prompt transformation hook
Bump version to 1.0.0-beta.3
…ble-tools-list fix: skip inserting prunable tools list when empty
…une-thinking-blocks chore: remove pruneThinkingBlocks from config
Tarquinen
force-pushed
the
feature/custom-config-path
branch
from
c517f0c to
e1eb62e
Compare
Tarquinen
added a commit
that referenced
this pull request
Dec 15, 2025
Support DCP config in $OPENCODE_CONFIG_DIR (updated from PR #112 to latest dev branch rebase)
Collaborator
|
moved to #135, thank you for the help! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds support for loading DCP config from
$OPENCODE_CONFIG_DIR/dcp.jsonc(ordcp.json), aligning the plugin with OpenCode’s custom config directory behavior.Details
lib/config.ts:getConfigPathsto also resolve a config path from$OPENCODE_CONFIG_DIR/dcp.jsoncordcp.jsonwhenOPENCODE_CONFIG_DIRis set.getConfignow merges config in this order:~/.config/opencode/dcp.jsonc$OPENCODE_CONFIG_DIR/dcp.jsonc.opencode/dcp.jsonc~/.config/opencode/dcp.jsoncis still created automatically on first run.OPENCODE_CONFIG_DIR.This makes DCP configuration placement align with OpenCode’s OPENCODE_CONFIG_DIR behavior, without changing any existing defaults or project-level overrides.