feat: 1.2.0 multi-agent coordination commands#21
Merged
Conversation
Brings the CLI in line with @delega-dev/mcp 1.2.0. The 1.1 release
focused on agent-friendly polish (--yes, --json, --dry-run flags on
destructive ops); this release adds the missing command coverage.
New commands (6):
- `delega tasks assign <task_id> <agent_id | --unassign>` — assign or
unassign a task. For multi-agent handoffs use `delegate` instead —
`assign` does not record a chain.
- `delega tasks chain <task_id>` — show the full parent/child
delegation chain, indented by depth. Renders the tree-ish view
(hosted {root_id} vs self-hosted {root: Task} both normalized).
- `delega tasks set-context <task_id> --kv key=value...` — deep-merge
keys into persistent context. Accepts repeated --kv pairs
(JSON-parsed values so numbers/bools/arrays work) or a full
--context '{...}' JSON object.
- `delega tasks dedup --content "..." [--threshold 0.6]` — Jaccard
similarity check against open tasks. Call before `tasks create` to
avoid redundant work.
- `delega agents delete <id>` — delete an agent. --yes / --dry-run
follow the existing 1.1 destructive-action pattern.
- `delega usage` — plan quota + rate-limit info. Hosted API only;
gated client-side with a clear error on self-hosted, mirroring the
delega-mcp + delega-python behavior.
All commands follow the existing pattern: Commander subcommand,
apiCall<T>, human-readable default output with --json opt-out.
Version: 1.1.5 → 1.2.0 (minor — 6 new commands, no breaking changes).
Verified: tsc --noEmit clean; build clean; `delega <new> --help`
renders; hosted-only gate on `delega usage` prints a clear error
against a self-hosted URL without making a request.
Out of scope:
- No test suite. The CLI CI runs typecheck + build only (pre-existing).
A proper test harness is a separate project. Relying on live smoke
against the hosted API after release.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Brings the CLI in line with @delega-dev/mcp 1.2.0. The 1.1 release focused on agent-friendly polish (--yes, --json, --dry-run flags); this adds the missing command coverage.
New commands (6)
Version: 1.1.5 → 1.2.0
Minor bump. All additions are backward compatible. Every command follows the existing pattern: Commander subcommand, `apiCall`, human-readable default with `--json` opt-out.
Test plan
Release
Tag `v1.2.0` after merge — `.github/workflows/publish.yml` publishes to npm + creates the GitHub Release.
Out of scope
🤖 Generated with Claude Code