Skip to content

Quality configuration #13207

Closed as not planned
Closed as not planned

Description

@florianleibert

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

Activity

  1. github-actions commented on Feb 11, 2026

    @github-actions
    Contributor

    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.

  2. github-actions commented on Feb 11, 2026

    @github-actions
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

needs:complianceThis means the issue will auto-close after 2 hours.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions