# 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

## Usage

```bash
clanker request raise [options] <id> <what>
```

## Arguments

- `<id>`: The ticket's ID, such as WEB-31
- `<what>`: What you ask, in one line of up to 200 characters

## Options

- `--kind <kind>` (required): How it is answered One of `approve`, `choose`, `answer`, `do`.
- `--details <markdown>`: Why, or for do the steps to take
- `--choice <label...>`: A choose request's 2 to 6 options, the one you recommend first
- `--format <format>`: What an answer request takes One of `text`, `link`.
- `--document <slug:revision...>`: A ticket document to read, such as plan:3
- `--pull-request <url...>`: A pull request to look at
- `--link <label=url...>`: A link to open, such as Preview=https://…
- `--command <command...>`: A command to run
- `--for <person>`: Who should answer; the ticket's owner when left out
- `--item <item>`: An open Human item of the ticket's current checklist that it settles
- `--fallback <answer>`: What you go with meanwhile; the request then does not block
- `--client <client>`: Raise it as your clanker in this client One of `claude`, `codex`, `cursor`.
- `--session <id>`: With --client, the session its answer goes to; this Claude Code session by default
- `--workspace <slug>`: Workspace slug or id (default: the linked workspace)

## Examples

```bash
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:3
clanker 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
```