​

tags

orc tags manages tags used to organize questions in a Workspace. Retrieve a list, create or update names and display colors, or soft-delete tags.

Authentication and access to the target Workspace are required. Use tag IDs returned by listing for updates and deletion. Attach tags to questions through orc prompts tags update; attachment is separate from creating a tag.

Inspect tags and their IDs.

List Workspace tags. Use --limit and returned cursors for pagination.

name is required and limited to 64 characters. Optional color uses a registered color name. Use --idempotency-key for retries.

Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.

Type: string. Optional.

(required) Tag name, from 1 to 64 characters. Must be unique among active tags in this workspace, ignoring case.; max 64 chars

Type: string. Optional.

Display color token. Defaults to gray when omitted.; enum: gray|red|orange|yellow|lime|green|cyan|blue|purple|fuchsia|pink|emerald|amber|violet|indigo|teal|sky|rose|slate|zinc|neutral|stone

Type: string. Optional.

Create a tag with a display color

Update supplied name and color by tag ID. Clear the color with --color null or --color reset.

Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.

Type: string. Optional.

Replacement tag name. Omit to retain the current name.; max 64 chars

Type: string. Optional.

Replacement color token. Send null to clear the stored color; omit to retain it.; enum: |gray|red|orange|yellow|lime|green|cyan|blue|purple|fuchsia|pink|emerald|amber|violet|indigo|teal|sky|rose|slate|zinc|neutral|stone; (use "null" or "reset" to clear)

Type: string. Optional.

Clear a tag’s display color

Soft-delete a tag by ID. Check the target Workspace and ID first.

Colors are gray, red, orange, yellow, lime, green, cyan, blue, purple, fuchsia, pink, emerald, amber, violet, indigo, teal, sky, rose, slate, zinc, neutral, and stone.

prompts tags update replaces all associations, so include existing tag IDs you want to preserve along with the new tag. A tag name cannot be used as the prompt ID argument.

Access to the target Workspace is required. Changes require the corresponding write permissions.

The following global options can be used with orc tags:

For details and examples, see global options.