pup
CLAUDE.md1k starsChanged 6 months agoApache-2.0View on GitHub
Rust-based CLI wrapper for Datadog APIs. Provides OAuth2 + API key authentication across a wide range of Datadog product domains. All PRs are reviewed against docs/REVIEW.md. Read it before submitting. Key rules: All commands follow consistent patterns:
- Reads credentials
- Installs packages
- Commits and pushes
1 other project uses a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- datadog-labs/pupword for word, first seen Oct 8, 2026
Who's talking about DataDog/pup
- A Hacker News story“Pup – Datadog CLI”Hacker News · Feb 10, 2026 · 4 points
- DataDog/terraform-provider-datadog“[datadog_provider] Add use_pup to authenticate with a pup login”GitHub · Nov 12, 2026 · 2 reactions
- DataDog/terraform-provider-datadog“[datadog_provider] Add bearer_token_command to refresh Bearer tokens from a command”GitHub · Oct 20, 2026 · 1 reactions
- datadog-labs/homebrew-pack“feat(policy): add trust policy for pup release workflow”GitHub · Feb 10, 2026 · 1 reactions
- Groupe-Hevea/tools-aquaproj“chore(deps): update dependency datadog-labs/pup to v2.4.5”GitHub · Nov 15, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub and Hacker News (50 times).
On GitHub · 49
- Nov 12, 2026[datadog_provider] Add use_pup to authenticate with a pup login — DataDog/terraform-provider-datadog2 reactions · 2 comments
- Oct 20, 2026[datadog_provider] Add bearer_token_command to refresh Bearer tokens from a command — DataDog/terraform-provider-datadog1 reaction · 3 comments
- Feb 10, 2026feat(policy): add trust policy for pup release workflow — datadog-labs/homebrew-pack1 reaction · 2 comments
- Nov 15, 2026chore(deps): update dependency datadog-labs/pup to v2.4.5 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 14, 2026chore(deps): update dependency datadog-labs/pup to v2.4.4 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
44 more on GitHub
- Nov 14, 2026chore(deps): update dependency datadog-labs/pup to v2.4.7 — mikutas/dotfiles0 reactions
- Nov 13, 2026chore(deps): update dependency datadog-labs/pup to v2.4.6 — mikutas/dotfiles0 reactions
- Nov 13, 2026chore(deps): update dependency datadog-labs/pup to v2.4.5 — mikutas/dotfiles0 reactions
- Nov 12, 2026chore(deps): update dependency datadog/pup to v2.4.7 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 12, 2026chore(deps): update dependency github:datadog/pup to v2.4.7 — JP-Ellis/dotfiles0 reactions
- Nov 11, 2026chore(deps): update dependency datadog/pup to v2.4.5 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 11, 2026Update dependency github:DataDog/pup to v2.4.2 — BarryThePenguin/dotfiles0 reactions
- Nov 10, 2026chore(deps): update dependency datadog-labs/pup to v2.4.3 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 10, 2026chore(deps): update all non-major dependencies — tak848/dotfiles0 reactions · 2 comments
- Nov 10, 2026chore(deps): update dependency github:datadog/pup to v2.4.4 — JP-Ellis/dotfiles0 reactions
- Nov 10, 2026chore(deps): update dependency datadog/pup to v2.4.3 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 8, 2026chore(deps): update dependency datadog-labs/pup to v2.4.2 — mikutas/dotfiles0 reactions
- Nov 7, 2026chore(deps): update dependency github:datadog/pup to v2.4.2 — JP-Ellis/dotfiles0 reactions
- Nov 7, 2026chore(deps): update dependency datadog/pup to v2.4.2 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 6, 2026chore(deps): update dependency datadog-labs/pup to v2.4.1 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 6, 2026chore(deps): update dependency datadog-labs/pup to v2.4.1 — mikutas/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.10 — BarryThePenguin/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.8 — BarryThePenguin/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.7 — BarryThePenguin/dotfiles0 reactions
- Nov 5, 2026Update dependency github:DataDog/pup to v2.3.6 — BarryThePenguin/dotfiles0 reactions
- Nov 4, 2026Update dependency github:DataDog/pup to v2.3.5 — BarryThePenguin/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency datadog/pup to v2.4.1 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 3, 2026Update dependency github:DataDog/pup to v2.3.4 — BarryThePenguin/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency github:datadog/pup to v2.4.1 — JP-Ellis/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency datadog/pup to v2.4.0 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 3, 2026chore(deps): update dependency datadog-labs/pup to v2.3.10 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 3, 2026Update dependency github:DataDog/pup to v2.3.3 — BarryThePenguin/dotfiles0 reactions
- Nov 2, 2026Update dependency github:DataDog/pup to v2 — BarryThePenguin/dotfiles0 reactions
- Nov 2, 2026Update dependency github:DataDog/pup to v1.27.1 — BarryThePenguin/dotfiles0 reactions
- Nov 1, 2026chore(deps): update dependency datadog-labs/pup to v2.3.8 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 31, 2026chore(deps): update dependency datadog-labs/pup to v2.3.10 — mikutas/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.5 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 30, 2026chore(deps): update dependency github:datadog/pup to v2.3.10 — JP-Ellis/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.6 — mikutas/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog/pup to v2.3.10 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.3 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 29, 2026chore(deps): update dependency datadog/pup to v2.3.6 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 29, 2026chore(deps): update dependency github:datadog/pup to v2.3.8 — JP-Ellis/dotfiles0 reactions
- Oct 26, 2026chore(deps): update dependency datadog/pup to v2.3.3 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 26, 2026chore(deps): update dependency github:datadog/pup to v2.3.5 — JP-Ellis/dotfiles0 reactions
- Sep 21, 2026[Plugin]: pup — using-system/otelyssey0 reactions · 6 comments
- Aug 23, 2026Add dsf WASM apps, named-sandbox connect, and TensorLake tool_runner door — rita-aga/temper0 reactions
- Jul 15, 2026Is a CLI in the roadmap? — incident-io/sdk-go0 reactions · 4 comments
- Jun 23, 2026Datadog, 'Pup' 오픈소스 공개 — 33개 Datadog 제품 200여 개 명령어를 AI 에이전트가 직접 호출 가능한 CLI로 제공 — roomedia/ax-trend0 reactions
On Hacker News · 1
- Feb 10, 2026Pup – Datadog CLI4 points
Other versions1 project uses a version of this.
Word for word · 1
- datadog-labs/pup★ 1k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- pupSkill
- dd-apmSkill
- dd-code-generationSkill
- dd-debuggerSkill
- dd-docsSkill
- dd-file-issueSkill
- dd-idpSkill
- dd-logsSkill
- dd-monitorsSkill
- dd-pupSkill
- dd-symdbSkill
- dd-triage-flaky-testSkill
- dd-unblock-prSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
17 rules. About 0 are common, 12 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 10
[TESTING.md](docs/TESTING.md): - Test strategy, coverage requirements, CI/CD
- Very specific: line 21
Reuse existing code: Search src/util.rs, src/output.rs, src/client.rs, and src/settings.rs before writing new helpers.
- Distinctive: line 22
Test both paths: Every change must include positive tests (happy path) and negative tests (error cases, bad input, edge cases).
- Very specific: line 24
No vulnerable dependencies: Only use latest stable crate versions with no known CVEs.
- Distinctive: line 77
All commands follow consistent patterns:
- Distinctive: line 106
Follow Rust conventions and idioms
- Very specific: line 107
Use cargo fmt and cargo clippy
- Distinctive: line 108
Keep functions small and focused
- Distinctive: line 109
Write clear, self-documenting code
- Very specific: line 112
Use anyhow for application errors: anyhow::bail!("context")
- Distinctive: line 114
Never expose API keys in errors
- Distinctive: line 117
Write unit tests for public functions
- Very specific: line 118
Use #[test] with assert_eq!
- Distinctive: line 179
Never commit credentials (API keys, tokens, secrets)
- Distinctive: line 180
Never log or print access/refresh tokens
- Distinctive: line 182
Use PKCE S256 for OAuth2 flows
- Distinctive: line 190
Default values (lowest priority)
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pup - Datadog API CLI
Rust-based CLI wrapper for Datadog APIs. Provides OAuth2 + API key authentication across a wide range of Datadog product domains.
Documentation Index
- ALIASES.md - Alias management (storage, commands, expansion)
- COMMANDS.md - Complete command reference
- CONTRIBUTING.md - Git workflow, PR process, commit format
- TESTING.md - Test strategy, coverage requirements, CI/CD
- REVIEW.md - Code review guidelines (read before submitting PRs)
- OAUTH2.md - OAuth2 implementation details (DCR, PKCE, token storage)
- EXAMPLES.md - Usage examples and common workflows
- ARCHITECTURE.md - Design decisions and technical details
- TROUBLESHOOTING.md - Common issues and debugging
Review Guidelines
All PRs are reviewed against docs/REVIEW.md. Read it before submitting. Key rules:
- Reuse existing code. Search
src/util.rs,src/output.rs,src/client.rs, andsrc/settings.rsbefore writing new helpers.src/formatter.rsandsrc/config.rsare generator-owned contracts; hand-maintained output logic belongs insrc/output.rs, and configuration loading and precedence belong insrc/settings.rs. Do not duplicate functionality that already exists. - Test both paths. Every change must include positive tests (happy path) and negative tests (error cases, bad input, edge cases).
- No malicious code. Obfuscated logic, backdoors, exfiltration, or unauthorized network calls result in rejection and a ban.
- No vulnerable dependencies. Only use latest stable crate versions with no known CVEs. Run
cargo auditbefore submitting. - Keep it simple. Small functions, shallow nesting, no premature abstractions. Prefer explicit over clever.
- Follow Rust standards.
cargo fmt,cargo clippy -- -D warnings,anyhowfor errors, idiomaticOption/Resultusage. - Minimal diffs. One concern per PR. Don't touch unrelated code, reformat untouched files, or add unnecessary improvements.
Quick Start
# Install via Homebrew (recommended)
brew tap datadog-labs/pack
brew install pup
# Or clone and build from source
git clone https://github.com/DataDog/pup.git && cd pup
cargo build --release
cp target/release/pup /usr/local/bin/pup
# Authenticate (OAuth2 recommended)
pup auth login
# Or use API keys (legacy)
export DD_API_KEY="key" DD_APP_KEY="key" DD_SITE="datadoghq.com"
# Run a command
pup monitors list --tag="env:production"
pup metrics query --query="avg:system.cpu.user{*}" --from="1h"Project Structure
pup/
├── src/
│ ├── main.rs # CLI entry point, clap enums, command routing
│ ├── commands/ # Command modules (monitors.rs, logs.rs, runbooks.rs, etc.)
│ ├── auth/ # OAuth2 + DCR + PKCE + token storage
│ ├── runbooks/ # Runbook engine (loader, template renderer, executor)
│ ├── client.rs # Datadog API client wrapper
│ ├── config.rs # Generator-owned configuration contract
│ ├── formatter.rs # Generator-owned formatting contract
│ ├── output.rs # Output rendering and printing (JSON envelope, YAML, table, CSV, TSV)
│ ├── settings.rs # Configuration loading, precedence, and storage paths
│ ├── useragent.rs # AI agent detection (User-Agent token, prompt auto-approval)
│ ├── util.rs # Time parsing, validation
│ └── version.rs # Version and build info
├── tests/ # E2E parity report
├── docs/ # Extended documentation
├── Cargo.toml # Rust dependencies
└── Cargo.lockCommand Structure
All commands follow consistent patterns:
pup <domain> <action> [options]
pup <domain> <subgroup> <action> [options]
# Examples
pup monitors list --tag="env:prod"
pup logs search --query="status:error" --from="1h"
pup rum apps list
pup security rules listSee COMMANDS.md for complete reference.
Development Workflow (For Agents)
1. Branch Creation
git checkout -b <type>/<description>
# Types: feat, fix, refactor, docs, test, chore, perf
# Example: feat/add-metrics-filtering2. Code Changes
Code Style:
- Follow Rust conventions and idioms
- Use
cargo fmtandcargo clippy - Keep functions small and focused
- Write clear, self-documenting code
Error Handling:
- Use
anyhowfor application errors:anyhow::bail!("context") - Wrap errors with context:
.map_err(|e| anyhow::anyhow!("context: {e:?}")) - Never expose API keys in errors
Testing:
- Write unit tests for public functions
- Use
#[test]withassert_eq! - Mock external dependencies
- Run with
cargo test
3. Commit
Stage specific files and commit with conventional format:
git add src/commands/specific_file.rs
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body describing what and why>
- Key change 1
- Key change 2
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
EOF
)"Commit types: feat, fix, docs, style, refactor, test, chore
4. Create PR
gh pr create \
--title "<type>(<scope>): <clear title>" \
--body "$(cat <<'EOF'
## Summary
1-2 sentences describing what and why.
## Changes
- Change 1 with file reference (src/commands/foo.rs:123)
- Change 2 with file reference
## Testing
- How changes were tested
- Test coverage details
## Related Issues
Closes #N
---
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"See CONTRIBUTING.md for detailed workflow and examples.
Security Requirements
Authentication:
- OAuth2 with PKCE (recommended):
pup auth login - API keys (legacy):
DD_API_KEY+DD_APP_KEY+DD_SITE - Token storage: OS keychain (primary), JSON file with
0600permissions (fallback)
Security Rules:
- Never commit credentials (API keys, tokens, secrets)
- Never log or print access/refresh tokens
- Validate all user inputs to prevent injection
- Use PKCE S256 for OAuth2 flows
- Restrict fallback token-storage file to
0600permissions
Configuration Precedence
- Command-line flags (highest priority)
- Environment variables
- Config file (
~/.config/pup/config.yaml) - Default values (lowest priority)
CI/CD Requirements
All PRs must pass:
cargo testcargo clippy -- -D warningscargo fmt --check- Cross-compilation for 4 targets
See TESTING.md for details.
Core Dependencies
- Rust (stable)
- datadog-api-client-rust - Official API client (pinned to a git rev in
Cargo.toml) - clap v4 - CLI framework (derive macros)
- tokio - Async runtime
- serde + serde_json + serde_norway - Serialization
- keyring v3 - OS keychain integration
- reqwest - HTTP client
License
Apache 2.0 - Copyright 2024-present Datadog, Inc.
Support
- Issues: GitHub Issues
- Community: Datadog Community
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

