clanker request raise
Raise a request on a ticket. Unless it has a fallback, the ticket needs a human until someone resolves it. With --client it is your clanker's, and the answer comes back to this session
clanker request raise [options] <id> <what>
Arguments
<id>stringRequiredThe ticket's ID, such as WEB-31
<what>stringRequiredWhat you ask, in one line of up to 200 characters
Options
--kind <kind>stringRequiredHow it is answered
approvechooseanswerdo--details <markdown>stringWhy, or for do the steps to take
--choice <label...>stringA choose request's 2 to 6 options, the one you recommend first
--format <format>stringWhat an answer request takes
textlink--document <slug:revision...>stringA ticket document to read, such as plan:3
--pull-request <url...>stringA pull request to look at
--link <label=url...>stringA link to open, such as Preview=https://…
--command <command...>stringA command to run
--for <person>stringWho should answer; the ticket's owner when left out
--item <item>stringAn open Human item of the ticket's current checklist that it settles
--fallback <answer>stringWhat you go with meanwhile; the request then does not block
--client <client>stringRaise it as your clanker in this client
claudecodexcursor--session <id>stringWith --client, the session its answer goes to; this Claude Code session by default
--workspace <slug>stringWorkspace slug or id (default: the linked workspace)
clanker request raise WEB-31 "Hosted search, or an index built into the docs site?" --kind choose --choice "Built-in index" --choice "Hosted service" --document plan:3clanker request raise WEB-31 "Add the TXT record for docs.acme.dev" --kind do --details "1. Open Cloudflare DNS for acme.dev. 2. Add TXT _verify." --command "dig +short TXT _verify.docs.acme.dev"clanker request raise WEB-31 "Approve the Plan" --kind approve --document plan:4 --client claude