How to Report Incorrect Repository Information for DeepSeek-Reasonix

Report incorrect repository information by verifying the discrepancy against the source code in internal/config/load.go or related files, then open a GitHub issue with reproduction steps, CLI output, and links to the specific source files that contradict the documentation.

DeepSeek-Reasonix is a single-binary, Go-based coding agent accessible via CLI/TUI, desktop app, or editor extension. When documentation, configuration defaults, or API specifications diverge from the actual implementation in the codebase, users need a systematic way to verify and report these issues. This guide walks you through identifying, verifying, and reporting incorrect repository information using specific source file paths and CLI commands from the esengine/DeepSeek-Reasonix repository.

Types of Incorrect Information You Might Encounter

Before filing a report, identify which category of information contains the error. The most common discrepancies involve documentation mismatches, configuration defaults, pricing data, or legacy migration logic.

Documentation Mismatches

Documentation errors occur when the guides in docs/ describe behavior that contradicts the implementation in internal/. For example, if docs/CONFIG_PATHS.md claims a default value that differs from the Default() function in internal/config/config.go, this constitutes a documentation mismatch.

Verify by running reasonix run "config show" and comparing the output against the documentation tables.

Configuration Default Errors

Configuration defaults are hardcoded in internal/config/default.go and merged via LoadForRoot in internal/config/load.go【/cache/repos/github.com/esengine/DeepSeek-Reasonix/main-v2/internal/config/load.go†L21-L38】. If the documented default for a setting like desktop.currency differs from what reasonix run "config show" displays, the defaults may be incorrect.

API Pricing Inaccuracies

Pricing information for DeepSeek models is populated by backfillDeepSeekOfficialPrices in internal/config/load.go. If reasonix run "list models" displays prices that do not match the official DeepSeek pricing page, the backfill logic contains incorrect data.

Legacy Migration Bugs

The configuration system performs automatic migrations via functions like MigrateLegacyAgentStepLimitsForRoot and migrateRetiredConfigKeysFile【/cache/repos/github.com/esengine/DeepSeek-Reasonix/main-v2/internal/config/load.go†L45-L55】. If running reasonix run "config migrate-legacy-agent-step-limits" fails to remove deprecated keys such as max_steps or corrupts the TOML file, the migration logic is faulty.

Verify the Discrepancy Using CLI Commands

DeepSeek-Reasonix provides several introspection commands to surface runtime configuration and provider information. Use these to gather evidence before opening an issue.

Show Effective Configuration

Run the following command to display the fully merged configuration after applying all TOML and MCP sources:

reasonix run "config show"

This executes the internal config command, printing values that combine built-in defaults, user-wide config (~/.reasonix/config.toml), project-level reasonix.toml, and MCP .mcp.json files. Compare this output against the claims in docs/CONFIG_PATHS.md or docs/GUIDE.md.

List Loaded Providers

To verify provider information or check for missing model entries:

reasonix run "providers list"

This prints each provider name, base URL, and available models. Cross-reference this list with the provider tables in docs/PLUGIN_PACKAGES.md. If a provider described in documentation does not appear, or if pricing information differs, you have found a discrepancy.

Validate TOML Files Programmatically

For configuration validation without side effects, use the ValidateFile helper from internal/config/load.go【/cache/repos/github.com/esengine/DeepSeek-Reasonix/main-v2/internal/config/load.go†L97-L115】:

package main

import (
	"fmt"
	"log"

	"reasonix/internal/config"
)

func main() {
	if err := config.ValidateFile("reasonix.toml"); err != nil {
		log.Fatalf("Invalid config: %v", err)
	}
	fmt.Println("Config is valid")
}

Compile and run this snippet with go run . to confirm that a project's reasonix.toml parses correctly. If validation fails against the documented schema, include the error message in your report.

Gather Technical Evidence

Once you identify a discrepancy, collect the following evidence to support your GitHub issue:

1. Source file links – Link directly to the GitHub blob URLs for the files containing the error (e.g., https://github.com/esengine/DeepSeek-Reasonix/blob/main-v2/internal/config/load.go).
2. Function references – Note specific functions like mergeTOMLProviders or backfillDeepSeekOfficialPrices that implement the incorrect logic.
3. CLI output – Copy the output from reasonix run "config show" or reasonix run "providers list" that contradicts the documentation.
4. Before/after snapshots – For migration bugs, provide the TOML file content before and after running reasonix run "config migrate-legacy-agent-step-limits".
5. Environment details – Include your go version, operating system, and DeepSeek-Reasonix version (check reasonix --version).

File a GitHub Issue

Navigate to the repository's Issues page and click "New issue". The .github/ISSUE_TEMPLATE/ directory contains templates that prompt for the information above.

Structure your issue with:

• Title – A concise summary such as "Incorrect default desktop.currency in CONFIG_PATHS.md" or "Missing max_steps migration in LoadForRoot".
• Description – What you expected based on documentation, what you observed in the code or CLI output, and why the discrepancy matters.
• Reproduction steps – Exact commands you ran (e.g., reasonix run "config show"), configuration snippets, and environment details.
• Links – Direct GitHub links to the source files that appear incorrect, specifically referencing lines in internal/config/load.go, internal/provider/provider.go, or related files.
• Proposed fix – Optional suggestion for correcting the documentation or code, or a minimal pull request if you have already implemented the fix.

Summary

• Identify the type of incorrect information: documentation mismatch, configuration default error, API pricing inaccuracy, or legacy migration bug.
• Verify discrepancies using introspection commands like reasonix run "config show" and reasonix run "providers list".
• Gather technical evidence including source file paths (internal/config/load.go), function names (LoadForRoot, migrateRetiredConfigKeysFile), and CLI output.
• Report via GitHub Issues with a clear title, reproduction steps, environment details, and links to the contradictory source code.

Frequently Asked Questions

What specific details should I include when reporting incorrect repository information?

Include the exact file path and function name where the error occurs (such as internal/config/load.go line 21-38 for LoadForRoot), the CLI output that contradicts documentation, your DeepSeek-Reasonix version, and a link to the GitHub blob URL of the offending source file. This allows maintainers to verify the issue against the actual implementation quickly.

How do I verify if a configuration default is actually incorrect?

Run reasonix run "config show" to see the effective configuration, then compare the output against the claims in docs/CONFIG_PATHS.md or internal/config/default.go. If the runtime value differs from the documented default, inspect the Default() function in internal/config/config.go and the merging logic in mergeTOMLProviders to confirm the discrepancy.

Where does DeepSeek-Reasonix store pricing information for models?

Model pricing is backfilled via backfillDeepSeekOfficialPrices in internal/config/load.go. Run reasonix run "list models" to view the current pricing, then compare it against the official DeepSeek pricing page. If the values diverge, the backfill function contains stale data and should be reported as incorrect repository information.

How can I test legacy configuration migrations safely?

Create a temporary reasonix.toml file containing deprecated keys like max_steps, then run reasonix run "config migrate-legacy-agent-step-limits" to trigger MigrateLegacyAgentStepLimitsForRoot. Inspect the file afterward to verify the key was removed without data loss. Include before-and-after file contents in your GitHub issue if the migration fails or produces unexpected results.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}