Skip to content

fix: Fix issue where assign invocation intermittently drops the message#21

Open
patricka3125 wants to merge 5 commits intomainfrom
fix/assign_dropped_msg
Open

fix: Fix issue where assign invocation intermittently drops the message#21
patricka3125 wants to merge 5 commits intomainfrom
fix/assign_dropped_msg

Conversation

@patricka3125
Copy link
Copy Markdown
Owner

@patricka3125 patricka3125 commented Apr 4, 2026

Address issue #20

patricka3125 and others added 5 commits April 3, 2026 12:01
…lse positives (awslabs#142)

* fix WAITING_USER_ANSWER regex

* formatting

---------

Co-authored-by: haofeif <56006724+haofeif@users.noreply.github.com>
…arent restrictions (awslabs#141) (awslabs#144)

_resolve_child_allowed_tools() treated ["*"] the same as None (no opinion),
causing restricted parents to override a child's explicit unrestricted config.
Split the condition so ["*"] returns None (unrestricted) while None inherits.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
awslabs#146)

* fix(launch): clarify confirmation prompt — show Role, remove Blocked, distinguish Y vs --yolo

The launch confirmation prompt was misleading: it showed "Blocked: (none)" for
providers that enforce restrictions natively (kiro-cli, q-cli), and the --yolo
hint didn't make clear that users need to exit and re-run. Now the prompt shows
Role and Allowed in CAO vocabulary, and clearly explains that [Y] keeps
restrictions while [--yolo] overrides everything.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* feat(launch): add --auto-approve flag to skip confirmation prompt

Adds --auto-approve to skip the confirmation prompt while keeping tool
restrictions enforced. Useful for automated flows, scripted launches,
and agent-to-agent workflows where --yolo is too permissive.

Addresses review feedback on PR awslabs#146 re: automated flows hanging on
the Y/n prompt.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: clarify TOOL_MAPPING role and why only 3 providers need it

Rewrite the "How Tool Restrictions Are Enforced" section to explain
why TOOL_MAPPING only covers Claude Code, Copilot CLI, and Gemini CLI
(they need translation to native tool names), while Kiro CLI, Q CLI,
Kimi CLI, and Codex accept CAO vocabulary directly.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix(launch): clarify prompt hints — say "relaunch with" not bracket options

The prompt hints like [--auto-approve] and [--yolo] implied users could
type them at the Y/n prompt. Changed to "relaunch with --auto-approve"
and "relaunch with --yolo" to make clear these are CLI flags for the
next launch, not options at the current prompt.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants