The Grepr command-line tool (@grepr/cli) and agent plugins that let Claude Code and Codex drive it for you.
- Just the CLI — jump to CLI section
- CLI + Claude Code skills — jump to Claude Code plugin section
- CLI + Codex skills — jump to Codex plugin section
- Node.js 20.0.0 or higher
npm install -g @grepr/cliAlternatives:
# Run without installing
npx @grepr/cli --help
# Or with yarn
yarn global add @grepr/cli# Save your organization configuration
grepr --org-name your-org-name config:save myconfig --default
# Query your data
grepr --conf myconfig query --dataset-name "production-logs" --query "level:ERROR"# Create a job from a definition file
grepr --conf myconfig job:create my-job.jsonThe CLI uses OAuth 2.0 with browser-based login. On the first command that requires access, your browser opens to complete the flow. Tokens are cached locally; subsequent commands don't prompt.
- Table — human-readable (default)
- CSV — for data analysis and spreadsheets
- JSON — machine-readable (pretty, raw, or compact)
Full command reference and advanced usage: docs.grepr.ai/cli
Preview: these skills are in early access. Expect rough edges and please file issues.
Skills for AI coding agents that let them manage your Grepr pipelines, datasets, integrations, and queries through the Grepr CLI — no context-switching to docs, no remembering subcommand syntax.
- Grepr CLI installed and configured (see CLI section above)
Try these prompts after installing the plugin for your agent:
List my running Grepr pipelines.
Build a grok rule that parses NGINX access logs from my
web-apiservice.
Debug why pipeline
<id>isn't producing output.
Query the last hour of error logs from the
production-logsdataset.
The agent will pick the right skill, run the CLI, and walk you through the result.
| Category | Skill | What it does |
|---|---|---|
| Router | cli | Dispatches to the right specialized skill based on intent |
| Commands | job-commands | List, view, create, update, delete jobs/pipelines |
| Commands | dataset-commands | Manage data lake datasets |
| Commands | integration-commands | View vendor and storage integrations |
| Commands | docs-commands | Semantic search over Grepr documentation |
| Queries | query-logs | Query data from datasets with filters and time ranges |
| Workflows | build-pipeline | End-to-end pipeline build, from requirements to production |
| Workflows | build-grok | Iterative grok pattern authoring and testing |
| Workflows | debug-pipeline | Troubleshoot pipelines that aren't producing expected output |
| Knowledge | grepr-model | Core Grepr concepts (events, jobs, graphs) — no docs lookup needed |
| Knowledge | job-graph-patterns | Common job graph patterns with examples |
| Knowledge | operations-reference | Reference for available Grepr sources, transforms, and sinks |
You can ask for Grepr work in natural language, or reference a skill by name when you want a specific workflow. Claude Code also lists skills by short name (e.g., /build-grok) with a (grepr) annotation in autocomplete; fully-qualified names such as /grepr:build-grok work when disambiguation is needed.
- Claude Code — the CLI, IDE extension, or desktop app
- Grepr CLI installed and configured (see CLI section above)
In Claude Code:
/plugin marketplace add grepr/cli
/plugin install grepr@grepr-cli
- Codex CLI, IDE extension, or app
- Grepr CLI installed and configured (see CLI section above)
codex plugin marketplace add grepr/cli --ref main
codex plugin add grepr@grepr-cliCLI:
npm update -g @grepr/cliClaude Code plugin:
/plugin marketplace update grepr-cli
/plugin install grepr@grepr-cli
Codex plugin:
codex plugin marketplace upgrade grepr-cli
codex plugin add grepr@grepr-cliBug reports and feature requests go to github.com/grepr/cli/issues. For Grepr platform questions, see docs.grepr.ai or contact support@grepr.ai.
Apache-2.0. See LICENSE.