CLI Reference

GROVE Grove workspace orchestrator and tool manager

Run ‘grove <tool>’ to delegate to installed tools, or use subcommands below.

USAGE grove [flags] grove [command]

COMMANDS build Build all Grove packages in parallel completion Generate the autocompletion script for the specified shell config Interactive configuration editor deps Manage dependencies across the Grove ecosystem dev Manage local development binaries ecosystem Manage Grove ecosystems install Install Grove tools from GitHub releases list List available Grove tools llm Unified interface for LLM providers release Manage releases for the Grove ecosystem repo Repository management commands run Run a command in all workspaces schema Manage and compose local JSON schemas self-update Update the grove CLI to the latest version setup Interactive setup wizard for Grove update Update Grove tools version Manage Grove tool versions

Flags: -c/—config, -h/—help, —json, -v/—verbose

AVAILABLE TOOLS BINARY DESCRIPTION REPO aglogs Agent transcript log parsin… agentlogs core Core libraries and debuggin… core cx LLM context management cx docgen LLM-powered, workspace-awar… docgen flow Job orchestration and workf… flow grove-anthropic Tools for using Anthropic/C… grove-anthropic grove-gemini Tools for Google’s Gemini API grove-gemini grove-nvim Neovim plugin for grove grove.nvim hooks Claude hooks integration fo… hooks nav Tmux session management for… nav nb Notebook and documentation … nb notify Notification system for Gro… notify skills Agent Skill Integrations skills tend Scenario-based testing tend

Command examples: grove install cx # Install a tool grove setup # Run setup wizard

Tool examples: grove cx stats # Show context statistics grove nb tui # Open notebook TUI grove flow status # Show flow plan status grove gmux sessionize # Create tmux session

Use “grove [command] —help” for more information.

GROVE BUILD Build all Grove packages in parallel

Builds Grove packages in parallel with a real-time status UI.

The build scope is context-aware based on your current directory:

• Ecosystem root: Builds all sub-projects within the ecosystem.
• Sub-project or Standalone project: Builds only the current project.

By default, all builds continue even if one fails. Use —fail-fast for CI environments where you want to stop immediately on the first failure.

This command replaces the root ‘make build’ for a faster and more informative build experience.

USAGE grove build [flags]

FLAGS -c, —config Path to grove.yml config file —dry-run Show what would be built without actually building —exclude Comma-separated glob patterns to exclude projects —fail-fast Stop all builds immediately when one fails (useful for CI) —filter Glob pattern to include only matching projects -h, —help help for build -i, —interactive Keep TUI open after builds complete for inspection -j, —jobs Number of parallel builds (default: 10) —json Output in JSON format -v, —verbose Stream raw build output instead of using the TUI

GROVE CONFIG Interactive configuration editor

Edit Grove configuration values interactively.

This command opens a TUI to edit the active configuration file. It prioritizes the project-level config if present, otherwise defaults to the global configuration.

Supports both YAML (with comment preservation) and TOML formats.

USAGE grove config [flags]

FLAGS -c, —config Path to grove.yml config file -h, —help help for config —json Output in JSON format -v, —verbose Enable verbose logging

GROVE DEPS Manage dependencies across the Grove ecosystem

The deps command provides tools for managing Go module dependencies across all Grove submodules.

USAGE grove deps [command]

COMMANDS bump Bump a dependency version across all submodules sync Update all Grove dependencies to their latest versions tree Display dependency tree visualization

Flags: -h/—help

Use “grove deps [command] —help” for more information.

GROVE DEPS BUMP Bump a dependency version across all submodules

Bump a Go module dependency across all Grove submodules.

This command finds all submodules that depend on the specified module and updates them to the specified version. If no version is specified or @latest is used, it will fetch the latest available version.

USAGE grove deps bump <module_path>[@version] [flags]

FLAGS —commit Create a git commit in each updated submodule -h, —help help for bump —push Push the commit to origin (implies —commit)

EXAMPLES grove deps bump github.com/grovetools/[email protected] grove deps bump github.com/grovetools/core@latest grove deps bump github.com/grovetools/core

GROVE DEPS SYNC Update all Grove dependencies to their latest versions

Synchronize all Grove dependencies across all submodules.

This command automatically discovers all Grove dependencies (github.com/grovetools/*) in each submodule and updates them to their latest versions. This is useful for keeping the entire ecosystem in sync after multiple tools have been released.

USAGE grove deps sync [flags]

FLAGS —commit Create a git commit in each updated submodule -h, —help help for sync —push Push the commit to origin (implies —commit)

EXAMPLES grove deps sync grove deps sync —commit grove deps sync —push

GROVE DEPS TREE Display dependency tree visualization

Display a tree visualization of dependencies in the Grove ecosystem.

Without arguments, shows the complete dependency graph for all repositories. With a repository name, shows dependencies for that specific repository.

USAGE grove deps tree [repo] [flags]

FLAGS —external Include external dependencies —filter Filter to specific repositories -h, —help help for tree —versions Show version information

EXAMPLES grove deps tree # Show complete dependency graph grove deps tree grove-meta # Show dependencies of grove-meta grove deps tree —versions # Include version information grove deps tree —external # Include external (non-Grove) dependencies

GROVE DEV Manage local development binaries

The ‘grove dev’ commands manage local development binaries built from source. This allows you to switch between different versions of Grove tools built from different git worktrees during development.

These commands are distinct from ‘grove version’ which manages official releases.

USAGE grove dev [command]

COMMANDS current Show currently active local development versions cwd Globally activate binaries from current directory link Register binaries from a local worktree list List registered local development versions list-bins List all binaries managed by local development links point Point current workspace to use specific binaries prune Remove registered versions whose binaries no longer exist secrets Manage GitHub repository secrets across all workspaces use Switch to a specific version of a binary workspace Display information about the current workspace context

Flags: -c/—config, -h/—help, —json, -v/—verbose

Use “grove dev [command] —help” for more information.

GROVE DEV CURRENT Show currently active local development versions

Displays the effective configuration for all Grove tools, showing whether each tool is using a development link or the released version.

This command shows the layered status where development links override released versions.

USAGE grove dev current [flags]

FLAGS -c, —config Path to grove.yml config file -h, —help help for current —json Output in JSON format -v, —verbose Enable verbose logging

EXAMPLES # Show current versions for all binaries grove dev current

# Show current version for a specific binary grove dev current flow

GROVE DEV CWD Globally activate binaries from current directory

Globally register and activate all binaries from the current working directory. This command combines ‘grove dev link’ and ‘grove dev use’ for all binaries found in the current directory, making them the global default.

This is the primary way to set your globally-managed development binaries to a specific version built from a local worktree.

USAGE grove dev cwd [flags]

FLAGS -c, —config Path to grove.yml config file -h, —help help for cwd —json Output in JSON format -v, —verbose Enable verbose logging

EXAMPLES # The binaries from your current worktree will now be the default # when you run ‘grove <tool>’ from anywhere on your system. cd ~/grove-ecosystem/.grove-worktrees/my-feature grove dev cwd

GROVE DEV LINK Register binaries from a local worktree

Register binaries from a Git worktree for local development. This command discovers binaries in the specified directory and makes them available for use with ‘grove dev use’.

USAGE grove dev link [flags]

FLAGS —as Custom alias for this version -c, —config Path to grove.yml config file -h, —help help for link —json Output in JSON format -v, —verbose Enable verbose logging

EXAMPLES # Link binaries from current directory grove dev link .

# Link with a custom alias grove dev link ../grove-flow —as feature-branch

GROVE DEV LIST List registered local development versions

Shows all registered local development versions for binaries. If a binary name is provided, shows only versions for that binary.

USAGE grove dev list [flags]

FLAGS -c, —config Path to grove.yml config file -h, —help help for list —json Output in JSON format -v, —verbose Enable verbose logging

EXAMPLES # List all binaries and their versions grove dev list

# List versions for a specific binary grove dev list flow

GROVE DEV POINT Point current workspace to use specific binaries

Configure the current workspace to use a specific binary from another location.

This is useful for testing development versions of Grove tools against your projects. For example, you can point your crud-app workspace to use a feature branch of the ‘flow’ tool while keeping everything else using global binaries.

Overrides are stored in .grove/overrides.json within the current workspace.

USAGE grove dev point [flags]

FLAGS -c, —config Path to grove.yml config file -h, —help help for point —json Output in JSON format —remove Remove the override for a binary -v, —verbose Enable verbose logging

EXAMPLES # Point to all binaries from a workspace (auto-discovers from grove.yml) cd ~/myproject grove dev point /path/to/grove-flow/.grove-worktrees/feature

# Point a specific binary to a workspace grove dev point flow /path/to/grove-flow/.grove-worktrees/feature

# Point to a specific binary file grove dev point flow /path/to/grove-flow/.grove-worktrees/feature/bin/flow

# List all configured overrides grove dev point

# Remove an override grove dev point —remove flow

GROVE DEV PRUNE Remove registered versions whose binaries no longer exist

Scans all registered local development links and removes those whose binary paths no longer exist on the filesystem. This helps clean up after deleted worktrees or moved directories.

If a pruned link was the active version, Grove will automatically fall back to the ‘main’ version or the active release version.

USAGE grove dev prune [flags]

FLAGS -c, —config Path to grove.yml config file -h, —help help for prune —json Output in JSON format -v, —verbose Enable verbose logging

EXAMPLES # Remove all broken links grove dev prune

GROVE DEV SECRETS Manage GitHub repository secrets across all workspaces

Set, update, or delete GitHub repository secrets for all discovered workspaces using the GitHub CLI

USAGE grove dev secrets [command]

COMMANDS delete Delete a secret from all workspace repositories list List secrets for all workspace repositories set Set a secret across all workspace repositories

Flags: -h/—help

Use “grove dev secrets [command] —help” for more information.

GROVE DEV SECRETS DELETE Delete a secret from all workspace repositories

Delete a GitHub repository secret from all discovered workspace repositories

USAGE grove dev secrets delete SECRET_NAME [flags]

FLAGS -e, —exclude Exclude workspaces matching pattern (can be specified multiple times) -h, —help help for delete -i, —include Only include workspaces matching pattern (can be specified multiple times)

GROVE DEV SECRETS LIST List secrets for all workspace repositories

List GitHub repository secrets for all discovered workspace repositories

USAGE grove dev secrets list [flags]

FLAGS -h, —help help for list

GROVE DEV SECRETS SET Set a secret across all workspace repositories

Set a GitHub repository secret across all discovered workspace repositories. If SECRET_VALUE is not provided, the secret will be read from stdin.

USAGE grove dev secrets set SECRET_NAME [SECRET_VALUE] [flags]

FLAGS -e, —exclude Exclude workspaces matching pattern (can be specified multiple times) -f, —file Read secret value from file -h, —help help for set -i, —include Only include workspaces matching pattern (can be specified multiple times)

GROVE DEV USE Switch to a specific version of a binary

Activates a specific locally-linked version of a Grove binary. This will update the symlink in ~/.local/share/grove/bin to point to the selected version.

With the —release flag, switches the binary back to the currently active released version.

USAGE grove dev use [flags]

FLAGS -c, —config Path to grove.yml config file -h, —help help for use —json Output in JSON format —release Switch back to the released version -v, —verbose Enable verbose logging

EXAMPLES # Use a specific version of flow grove dev use flow feature-branch

# Use the main version of cx grove dev use cx main

# Switch flow back to the released version grove dev use flow —release

GROVE DEV WORKSPACE Display information about the current workspace context

Provides information about the currently active Grove workspace. A workspace is detected by the presence of a ‘.grove/workspace’ file in a parent directory. To make Grove prioritize binaries from the current workspace, run: grove dev delegate workspace

USAGE grove dev workspace [flags]

FLAGS —check Exit with status 0 if in a workspace, 1 otherwise -c, —config Path to grove.yml config file -h, —help help for workspace —json Output in JSON format —path Print the workspace root path if found -v, —verbose Enable verbose logging

EXAMPLES # Show current workspace info grove dev workspace

# Check if in a workspace (for scripts) grove dev workspace —check

# Print the workspace root path grove dev workspace —path

GROVE ECOSYSTEM Manage Grove ecosystems

Manage Grove ecosystems (monorepos).

Commands: init Create a new Grove ecosystem import Import an existing repository into the ecosystem list List repositories in the ecosystem

USAGE grove ecosystem [command]

COMMANDS import Import an existing repository into the ecosystem init Create a new Grove ecosystem list List repositories in the ecosystem

Flags: -h/—help

EXAMPLES # Create a new ecosystem grove ecosystem init

# Import an existing repo as submodule grove ecosystem import ../my-existing-tool grove ecosystem import github.com/user/repo

# List repos in the ecosystem grove ecosystem list

Use “grove ecosystem [command] —help” for more information.

GROVE ECOSYSTEM IMPORT Import an existing repository into the ecosystem

Import an existing repository into the ecosystem as a git submodule.

The repo can be:

• A local path (../my-repo or /path/to/repo)
• A GitHub shorthand (user/repo)
• A full Git URL (https://github.com/user/repo.git)

USAGE grove ecosystem import <repo> [flags]

FLAGS -h, —help help for import —path Custom path for the submodule

EXAMPLES # Import from local path grove ecosystem import ../my-existing-tool

# Import from GitHub grove ecosystem import grovetools/grove-context

# Import with custom directory name grove ecosystem import grovetools/grove-context —path vendor/context

GROVE ECOSYSTEM INIT Create a new Grove ecosystem

Create a new Grove ecosystem (monorepo).

By default, creates a minimal ecosystem with grove.yml and README. Use —go to add Go workspace support (go.work, Makefile).

USAGE grove ecosystem init [name] [flags]

FLAGS —go Add Go workspace support (go.work, Makefile) -h, —help help for init

EXAMPLES # Create minimal ecosystem in current directory grove ecosystem init

# Create ecosystem with a name grove ecosystem init my-ecosystem

# Create Go-based ecosystem grove ecosystem init —go grove ecosystem init my-ecosystem —go

GROVE ECOSYSTEM LIST List repositories in the ecosystem

List all repositories in the current Grove ecosystem.

Shows submodules and local directories that contain grove.yml files.

USAGE grove ecosystem list [flags]

FLAGS -h, —help help for list

EXAMPLES grove ecosystem list

GROVE INSTALL Install Grove tools from GitHub releases

Install one or more Grove tools from GitHub releases.

You can specify a specific version using the @ syntax, or install the latest version. Use ‘all’ to install all available tools, or ‘all@nightly’ to install latest RC builds of all tools.

USAGE grove install [tool[@version]…] [flags]

FLAGS -h, —help help for install —use-gh Use gh CLI for downloading (supports private repos)

EXAMPLES grove install cx # Install latest stable version of cx grove install [email protected] # Install specific version of cx grove install cx@nightly # Install latest pre-release (RC/nightly) of cx grove install cx@source # Build and install cx from main branch grove install cx nb flow # Install multiple tools grove install all # Install all available tools grove install all@nightly # Install latest RC builds of all tools grove install —use-gh cx # Use gh CLI for private repo access

GROVE LIST List available Grove tools

Display all available Grove tools and their installation status

USAGE grove list [flags]

FLAGS —check-updates Check for latest releases from GitHub (default: true) -h, —help help for list

GROVE LLM Unified interface for LLM providers

The ‘grove llm’ command provides a single, consistent entry point for all LLM interactions, regardless of the underlying provider (OpenAI, Gemini, etc.).

It intelligently delegates to the appropriate provider-specific tool based on the model name.

USAGE grove llm [command]

COMMANDS request Make a request to an LLM provider

Flags: -c/—config, -h/—help, —json, -v/—verbose

Use “grove llm [command] —help” for more information.

GROVE LLM REQUEST Make a request to an LLM provider

Acts as a facade, delegating to the appropriate tool (grove-gemini, grove-openai) based on the model.

Model determination precedence:

1. —model flag
2. ‘llm.default_model’ in grove.yml

USAGE grove llm request [prompt…] [flags]

FLAGS —cache-ttl Cache TTL for Gemini (e.g., 1h, 30m) —context Additional context files or directories to include -f, —file Read prompt from file -h, —help help for request —max-output-tokens Maximum tokens in response (-1 to use default) (default: -1) -m, —model LLM model to use (e.g., gpt-4o-mini, gemini-2.0-flash) —no-cache Disable context caching for Gemini -o, —output Write response to file instead of stdout -p, —prompt Prompt text —recache Force recreation of the Gemini cache —regenerate Regenerate context before request —stream Stream the response (if supported by provider) —temperature Temperature for randomness (-1 to use default) (default: -1) —top-k Top-k sampling (-1 to use default) (default: -1) —top-p Top-p nucleus sampling (-1 to use default) (default: -1) —use-cache Specify a Gemini cache name to use -w, —workdir Working directory (defaults to current) -y, —yes Skip confirmation prompts

GROVE RELEASE Manage releases for the Grove ecosystem

Manage releases for the Grove ecosystem using a stateful, multi-step workflow.

The release process is divided into distinct commands: plan - Generate a release plan analyzing all repositories for changes tui - Review and approve the release plan interactively (or use ‘review’) apply - Execute the approved release plan clear-plan - Clear the current release plan and start over undo-tag - Remove tags locally and optionally from remote rollback - Rollback commits in repositories from the release plan

Typical workflow:

1. grove release plan —rc # Generate RC release plan (auto-checks out rc-nightly)
2. grove release tui # Review and approve
3. grove release apply # Execute the release

Recovery commands: grove release undo-tag —from-plan —remote # Remove all tags from failed release grove release rollback —hard # Reset repositories to previous state grove release clear-plan # Start over with a new plan

USAGE grove release [flags] grove release [command]

COMMANDS apply Execute a previously generated release plan clear-plan Clear the current release plan plan Generate a release plan for the ecosystem review Review and modify the release plan (alias for ‘tui’) rollback Rollback commits in repositories from the release plan tui Launch interactive TUI for release planning undo-tag Remove tags locally and optionally from remote

Flags: -h/—help

EXAMPLES grove release plan —rc # Plan a Release Candidate (no docs) grove release plan —repos grove-core —with-deps # Specific repos with dependencies grove release tui # Review and modify the plan grove release apply —dry-run # Preview what would be done

Use “grove release [command] —help” for more information.

GROVE RELEASE APPLY Execute a previously generated release plan

Execute a release plan that was previously generated with ‘grove release plan’ and reviewed with ‘grove release tui’.

This command will:

1. Load the plan from the Grove state directory
2. Execute the release for all approved repositories
3. Create tags and push changes if configured
4. Clear the plan upon successful completion

Use —dry-run to preview what would be done without making changes.

USAGE grove release apply [flags]

FLAGS —dry-run Print commands without executing them -h, —help help for apply —push Push changes to remote repositories (default: true) (default: true) —resume Only process repos that haven’t completed successfully —skip-ci Skip CI waits after changelog updates (still waits for release workflows) —skip-parent Skip parent repository updates

GROVE RELEASE PLAN Generate a release plan for the ecosystem

Generate a release plan that analyzes all repositories for changes and suggests appropriate version bumps.

The plan is saved to the Grove state directory and can be:

• Reviewed and modified with ‘grove release tui’
• Applied with ‘grove release apply’
• Cleared with ‘grove release clear-plan’

Use —rc flag to create a Release Candidate plan that skips changelog and documentation updates.

USAGE grove release plan [flags]

FLAGS -h, —help help for plan —llm-changelog Generate changelog using an LLM —major Repositories to receive major version bump —minor Repositories to receive minor version bump —patch Repositories to receive patch version bump —rc Generate a Release Candidate plan (skip docs/changelogs) —repos Only release specified repositories —version Set explicit version for repositories (format: repo=v1.2.3) —version-all Set all repositories to this version (e.g., v0.6.0) —with-deps Include all dependencies of specified repositories

GROVE RELEASE REVIEW Review and modify the release plan (alias for 'tui')

Launch the interactive TUI to review and modify the release plan.

This is an alias for ‘grove release tui’.

USAGE grove release review [flags]

FLAGS -h, —help help for review

GROVE RELEASE ROLLBACK Rollback commits in repositories from the release plan

Rollback recent commits in repositories that are part of the release plan.

This command helps recover from failed releases by resetting repositories to a previous state. It reads the release plan to know which repositories to operate on.

USAGE grove release rollback [flags]

FLAGS —commits Number of commits to roll back (default: 1) —force Allow force push if needed —hard Shortcut for —mode=hard -h, —help help for rollback —mixed Shortcut for —mode=mixed —mode Reset mode: (default: mixed) • hard • soft • mixed —push Push the rollback to origin —soft Shortcut for —mode=soft

EXAMPLES grove release rollback # Rollback 1 commit (mixed mode) grove release rollback —commits 2 # Rollback 2 commits grove release rollback —hard # Hard reset (loses changes) grove release rollback —soft —push # Soft reset and push grove release rollback —push —force # Force push after rollback

GROVE RELEASE TUI Launch interactive TUI for release planning

Launch an interactive Terminal User Interface for release planning.

This command provides an interactive way to:

• Review repositories with changes
• See LLM-suggested version bumps with justifications
• Manually adjust version bump types (major/minor/patch)
• Preview and approve changelogs
• Execute the release once all repositories are approved

The release plan is persisted in the Grove state directory and can be resumed if interrupted.

USAGE grove release tui [flags]

FLAGS —fresh Clear any existing release plan and start fresh -h, —help help for tui

GROVE REPO Repository management commands

Manage Grove repositories.

USAGE grove repo [command]

COMMANDS add Create a new local Grove repository

Flags: -h/—help

EXAMPLES # Create a new local repository grove repo add my-tool —description “My new tool”

# Create and add to an existing ecosystem grove repo add my-tool —ecosystem

# Use a different template grove repo add my-tool —template maturin

Use “grove repo [command] —help” for more information.

GROVE REPO ADD Create a new local Grove repository

Create a new local Grove repository.

By default, creates a minimal repository with just a README and grove.yml. Use —template to start from a project template instead.

USAGE grove repo add <repo-name> [flags]

FLAGS -a, —alias Binary alias (defaults to repo name) -d, —description Repository description —dry-run Preview operations without executing —ecosystem Add repository to an existing Grove ecosystem as a submodule -h, —help help for add —template Template: (e.g., owner/repo) • go • maturin • react-ts • GitHub repo

EXAMPLES # Create a minimal repository (default) grove repo add my-tool

# Create with a description grove repo add my-tool —description “My new tool”

# Create from a Go CLI template grove repo add my-tool —template go

# Create from other templates grove repo add myrust —template maturin grove repo add myapp —template react-ts

# Add to an existing ecosystem grove repo add my-tool —ecosystem

GROVE RUN Run a command in all workspaces

Execute a command across all discovered workspaces.

The command will be executed in each workspace directory with the workspace as the current working directory.

Use — to separate grove run flags from the command and its arguments.

USAGE grove run [flags] — <command> [args…]

FLAGS —exclude Comma-separated list of workspace patterns to exclude (glob patterns) -f, —filter Filter workspaces by glob pattern -h, —help help for run

EXAMPLES # Run grove context stats in all workspaces grove run cx stats

# Run git status in all workspaces grove run git status

# Filter workspaces by pattern grove run —filter “grove-*” — npm test

# Exclude specific workspaces grove run —exclude “grove-core,grove-flow” — npm test

# Run command with flags (using — separator) grove run — docgen generate —output docs/

# Run with JSON output aggregation grove run —json — cx stats

GROVE SCHEMA Manage and compose local JSON schemas

Tools for working with Grove JSON schemas.

The schema command provides utilities for generating unified schemas from ecosystem workspaces for local development.

USAGE grove schema [command]

COMMANDS generate Generate a unified local schema for the current ecosystem

Flags: -c/—config, -h/—help, —json, -v/—verbose

Use “grove schema [command] —help” for more information.

GROVE SCHEMA GENERATE Generate a unified local schema for the current ecosystem

Scans all workspaces in the current ecosystem for locally generated schema files and composes them into a single ‘grove.schema.json’ at the ecosystem root.

This enables IDE autocompletion and validation during local development.

The command will:

1. Find the ecosystem root (directory containing workspaces in grove.yml)
2. Locate grove-core’s base schema
3. Discover all workspace projects and look for their schema files
4. Compose them into a unified schema at .grove/grove.schema.json

Example usage: grove schema generate

USAGE grove schema generate [flags]

FLAGS -h, —help help for generate

GROVE SETUP Interactive setup wizard for Grove

Interactive setup wizard for configuring Grove.

The setup wizard guides you through configuring:

• Ecosystem directory: Where your Grove projects live
• Notebook directory: For notes and development plans
• Gemini API key: For LLM-powered features
• tmux popup bindings: Quick access to Grove tools
• Neovim plugin: IDE integration

USAGE grove setup [flags] grove setup [command]

COMMANDS git-hooks Manage Git hooks for Grove repositories starship Manage Starship prompt integration

Flags: -c/—config, —defaults, —dry-run, -h/—help, —json, —only, -v/—verbose

EXAMPLES # Run the interactive setup wizard grove setup

# Run with defaults (non-interactive) grove setup —defaults

# Run specific steps only grove setup —only ecosystem,notebook

# Preview changes without making them grove setup —dry-run

Use “grove setup [command] —help” for more information.

GROVE SETUP STARSHIP Manage Starship prompt integration

Provides commands to integrate Grove status with the Starship prompt.

USAGE grove setup starship [command]

COMMANDS install Install the Grove module to your starship.toml

Flags: -h/—help

Use “grove setup starship [command] —help” for more information.

GROVE SETUP STARSHIP INSTALL Install the Grove module to your starship.toml

Appends a custom module to your starship.toml configuration file to display Grove status in your shell prompt. It will also attempt to add the module to your main prompt format.

USAGE grove setup starship install [flags]

FLAGS -h, —help help for install

GROVE UPDATE Update Grove tools

Update one or more Grove tools by reinstalling them. If no tools are specified, updates grove itself.

USAGE grove update [tools…] [flags]

FLAGS -h, —help help for update —use-gh Use gh CLI for downloading (supports private repos)

EXAMPLES grove update # Update grove itself grove update context version # Update specific tools grove update cx nb grove update —use-gh cx # Use gh CLI for private repos

GROVE VERSION Manage Grove tool versions

List, switch between, and uninstall different versions of Grove tools

USAGE grove version [flags] grove version [command]

COMMANDS list List installed versions uninstall Uninstall a specific version use Switch a tool to a specific version

Flags: -h/—help, —json

Use “grove version [command] —help” for more information.

GROVE VERSION LIST List installed versions

Display all installed versions of Grove tools

USAGE grove version list [flags]

FLAGS -h, —help help for list

GROVE VERSION UNINSTALL Uninstall a specific version

Remove a specific version of Grove tools.

If the version being uninstalled is currently active, the active version will be cleared.

USAGE grove version uninstall <version> [flags]

FLAGS -h, —help help for uninstall

EXAMPLES grove version uninstall v0.1.0

GROVE VERSION USE Switch a tool to a specific version

Switch a specific tool to an installed version.

This command updates the symlink in ~/.local/share/grove/bin for the specified tool.

USAGE grove version use <tool@version> [flags]

FLAGS -h, —help help for use

EXAMPLES grove version use [email protected] grove version use [email protected] grove version use [email protected]