Skip to content

docs: add --resume flag documentation #200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kibarik wants to merge 2 commits into
base: main
Choose a base branch
from
+18 −1
Open

docs: add --resume flag documentation #200

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a4f35c6
docs(readme): add resume flag documentation
kibarik May 16, 2026
fff14d2
docs(cli): improve --resume flag help text
kibarik May 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,18 @@ repowise init . # scans for git repos, indexes each, runs cross-repo analys
repowise serve # workspace dashboard + per-repo pages
```

### Resuming an interrupted index

If `repowise init` is interrupted (timeout, crash, Ctrl+C), you can resume from where it stopped:

```bash
repowise init . --resume
```

The `--resume` flag checks the vector store for already-generated pages and continues generation for only the missing pages. Pro tip: Always use `--resume` when re-running init on a large repo — it's a safe no-op if the repo is fully indexed.

**How it works:** Pages are written to LanceDB incrementally during generation, but the SQL `generation_jobs` row only finalizes at the end. A hard interrupt can leave LanceDB ahead of SQL — `--resume` is the supported recovery path, and `repowise doctor` will flag any drift.

That's it. `repowise init` automatically registers the MCP server, installs PreToolUse/PostToolUse hooks in `~/.claude/settings.json`, generates `.mcp.json` at the project root, and offers to install a post-commit git hook that keeps everything in sync after every commit. See [Auto-Sync](docs/AUTO_SYNC.md) for all sync methods (hooks, file watcher, GitHub/GitLab webhooks, polling).

To manually add the MCP server to another editor:
Expand Down
7 changes: 6 additions & 1 deletion packages/cli/src/repowise/cli/commands/init_cmd.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -854,7 +854,12 @@ def _workspace_init(
"--dry-run", is_flag=True, default=False, help="Show generation plan without running."
)
@click.option("--yes", "-y", is_flag=True, default=False, help="Skip cost confirmation prompt.")
@click.option("--resume", is_flag=True, default=False, help="Resume from last checkpoint.")
@click.option(
"--resume",
is_flag=True,
default=False,
help="Skip pages already generated in the vector store and continue from where a previous run stopped. Safe no-op on a fully indexed repo."
)
@click.option(
"--force", is_flag=True, default=False, help="Regenerate all pages, ignoring existing."
)
Expand Down