GeezerVison is showing github.com — Add Kujo CMD lifecycle and status mod by robertdevore · Pull Request #1053 · CommandCodeAI/command-code
Conversation
Adds Kujo CMD to the mods directory using the npm package @kujolang/kujo-cmd, with registry name kujo-cmd and both source and npm set to @kujolang/kujo-cmd.
Kujo CMD provides /kujo help, /kujo setup, and /kujo status, metadata-only Watchdog correlation, and a one-shot continuation after failed Kujo calls. Explicit package-mode setup connects the local MCP tools, skills, scoped agents, request-bound approvals, and execution receipts.
Review changes
- Watchdog recording, delivery, and spool replay require valid project configuration or explicit
KUJO_CMD_WATCHDOG=1. KUJO_CMD_WATCHDOG=0 disables them even in configured projects. An unconfigured project is left untouched.
- A spool directory is created only after retryable delivery failures, with at most 100 batches. Setup, update, and repair add
/.kujo/watchdog-spool/ to .gitignore while preserving existing rules.
- README explains that the seven agents'
permissionMode: dont-ask does not bypass the Kujo runtime's human approval for mutating Abilities.
- The registry now uses npm as requested.
Release status
The fixes are tagged v0.3.1 at bb8703c. The provenance-enabled npm release workflow completed successfully. @kujolang/[email protected] is published on npm and is the latest release. Its SHA-512 integrity, registry signatures, and provenance attestations were verified. The provenance points to bb8703c3159a198b93c379ba414a883ec68e4489 and this release workflow; the published package contents match the checkout.
Verification
- All 25 automated package/runtime/approval/security/setup/mod tests passed locally.
- Real end-to-end coverage passed for 19 tools, including browser checks, approvals, receipts, concurrency, and restart.
- Command Code 1.85.1 and 1.88.0 passed production-only tarball installation with lifecycle scripts disabled, package-mode migration, MCP discovery, and the packed mod leaving unconfigured projects untouched. The 1.88.0 rerun on 2026-10-23 used an explicit binary path and a version assertion; it confirmed five Essentials Abilities, three skills, seven agents, and the factory lifecycle hooks.
- Registry schema/format validation passed; all existing upstream entries are preserved.
- Current cross-platform CI passed on Linux, macOS, and Windows. It includes the Windows test-fixture correction at
7dedc53; that test-only commit does not change the published package.
The host checks used local-only mode with a temporary non-secret key placeholder, originally needed for Command Code 1.85.1's key-presence preflight. Real-tool checks used local source checkouts. This release does not claim a new interactive/model-backed session or Desktop verification.
Package source · Dated verification record
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the submission, @robertdevore, and for the detailed verification record. We reviewed the published @kujolang/[email protected] package (integrity and provenance check out, code matches kujolang/kujo-cmd@271b580). Setup is opt in, and the legacy bridge removal is carefully limited to files Kujo owns. One change is needed before we can list it.
Blocking: the mod writes .kujo/watchdog-spool/ into every project
In assets/command-code/mods/kujo-command-bridge.ts, every run emits Watchdog records whether or not Kujo was set up for that project. submit() creates <project>/.kujo/watchdog-spool/ on each call (line 56), and when nothing is listening on 127.0.0.1:7700 each batch is saved there (up to 100 files). Someone who installs the mod from the mods hub and never runs setup ends up with an untracked .kujo/ folder in every repo they open, and it is not gitignored.
Could you skip recording and spooling unless the project is configured, for example when .kujo/cmd.json exists or the user opts in with an env var? Adding the spool folder to .gitignore during setup would also help for configured projects.
Registry entry
Since 0.3.0 is now published on npm with provenance, please switch the entry to the npm source so the mods hub installs a pinned, verified version instead of the default branch:
"name": "kujo-cmd",
"source": "@kujolang/kujo-cmd",
"npm": "@kujolang/kujo-cmd", Non blocking note
The seven setup agents use permissionMode: dont-ask, including ones with tools that make changes. We saw that the Kujo runtime still requires a human approval for abilities that are not read only, so this is fine, but it is worth stating in the README so users know where the approval happens.
Once a release with the spool fix is on npm, push the updated entry here and we will take another look.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
@ahmadbilaldev Thanks for the detailed review! Fixed the Watchdog recording/spooling issue, added the gitignore rule, clarified runtime approvals in the README, and switched the registry entry to npm.
The fixes are published in @kujolang/[email protected] with verified provenance. Tests and CI passed, including compatibility checks against Command Code 1.88.0. The PR description has the details and is ready for another look. Thanks!
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Reviewers
Requested changes must be addressed to merge this pull request.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|