Show HN: Transform your codebase into a single Markdown doc for feeding into AI

Original Article ↗ Hacker News Discussion ↗

Tool Landscape & Comparisons

  • Many commenters note there are already numerous tools that flatten repos for LLMs (Repomix, llmcat, files-to-prompt, code2prompt, gitingest, repo2txt, etc.), plus many homegrown bash/Python scripts.
  • CodeWeaver is described as:
    • Compiled Go binary with no runtime deps.
    • Regex-based exclusion list rather than .gitignore, which some see as more flexible and others as more tedious.
    • Still relatively minimal compared to more “full-fledged” solutions.
  • Several people share similar tools they built (Go, Rust, CLI, VS Code extensions), often adding:
    • .gitignore or custom ignore/whitelist files.
    • Binary and large-file filtering.
    • Per-feature or per-folder bundles rather than a single giant file.

Use Cases & Workflows

  • Common workflows:
    • Generate README/documentation from code.
    • Copy curated subsets of files for ChatGPT / Claude / Gemini via clipboard.
    • Use web-only “big brain” models like o1 Pro or Deep Research by pasting text.
  • Some see this as infrastructure for other tools (e.g., agents, RAG systems), not an end-user interface.

Context Limits, Quality, and Strategy

  • Strong skepticism about dumping entire large codebases:
    • Quickly exceeds context limits even with 1–2M token windows.
    • Attention dilution and token waste on irrelevant parts.
    • Better results reported when feeding tightly targeted context rather than relying on opaque indexing.
  • Others report moderate success on large bundles for:
    • Queries like “where is X done?”, “where is this function called?”, listing TODOs.
    • Simple-to-moderate refactors, especially in smaller Python projects.
  • Some would prefer higher-level summaries (APIs, method signatures, dependency graphs) instead of raw full code.

IDE-Integrated & Agentic Alternatives

  • Many argue that IDE agents (Cursor, Copilot, Windsurf, Aider, cline, etc.) that index the repo and fetch relevant files are a better long-term pattern.
  • Mixed experiences:
    • Some report excellent navigation/refactoring on small projects.
    • Others complain about incomplete edits and weak refactoring, especially in large monorepos or certain languages.
  • There’s demand for tools that:
    • Navigate and modify code interactively (true “pair programming”).
    • Give precise control over which files are in context.

Naming & Legal Concerns

  • Multiple commenters point out potential confusion and trademark risk with the “CodeWeaver” name due to an existing, similarly named software company.
  • Some think it’s overblown; others expect a cease-and-desist and suggest alternative names.