Reported issues for redcon

Pod holds 16 of 17 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to redcon.

Most discussed

feat(install): Claude Code Plugin Marketplace manifest (.claude-plugin/plugin.json)

Problem

The 'Zero-install (recommended)' README path lands users on `claude mcp add redcon -- uvx redcon-mcp`. That works, but it's still a manual one-liner. The real one-click experience is the Claude Code Plugin Marketplace: a user runs `/plugin install redcon-mcp@` and it's done.

To get there, we need:

A `.claude-plugin/plugin.json` manifest in the repo so the package describes itself correctly to the marketplace.
A README section pointing at the marketplace ins

Read the thread · 2026-05-07 · closed · 1 comment

feat(scorer): mention-weighted personalised PageRank for MCP rank flow

Problem

Aider's repo map wins on hard tasks (e.g. 'audit TLS verification') because its personalised PageRank uses the current chat turn's identifiers as the personalisation vector - files defining symbols the user just mentioned dominate the random walk. Redcon already has personalised PR (`redcon/scorers/relevance.py:251`), but the personalisation vector is built only from task-keyword seeds. There's no way for the agent to say 'I just talked about `authenticate` and `rate_limit

Read the thread · 2026-05-07 · closed · 1 comment

feat(mcp): layered match cascade in batch_edit (exact -> whitespace -> indent)

Problem

`redcon_batch_edit` currently does exact string-replace only. If the agent's `old_string` differs from the on-disk text by even a single space - extra trailing whitespace, tabs vs spaces, an indent shift from a recent reformat - the edit is skipped with 'old_string not found'. The user has to re-read the file and try again.

This is a measurable cliff for weaker / cheaper models. Aider's strength here is well-documented: their edit format applies a cascade (exact -> whitespace-in

Read the thread · 2026-05-07 · closed · 1 comment

feat(mcp): post-edit confirmation snippet in batch_edit response

Problem

After `redcon_batch_edit` lands, the agent typically issues a follow-up native `Read` to confirm the change worked - particularly for renames or signature changes where the surrounding code matters. That's an extra round trip that costs tokens and latency, and the information is already on the server side at write time.

WozCode's headline 25-55% saving comes from this exact lever: the search/edit response carries enough surrounding context that the model commits and moves on wit

Read the thread · 2026-05-07 · closed · 1 comment

feat(mcp): register all detected IDE targets, surface failures, never tłumi

Problem

Three coupled issues in `redcon init`'s MCP wiring:

`install_for_target` picks the first writable path for Cursor and stops. If a user has both `./.cursor/mcp.json` (project) and `~/.cursor/mcp.json` (global), only one ends up registered. They install Redcon, hit Cursor, and tools don't show up because the wrong scope was written.
`cmd_init` wraps `install_all()` in a bare `except Exception: pass`. If anything fails (permission denied, JSON corruption, missi

Read the thread · 2026-05-07 · closed · 1 comment

feat(doctor): loud diagnostics for tree-sitter / ast-grep / mcp extras

Problem

Two of Redcon's better features silently degrade when their optional extras aren't installed:

`redcon[symbols]` (tree-sitter): without it, the symbol-extraction compressor falls back to regex per file, with only a debug-level log. The user has no idea they're missing the better path.
`redcon[ast_grep]` (or the `ast-grep` binary): `redcon_structural_search` returns a 'backend=unavailable' marker but the user has to read the response to find out.

`redcon doctor` already

Read the thread · 2026-05-07 · closed · 1 comment

feat(ux): zero-config first run - redcon.toml is optional, not required

Problem

A fresh user expects the install-and-go workflow:

``` pip install redcon[mcp] redcon plan "my task" --repo . ```

The engine already supports this (`load_config` falls back to `default_config()` when `redcon.toml` is absent), but the surrounding UX disagrees:

`redcon doctor` flags missing `redcon.toml` as two warnings (`config` and `redcon_toml` both nag with "Run 'redcon init' to create one"). Sends the message that the file is required.
README's

Read the thread · 2026-05-07 · closed · 1 comment

feat(install): one-line uvx install (redcon-mcp script entrypoint)

Problem

Current install path requires multiple steps:

``` pip install "redcon[mcp]" redcon init

restart IDE

```

Even worse if the user wants the absolute minimum: `pip install redcon` followed by `redcon init --no-mcp` plus manual `.mcp.json` editing. Repomix, code2prompt, and most modern MCP servers ship as one-liners (`npx repomix`, `uvx mcp-foo`) - no install step, no venv, no init.

Proposed change

Add a dedicated `redcon-mcp` console script so users can run t

Read the thread · 2026-05-07 · closed · 1 comment

Most recent

feat(mcp): redcon_batch_edit - apply edits across multiple files in one call

Problem

Multi-file edits today take N round trips: agent calls native Edit once per file, each round trip pays output tokens for the agent to format the call and parse the response. For a "rename function across 6 files" task that is 6 sequential calls plus a verification Read per file = 12 round trips.

WozCode collapses this into one batched edit call, which is most of the speed win they advertise (5-10x faster on database/refactor tasks). MCP gives us the integration point for free: o

Read the thread · 2026-05-07 · closed · 1 comment

feat(mcp): redcon_search_and_read - batched rank+grep+read in one call

Problem

Current MCP flow for "find pattern X and show me the relevant code" requires 3+ tool calls from the agent:

redcon_rank (or redcon_plan) - get top-K ranked files for the task
redcon_search - grep pattern within those files, returns paths + line numbers
Native Read per matching file - to actually see the surrounding context

Each round trip costs output tokens (the agent reasons, picks the next call, formats arguments) and burns wall-clock. WozCode's recently-publishe

Read the thread · 2026-05-07 · closed · 1 comment

Tier 3: tree-sitter symbols, repo-map, structural search, semantic fallback

Goal

Heaviest research-driven additions. Each lands behind an optional install extra so the default redcon footprint stays unchanged.

Sub-tasks

A. Tree-sitter symbol extractor (`redcon[symbols]`)

New `redcon/symbols/tree_sitter.py`
`tree-sitter-language-pack` (~30 MB wheel, pip-installable, no system deps)
Exposes `extract_signatures(path, source, language)` returning class/function/method/type/interface signatures with line ranges
Covers Python, TypeScript, JavaSc

Read the thread · 2026-04-26 · closed · 1 comment

Tier 1 sprint: 6 token-reduction wins from research synthesis

Goal

Land six independent improvements identified by the 12-agent research synthesis. Each is low-cost, high-ROI, and doesn't touch existing architecture. Estimated combined token reduction: +30-50% over current on pytest-failure / git-diff / rg workloads, plus two new MCP integrations.

Items

Tokenizer-friendly format: drop leading 3-space indents in failure body lines (test compressors), make sure listing tree uses ASCII not Unicode box-drawing in our OWN emitted output, c

Read the thread · 2026-04-26 · closed · 1 comment

M1: redcon_run MCP tool with git diff/status/log compressors

Goal

Add command-output compression as a complement to existing file-context packing. First milestone is the pure-Python pipeline plus three highest-value compressors (git diff, git status, git log) and the MCP tool that exposes it to agents.

This is the foundation for the wider rtk-style integration tracked in the parent plan (M1-M10). Native Rust acceleration lands in M4; this milestone deliberately stays pure-Python to keep the existing setuptools build untouched.

Scope

New module

Read the thread · 2026-04-26 · closed · 1 comment

feat: implement POST /events ingestion endpoint with validation

Implement the HTTP endpoint that accepts telemetry events, validates them against the existing event schemas, and stores them in PostgreSQL.

Read the thread · 2026-03-15 · closed · 1 comment

Add Agent Integration wiki page

Document BudgetGuard integration, cost simulation, multi-turn agent loops, strict policy enforcement, middleware helpers, typed middleware API, workflow planning, delta mode, and adapter abstraction.

Read the thread · 2026-03-15 · closed · 1 comment

Add CLI Reference wiki page

Document all CLI commands: plan, plan-agent, pack, profile, read-profiler, report, diff, pr-audit, prepare-context, benchmark, heatmap, watch, and global flags.

Read the thread · 2026-03-15 · closed · 1 comment

The remaining reports are on the project's issue tracker.