NextClaw v0.51.0
Released: 2026-09-10
Tags: user feedback, maintenance automation, CLI, Codex
NextClaw v0.51.0 closes the maintenance loop from feedback approval to local handling and a reply on the original post. The feedback platform continues to own posts, comments, state, and approval. A local maintainer consumes approved events and runs the command you configure.
New features
nextclaw feedback maintain configuresets the feedback endpoint, private credential, and any executable command.nextclaw feedback maintain startwatches for approved feedback in the background. Idle scans never call a model.status,stop, andrestartprovide an observable and recoverable local lifecycle.- The included Codex Desktop preset creates a task for the first event and resumes that task after user follow-ups. A custom command can connect another AI, a script, or a notification system.
Safety and state
- The first repair requires administrator approval. A user follow-up requires another approval before further repair work.
- Credentials live in a separate permission-restricted file. Trigger commands run as argument arrays without a shell.
- Feedback, events, repair runs, and local task mappings are persisted separately so interrupted work can resume. Maintainer comments cannot create a self-reply loop.
What you need to do
After upgrading, maintainers configure the bridge once with nextclaw feedback maintain configure, then run nextclaw feedback maintain start. People submitting feedback do not need a GitHub account and do not need to change the existing submission flow.