Skip to content

Require attachment state when claiming Cuey requests #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kkkyuecheng merged 1 commit into from
Aug 25, 2026
Merged

Require attachment state when claiming Cuey requests #26

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion plugins/cuey/skills/cuey/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Before using any tool, classify the invocation:

## Ask Cuey

Before inspecting attachments, running commands, reading files, recalling memory, searching, or doing any other work, call `cuey:claim_cuey_request` with the exact original `$ARGUMENTS` as `question`.
Before inspecting or reading attachments, running commands, reading files, recalling memory, searching, or doing any other work, determine only whether the current request includes one or more Claude-visible attachments. Then call `cuey:claim_cuey_request` with the exact original `$ARGUMENTS` as `question` and `expectsAttachments` set to `true` when attachments are present or `false` when there are none. This boolean is required; do not infer it from the question text.

- If it returns `status: "claimed"`, retain the returned `requestId`. Only then may you collect the attachment feature matrix described below. Pass that exact `requestId` unchanged to `cuey:start_cuey`.
- If it returns `status: "handoff"` with a `requestId`, another Cuey execution already owns the request. Retain that `requestId`, do not inspect attachments, do not call `cuey:start_cuey`, and immediately poll `cuey:get_cuey_result` with that `requestId` until Cuey returns the final result.
Expand Down
Loading