agentleFS
nafgnafg/claude-converse/CLAUDE.md

claude-converse

CLAUDE.md0 starsChanged 7 months agoMITView on GitHub

Converse has been rebuilt around a shared TypeScript voice core with two harness adapters: The old Python split (listener.py, speak.py, render_status.py, shell + lockfile coordination) has been removed in favor of: Both harnesses load ~/.config/claude-converse/config.conf (under XDG_CONFIG_HOME when set). On first load Converse copies the committed reference config.example.conf there (mode 0600). The HOCON config file is the only source of settings — there are no environment-variable overrides. Restart Claude /converse or run Pi /reload after editing. Claude keeps the same…

  • In this repository2 other files it gives its agents.

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    if bind fails, voice mode is already active elsewhere

    line 55
  2. Very specific:

    if a leading [heard] ... [/heard] wrapper is well-formed, it is stripped before speech

    line 73
  3. Distinctive:

    if malformed or absent, text is spoken unchanged

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Converse internals

Rewrite overview

Converse has been rebuilt around a shared TypeScript voice core with two harness adapters:

  • Claude: HTTP daemon on localhost
  • Pi: in-process extension service

The old Python split (listener.py, speak.py, render_status.py, shell + lockfile coordination) has been removed in favor of:

  • one shared service implementation
  • one energy-based VAD state machine
  • harness-specific transport/adapters only where needed

Both harnesses load ~/.config/claude-converse/config.conf (under XDG_CONFIG_HOME when set). On first load Converse copies the committed reference config.example.conf there (mode 0600). The HOCON config file is the only source of settings — there are no environment-variable overrides. Restart Claude /converse or run Pi /reload after editing.

Claude transport

Claude keeps the same high-level harness affordances:

  • PreToolUse rewrite injects the authoritative Claude session id by replacing __CLAUDE_SESSION_ID__ in commands
  • Monitor consumes final transcripts from:
GET /v1/transcriptions/final?owner_id=<session>
  • Stop hook sends assistant text to:
POST /v1/speak
  • Statusline fetches already-rendered text from:
GET /v1/status?owner_id=<session>

The Claude daemon starts explicitly on /converse on and shuts down explicitly on /converse off.

Pi transport

Pi uses the same shared service object directly in-process.

There is no Pi-side daemon. The extension binds the same configured port only to preserve global exclusivity with Claude. It also registers wait_for_voice, which the model can call when a Transcribed: message is semantically unfinished; continuation wakes the tool immediately, while a bounded timeout prevents indefinite silence.

Exclusivity

CONVERSE_PORT is the exclusivity mechanism.

  • Claude daemon binds it because it serves HTTP
  • Pi binds the same port while voice mode is active
  • if bind fails, voice mode is already active elsewhere

Voice pipeline

  1. parecord streams raw PCM from the OS-selected default input. Override CONVERSE_RECORDER_COMMAND=arecord and CONVERSE_RECORDER_DEVICE=... only if needed.
  2. EnergyVad frames the stream and emits:
    • speech start
    • partial snapshot
    • final snapshot
    • barge-in
  3. final snapshots go to the independently configured STT provider: hosted OpenAI/Groq, local Whisper-compatible HTTP, or the persistent official Moonshine Voice sidecar
  4. assistant text goes to the independently configured TTS provider: OpenAI-compatible speech or the official Pocket TTS multipart API
  5. synthesized WAV is played via paplay to the OS-selected default output; Pocket TTS streams its chunked WAV response directly to the player

TTS cleanup

The service preserves the previous fail-open behavior:

  • if a leading [heard] ... [/heard] wrapper is well-formed, it is stripped before speech
  • if malformed or absent, text is spoken unchanged

So Claude may still use the wrapper, but the runtime never depends on it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.