Sandworm 🪱

A simple tool that concatenates a bunch of files (think a project folder) into a single document, perfect for feeding to large language models and "talk-to-your-codebase" workflows.

It integrates with Claude Projects and automates the filesync process, which allows you to quickly iterate on your code with the help of Claude.

Quick start

brew tap holonoms/tap
brew install sandworm
brew sandworm --help

What does it do?

Sandworm reads your project directory, combines all text files into a single text file, and uploads this file to a configured Claude project. This Allows you to chat with Claude having the most recent version of your entire project context.

What is good for?

The typical workflow is:

1. Make changes to your project
2. Run sandworm to update your Claude project
3. Ask Claude to iterate on the new code (e.g. build new feature, refactor code)
4. Apply Claude's suggested changes & run sandworm again

Rinse and repeat. Used in this fashion, sandworm allows you to very quickly add new features to your software projects by leveraging Claude (or a similar LLM).

How does it work?

Sandworm will initially look for a .sandwormignore file, falling back to a .gitignore file if not found. This ignore file (which follows .gitignore inclusion/exclusion patterns) is how sandworm determines which files to combine into the output file.

It then creates a project file that consists of a file & folder tree at the top, followed by individual file's contents.

The first time you run sandworm push (or just sandworm), you'll be prompted to configure the Claude Project you want to sync with. Once that's done, subsequent runs of sandworm will take care of syncing the newly generated file with the Project's file. Every new Project Chat with Claude will include your whole project as context.

Advanced topics

Usage

Project file concatenator

Usage:
  sandworm [directory] [flags]
  sandworm [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  config      Manage project configuration
  generate    Generate concatenated file only
  help        Help about any command
  purge       Remove all files from Claude project
  push        Generate and push to Claude
  setup       Configure Claude project

Flags:
  -h, --help                 help for sandworm
      --ignore string        Ignore file (default: .gitignore)
  -k, --keep                 Keep the generated file after pushing
  -L, --follow-symlinks      Follow symbolic links when traversing directories
  -n, --line-numbers         Show line numbers in output (can also be set via config)
  -o, --output string        Output file
  -v, --version              version for sandworm

Use "sandworm [command] --help" for more information about a command.

Examples

Basic usage with default options:

# Use current directory as root folder
sandworm

Specify custom output file:

sandworm src/ -o context.txt

Use custom ignore file:

sandworm src/ --ignore custom-ignore.txt

Keep the uploaded file for inspection:

sandworm push -k

Follow symbolic links when traversing directories:

sandworm -L

Show line numbers in output:

sandworm -n

Configure project to always follow symbolic links:

sandworm config set processor.follow_symlinks true

Generate only, don't push to Claude Project:

sandworm generate

Configuration

Sandworm maintains configuration in two places:

• A global configuration file at ~/.config/sandworm/config.json
• A local configuration file at the root of your project, .sandworm

The first is used for global configuration, like your Claude session key. The latter is project-specific, and stores your Claude organization ID, project ID, the document ID for the file that holds your condensed project, and other project-specific settings.

Project Configuration Options

• processor.follow_symlinks: Set to true to always follow symbolic links when traversing directories

# Enable following symlinks for this project
sandworm config set processor.follow_symlinks true

# Disable following symlinks for this project  
sandworm config set processor.follow_symlinks false

# Check current setting
sandworm config get processor.follow_symlinks

# List all available configuration options
sandworm config list

Output Format

The generated file will have the structure:

PROJECT STRUCTURE:
================

/
├── components
│   ├── Button.tsx
│   └── Card.tsx
└── pages
    └── index.tsx

FILE CONTENTS:
=============

================================================================================
FILE: components/Button.tsx
================================================================================
[file contents here]

================================================================================
FILE: components/Card.tsx
================================================================================
[file contents here]

...

Development

We recommend installing both mise (or an equivalent version manager) and just for a smooth development experience. The linting command also requires golangci-lint to be installed, although that one runs as part of our CI on Github.

# Setup tooling
mise install (or something else that supports .tool-versions)

# Run project from sources
just run --help

# Build binary & run it
just build && bin/sandworm

# Run all checks
just lint

# Run the test suite
just test

# Other tasks
just --list

Cutting a new release

New releases are produced with goreleaser. To create a new release, simply push a tag in the format vX.Y.Z. A new release will be automatically created and uploaded to GitHub.

git tag -a v0.42.0 -m "Release v0.42.0"
git push origin v0.42.0