Repo brief: Nukesor/pueue

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T06:03:43.186Z · commit 8b9d6fef8199

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 1w ago
• 5 active contributors
• Apache-2.0 licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Pueue is a daemon-based command queue manager written in Rust that allows you to schedule, execute, and manage shell commands with sequential or parallel execution. It persists task state to disk, supports task dependencies and groups, and lets you control tasks from any terminal via a client-daemon architecture—solving the problem of running long-lived background tasks without keeping a terminal session open. Workspace with two main crates: pueue/ (client and daemon binary in src/bin/pueue.rs and src/bin/pueued.rs) and pueue_lib/ (shared library). Client code in pueue/src/client/ with command modules (add.rs, clean.rs, edit.rs, follow.rs, etc.), daemon logic separate, state persisted…

Start here

Open these first:

• pueue/src/bin/pueued.rs — Daemon entry point that initializes the background task processor, network server, and state management—every contributor…
• pueue/src/bin/pueue.rs — Client CLI entry point that parses commands and communicates with the daemon—essential for understanding the user-facing…
• pueue/src/daemon/internal_state/state.rs — Core state machine managing task queues, groups, and execution status—the heart of Pueue's data model that all handlers…
• pueue/src/daemon/network/message_handler/mod.rs — Central dispatcher routing client commands to appropriate handlers—critical for understanding how client requests are…
• pueue/src/client/cli.rs — CLI argument parser and command routing—defines the command structure and options users interact with.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/Nukesor/pueue.git
cd pueue
cargo build --release
./target/release/pueued &  # Start daemon
./target/release/pueue add 'your command here'  # Add task
./target/release/pueue status  # Check queue

Daily commands:

Development: just test (Justfile present) or cargo test --workspace. Start daemon: cargo run --bin pueued -- --daemon. Start client: cargo run --bin pueue -- status. CI/CD uses nextest (config/.config/nextest.to…

…shortened for this brief.

Key cautions & unknowns

• Single-maintainer risk — top contributor 87% of recent commits
• Daemon must be running before client commands work (no auto-start). State is persisted as CBOR (not human-readable)—check ~/.local/share/pueue/ on Linux or use pueue log to view task output. TLS handshake required…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.