pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for argot

Pod holds 16 of 16 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 argot.

Most discussed

RD-01 — Replace README opening and audit-first quick start

Execution assignment: PR-14 · Batch H — Public validation and README Constitution: Agent execution rules

  • Goal: Make the first screen one product job, one current boundary and one executable audit path.
  • Owner: README
  • Why: D1/D2/D10/D11 reject the current voice/harness opening and feature-first flow.
  • Scope: Logo/title/subtitle/badges, opening paragraphs, install and qui

Read the thread · 2026-07-22 · closed · 5 comments

DOC-10 — Consolidate suppression workflow

Execution assignment: PR-11 · Batch F — Canonical reference documentation Constitution: Agent execution rules

  • Goal: Give one inspect → act/mute with reason → commit → review/prune path.
  • Owner: Documentation reference
  • Why: Suppression power is spread across long pages and must retain human-last-word safeguards.
  • Scope: Inline/path/mute/local config/locked behavior and `

Read the thread · 2026-07-22 · closed · 4 comments

PL-06 — Add plugin package contract smoke

Execution assignment: PR-08 · Batch D — Shipped integrations and proof Constitution: Agent execution rules

  • Goal: Validate six skills, MCP startup, hook paths, versions and duplicate wiring.
  • Owner: Integration packaging
  • Why: The current bundle has five/six documentation drift and no package-level contract test.
  • Scope: Plugin/marketplace manifests, skills paths/count, M

Read the thread · 2026-07-22 · closed · 4 comments

DR-05 — Classify secondary JSON outputs

Execution assignment: no-source-pr · Batch B — Stable contracts and claim data Constitution: Agent execution rules

  • Goal: Decide which status/list/inspect/rules/conventions/suggest/voice-diff JSON outputs are public contracts.
  • Owner: Decision owner
  • Why: Calling ad hoc output stable creates accidental API commitments.
  • Scope: Classify each output as versioned public, bes

Read the thread · 2026-07-22 · closed · 4 comments

DOC-01 — Implement target docs navigation and route compatibility

Execution assignment: PR-10 · Batch E — Canonical journey documentation Constitution: Agent execution rules

  • Goal: Create Start, Use, Configure, Understand and Help groups with stable routes.
  • Owner: Documentation journeys
  • Why: Current monoliths obscure the audit-to-habit journey.
  • Scope: Frontmatter/order/sidebar, new route placeholders and redirects/compatibility pages

Read the thread · 2026-07-22 · closed · 3 comments

AU-04 — Add audit contract regression fixtures

Execution assignment: PR-05 · Batch C — Activation and retention evidence Constitution: Agent execution rules

  • Goal: Lock cross-renderer boundaries and next actions after the rewrite.
  • Owner: Rust audit activation
  • Why: Terminal, Markdown, HTML, JSON and caption currently drift independently.
  • Scope: Findings, empty, marker attribution, transient-added-then-removed and CT

Read the thread · 2026-07-22 · closed · 3 comments

DOC-07 — Rewrite Other agents and MCP guide

Execution assignment: PR-10 · Batch E — Canonical journey documentation Constitution: Agent execution rules

  • Goal: Explain generic skills/MCP compatibility without implying tested lifecycle automation.
  • Owner: Documentation journeys
  • Why: “70+” and passive MCP currently read too broadly.
  • Scope: agents.md non-Claude content, MCP setup/coverage, named host status from IN

Read the thread · 2026-07-22 · closed · 2 comments

DOC-06 — Consolidate Claude Code guide

Execution assignment: PR-10 · Batch E — Canonical journey documentation Constitution: Agent execution rules

  • Goal: Give one tested path for binary, plugin, skills, MCP, pre-write and optional shipped end-of-turn behavior.
  • Owner: Documentation journeys
  • Why: Existing plugin.md and agent prose overlap and blur automatic coverage.
  • Scope: plugin.md becomes canonical Cla

Read the thread · 2026-07-22 · closed · 2 comments

Most recent

MC-02 — Add MCP protocol wording snapshots

Execution assignment: PR-03 · Batch B — Stable contracts and claim data Constitution: Agent execution rules

  • Goal: Lock tool names, capability boundaries and startup fit status.
  • Owner: Rust check contracts
  • Why: MCP copy is consumed by agents and easy to overstate silently.
  • Scope: Initialize/list-tools/tool-description snapshots and fitted/unfitted startup text.
  • **Fil

Read the thread · 2026-07-22 · closed · 2 comments

MC-01 — Correct MCP tool capability descriptions

Execution assignment: PR-03 · Batch B — Stable contracts and claim data Constitution: Agent execution rules

  • Goal: State passive invocation and base-hunk coverage in tool/startup text.
  • Owner: Rust check contracts
  • Why: MCP check/explain are not the full production changeset composition.
  • Scope: Five tool descriptions, startup instructions and full-CLI pointer; keep tool

Read the thread · 2026-07-22 · closed · 2 comments

PL-04 — Package lifecycle manifest and opt-out (gated)

Execution assignment: PR-08 · Batch D — Shipped integrations and proof Constitution: Agent execution rules

  • Goal: Wire the approved lifecycle into the Claude plugin with an explicit opt-out.
  • Owner: Integration packaging
  • Why: Product behavior must be inspectable and reversible by the user.
  • Scope: hooks/hooks.json, plugin metadata/config and lifecycle-specific document

Read the thread · 2026-07-22 · closed · 2 comments

EV-01 — Inventory released integration behavior

Execution assignment: PR-02 · Batch A — Baseline truth Constitution: Agent execution rules

  • Goal: Produce the tested capability matrix that distinguishes automatic, passive, invoked and user-wired surfaces.
  • Owner: Evidence and claims
  • Why: P0-1 and D8 require knowing which lifecycle is genuinely reachable before implementation or claims.
  • Scope: Claude plugin/pre-write h

Read the thread · 2026-07-22 · closed · 2 comments

Generate STYLE.md from learned voice (onboarding companion)

Background

argot already learns the repo's voice. That data is currently used reactively (score new hunks against it). It's also useful proactively as documentation:

  • For new human contributors: "here's how this codebase tends to write" — a generated style guide grounded in the repo's actual practice, not aspirational rules
  • For LLM coding agents: a system-prompt-friendly summary of the repo's voice (ties into the MCP server ticket — same data, human-readable form)
  • **For PR-au

Read the thread · 2026-05-04 · closed · 0 comments

Calibration freshness: warn when model is stale, optional auto-refit

Background

argot's model rots silently. After ~1000 commits or a meaningful chunk of refactoring since the last fit, the threshold and corpus are increasingly out of date — but the user has no signal that the numbers they're seeing are stale.

This is a quiet correctness gap: argot looks like it's still working, but the voice it learned isn't current.

Goal

Surface staleness clearly, give users a frictionless path to address it.

What it does

  • On every check, compute a "model ag

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

MCP server for LLM coding agents (with preemptive voice-context queries)

Background

LLM coding agents (Claude Code, Cursor, Aider, etc.) generate code that frequently sits just off the repo's voice — calls a slightly-wrong helper, picks an unfamiliar import alias, structures a function in the framework's default style instead of the local style. This is exactly the gap argot was built for, but today an agent has to shell out to argot check and parse text output.

There's a sharper opportunity hiding here: argot doesn't have to be a post-hoc linter for LLMs.

Read the thread · 2026-05-04 · closed · 0 comments

Set up proper user-facing documentation site

Background

User-facing docs today are concentrated in the README (long, increasingly the only entry point) plus scattered material in docs/research/ (era-by-era ADRs) and docs/agents/ (internal agent guidance). There's no dedicated docs site, no structured reference for the CLI / config / scorer, no how-to guides, and no per-language pages.

As the supported-languages list grows (#42–#50) and surfaces like introspection (#51) and per-hunk evidence (#40) land, the README is going to buckl

Read the thread · 2026-05-04 · closed · 0 comments

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