anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Quality configuration #9115

New Issue
Closed
opened 2026-02-16 18:11:40 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 18:11:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @florianleibert on GitHub (Feb 11, 2026).

Originally assigned to: @thdxr on GitHub.

Task: Quality configuration

Description

Extend the opencode config system to support quality monitoring settings. Add a quality section to Config.Info with all configurable options including scoring weights, regression thresholds, logging preferences, and database path.

Acceptance Criteria

  • quality key added to Config.Info Zod schema in packages/opencode/src/config/config.ts
  • All settings have sensible defaults (enabled: true, logging: true, logLevel: "normal", etc.)
  • Weights sub-object: correctness (40), userFeedback (35), staticAnalysis (25)
  • Regression sub-object: threshold (15), windowSize (20), alertLevel ("moderate")
  • Paths configurable: dbPath (".opencode/quality.db"), logPath (".opencode/quality.log")
  • retentionDays configurable (default: 90)
  • Quality config accessible via Config.get() following existing patterns
  • Config validates that weights sum to 100 (or normalizes them)
  • Zod schemas exported for reuse in other quality modules

Technical Details

  • Modify packages/opencode/src/config/config.ts — add quality to the Config.Info schema
  • Use .optional() so existing configs without quality section continue to work
  • Follow the pattern used by compaction and experimental config sections
  • Export quality config type for use in packages/opencode/src/quality/ modules

Dependencies

  • None — this is a foundation task

Effort Estimate

  • Size: S
  • Hours: 2-3
  • Parallel: true
Originally created by @florianleibert on GitHub (Feb 11, 2026). Originally assigned to: @thdxr on GitHub. # Task: Quality configuration ## Description Extend the opencode config system to support quality monitoring settings. Add a `quality` section to `Config.Info` with all configurable options including scoring weights, regression thresholds, logging preferences, and database path. ## Acceptance Criteria - [ ] `quality` key added to `Config.Info` Zod schema in `packages/opencode/src/config/config.ts` - [ ] All settings have sensible defaults (enabled: true, logging: true, logLevel: "normal", etc.) - [ ] Weights sub-object: correctness (40), userFeedback (35), staticAnalysis (25) - [ ] Regression sub-object: threshold (15), windowSize (20), alertLevel ("moderate") - [ ] Paths configurable: dbPath (".opencode/quality.db"), logPath (".opencode/quality.log") - [ ] retentionDays configurable (default: 90) - [ ] Quality config accessible via `Config.get()` following existing patterns - [ ] Config validates that weights sum to 100 (or normalizes them) - [ ] Zod schemas exported for reuse in other quality modules ## Technical Details - Modify `packages/opencode/src/config/config.ts` — add `quality` to the Config.Info schema - Use `.optional()` so existing configs without quality section continue to work - Follow the pattern used by `compaction` and `experimental` config sections - Export quality config type for use in `packages/opencode/src/quality/` modules ## Dependencies - [ ] None — this is a foundation task ## Effort Estimate - Size: S - Hours: 2-3 - Parallel: true
yindo added the needs:compliance label 2026-02-16 18:11:40 -05:00
yindo closed this issue 2026-02-16 18:11:40 -05:00
yindo commented 2026-02-16 18:11:40 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 11, 2026):

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

  • This issue must use one of our three required templates: Bug Report, Feature Request, or Question
  • Currently, the issue is formatted as a task/implementation specification, which is not a valid template format
  • Please reformat as a Feature Request (if proposing new functionality) or another appropriate template

Additionally, this appears to be related to epic #13201 (add-regression-detection). Consider linking them with a comment like 'Part of #13201' for clarity.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions[bot] commented on GitHub (Feb 11, 2026): <!-- issue-compliance --> This issue doesn't fully meet our [contributing guidelines](../blob/dev/CONTRIBUTING.md). **What needs to be fixed:** - This issue must use one of our three required templates: **Bug Report**, **Feature Request**, or **Question** - Currently, the issue is formatted as a task/implementation specification, which is not a valid template format - Please reformat as a Feature Request (if proposing new functionality) or another appropriate template Additionally, this appears to be related to epic #13201 (add-regression-detection). Consider linking them with a comment like 'Part of #13201' for clarity. Please edit this issue to address the above within **2 hours**, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know.
yindo commented 2026-02-16 18:11:40 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 11, 2026):

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.

@github-actions[bot] commented on GitHub (Feb 11, 2026): This issue has been automatically closed because it was not updated to meet our [contributing guidelines](../blob/dev/CONTRIBUTING.md) within the 2-hour window. Feel free to open a new issue that follows our issue templates.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label needs:compliance
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9115
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?