export declare const SKILL_NAME = "comms-cli"; export declare const SKILL_DESCRIPTION = "Comms messaging CLI. View and respond to inbox threads, channel threads, direct messages, mentions, and group conversations; search, react, archive, mute, and manage workspaces. Use when the user mentions Comms, asks about their inbox, mentions, threads, DMs, channels, or wants to read or send Comms messages."; export declare const SKILL_AUTHOR = "Doist"; export declare const SKILL_LICENSE = "MIT"; export declare const SKILL_VERSION: string; export declare const SKILL_CONTENT = "# Comms CLI (tdc)\n\nAccess Comms messaging via the `tdc` CLI. Use when the user asks about their Comms workspaces, threads, messages, or wants to interact with Comms in any way.\n\n## Setup\n\n```bash\ntdc auth login # OAuth login (standard write scopes)\ntdc auth login --read-only # OAuth login with read-only scope\ntdc auth login --full-access # OAuth login with delete/admin scopes\ntdc auth login --credential-store system # Require the system credential manager\ntdc auth login --credential-store plaintext # Explicitly allow plaintext config storage\ntdc auth login --callback-port # Override the local OAuth callback port (default 8766)\ntdc auth login --json # Emit a JSON envelope for scripted / agent use\ntdc auth login --ndjson # Emit an NDJSON envelope for scripted / agent use\ntdc auth token # Save API token manually (prompts securely; scope unknown, assumed write-capable)\ntdc auth token --credential-store system # Require the system credential manager\ntdc auth status # Verify authentication + show mode\ntdc auth status --json # Full status payload as JSON (--ndjson also supported)\ntdc auth status --user # Target a specific stored account (id, id:, or display name)\ntdc --user auth # Equivalent to passing --user after the subcommand; other commands accept the flag but ignore it\ntdc auth logout # Remove saved token and auth metadata\ntdc auth logout --json # Emits `{\"ok\": true}` (--ndjson is silent)\ntdc auth logout --user # Target a specific stored account; mismatched ref errors with ACCOUNT_NOT_FOUND\ntdc auth token view # Print the saved token to stdout (pipe-safe; refreshes an expiring OAuth token first; refuses if COMMS_API_TOKEN is set)\ntdc auth token view --user # Print the saved token for a specific stored account\ntdc auth refresh-token view # Print the saved OAuth refresh token to stdout (pipe-safe; OAuth logins only)\ntdc auth refresh-token view --user # Print the saved OAuth refresh token for a specific stored account\ntdc account [list|current|use |remove ] # Manage stored accounts; all support --json/--ndjson\n # current's payload is {id, label, authMode, authScope, source:\"config\"} | {source:\"env\"} | {source:\"token-only\"}\ntdc auth login # Re-running auth login with a different OAuth grant adds a NEW account; default stays pinned unless none was set\ntdc workspaces # List available workspaces\ntdc workspaces --ids-only # Output only workspace IDs\ntdc workspace use # Set current workspace\ntdc completion install # Install shell completions\ntdc config view # Show the current CLI configuration file (token masked)\ntdc config set # Set a user preference (e.g. unarchive-new-threads true)\ntdc doctor # Diagnose CLI setup and environment issues\ntdc update # Update CLI to latest version\ntdc changelog # Show recent changelog entries\ntdc migrate urls # Translate old twist.com URLs to Comms URLs (needs a Twist token)\n```\n\nOAuth login uses Todoist OAuth for Comms access. The default grant can read Comms data and create/update content or messages. It does not include delete, channel management, or user/workspace write scopes; use `tdc auth login --full-access` only when needed (all `tdc groups` writes and `tdc status set|clear` require it). Credential storage defaults to `fallback`: use the system credential manager when available, otherwise warn and save to `~/.config/comms-cli/config.json`. Pass `--credential-store system` to fail instead of writing plaintext, or `--credential-store plaintext` to choose config-file storage explicitly. `COMMS_API_TOKEN` always takes priority over the stored token.\n\nIn read-only mode (`tdc auth login --read-only`), commands that modify Comms data (reply, archive, react, delete, etc.) are blocked by the CLI. Externally provided tokens (`COMMS_API_TOKEN` or `tdc auth token`) are treated as unknown scope and assumed write-capable.\n\n## View by URL\n\n```bash\ntdc view # View any Comms entity by URL\n```\n\nRoutes automatically based on URL structure:\n- Message URL \u2192 `tdc msg view`\n- Conversation URL \u2192 `tdc conversation view`\n- Thread+comment URL \u2192 `tdc thread view` (comment ID extracted from URL)\n- Thread URL \u2192 `tdc thread view`\n\nURLs may use either `https://comms.todoist.com/{workspaceId}/...` or `https://comms.todoist.com/a/{workspaceId}/...`.\n\nAll target command flags pass through (e.g. `--json`, `--raw`, `--full`).\n\n## Inbox\n\n```bash\ntdc inbox # Show inbox threads\ntdc inbox --unread # Only unread threads\ntdc inbox --mentions # Only unread threads where you were mentioned (implies --unread)\ntdc inbox --archive-filter all # Show active + done threads\ntdc inbox --archive-filter archived # Show only done threads\ntdc inbox --channel # Filter by channel name (fuzzy)\ntdc inbox --since # Filter by date (ISO format)\ntdc inbox --limit # Max items (default: 50)\ntdc inbox --ids-only # Output only thread IDs, one per line\n```\n\n## Threads\n\n```bash\ntdc thread # View thread (shorthand for view)\ntdc thread view # View thread with comments\ntdc thread view --comment # View a specific comment\ntdc thread view # Comment ID extracted from URL\ntdc thread view --unread # Show only unread comments\ntdc thread view --context 3 # Include 3 read comments before unread\ntdc thread view --limit 20 # Max comments to show (default: 50; the header says when it left some out)\ntdc thread view --since # Comments newer than date\ntdc thread view --raw # Show raw markdown\ntdc thread create \"Title\" \"content\" # Create a new thread\ntdc thread create \"Title\" \"content\" --json # Create and return as JSON\ntdc thread create \"Title\" \"content\" --json --full # Include all thread fields\ntdc thread create \"Title\" \"content\" --notify 123,Cbzzm11ZeYZoJYD4a6rti # Notify user and/or group IDs\ntdc thread create \"Title\" \"content\" --unarchive # Land thread in author's Inbox (overrides default Comms auto-archive)\ntdc thread create \"Title\" \"content\" --no-unarchive # Force archive even when userSettings.unarchiveNewThreads=true\ntdc thread create \"Title\" \"content\" --dry-run # Preview without posting\ntdc thread create \"Title\" --file ./a.png # Attach a file (repeatable; content optional)\ntdc thread reply \"content\" # Post a comment (notifies EVERYONE_IN_THREAD by default)\ntdc thread reply \"content\" --notify NONE # Post without notifying anyone\ntdc thread reply \"content\" --notify NONE --dry-run # Preview without posting\ntdc thread reply \"content\" --notify EVERYONE # Notify all workspace members\ntdc thread reply \"content\" --notify 123,id:456 # Notify specific users by ID\ntdc thread reply \"content\" --notify 123,Cbzzm11ZeYZoJYD4a6rti # Notify a user and a group (group IDs are base58, not numeric)\ntdc thread reply \"content\" --json # Post and return comment as JSON\ntdc thread reply \"content\" --json --full # Include all comment fields\ntdc thread reply \"content\" --close # Reply and close the thread\ntdc thread reply \"content\" --reopen # Reply and reopen a closed thread\ntdc thread reply \"content\" --close --notify NONE # Reply and close without notifying anyone\ntdc thread reply \"content\" --file ./a.png # Attach a file (repeatable; content optional)\ntdc thread done # Preview thread archive (requires --yes to execute)\ntdc thread done --yes # Archive thread (mark done)\ntdc thread done --yes --json # Archive and return status as JSON\ntdc thread undone --yes # Unarchive thread (move it back to your inbox); inverse of done\ntdc thread undone --yes --json # Unarchive and return status as JSON\ntdc thread mark-read # Mark a thread read\ntdc thread mark-read --yes # Mark multiple threads read\nprintf \"id:CbT8n2Kp4Qx6Rz9Lm3Va\\nid:CbT9m4Qr7Vz2Nx8Lp5Sa\\n\" | tdc thread mark-read --stdin --dry-run # Preview bulk mark-read from stdin\ntdc thread mark-unread # Mark a whole thread unread; inverse of mark-read\ntdc thread mark-unread --from # Mark unread from that comment onward (single thread only)\ntdc thread mark-unread --yes # Mark multiple threads unread (also accepts refs on stdin with --stdin)\ntdc thread mute # Mute thread for 60 minutes (default)\ntdc thread mute --minutes 480 # Mute for custom duration\ntdc thread mute --json # Mute and return { id, mutedUntil } as JSON\ntdc thread mute --json --full # Mute and return full thread as JSON\ntdc thread unmute # Unmute a muted thread\ntdc thread unmute --json # Unmute and return { id, mutedUntil } as JSON\ntdc thread delete # Preview thread deletion (requires --yes to execute)\ntdc thread delete --yes # Permanently delete a thread\ntdc thread delete --yes --json # Delete and return status as JSON\ntdc thread rename \"New title\" # Rename a thread (change its title)\ntdc thread rename \"New title\" --json # Rename and return { id, title } as JSON\ntdc thread rename \"New title\" --json --full # Rename and return full thread as JSON\ntdc thread update \"New body\" # Update a thread's body (the first post)\necho \"New body\" | tdc thread update --stdin # Update body from stdin\ntdc thread update \"New body\" --dry-run # Preview without updating\ntdc thread update \"New body\" --json # Update and return { id, content } as JSON\ntdc thread update \"New body\" --json --full # Update and return full thread as JSON\n```\n\nDefault `--notify` for reply is EVERYONE_IN_THREAD, which may notify more people than intended. Before posting, confirm with the user whether specific people should be notified instead (via `--notify `) or nobody (via `--notify NONE`). Options: NONE, EVERYONE, EVERYONE_IN_THREAD, or comma-separated user and/or group IDs.\n\n`--notify NONE` sends empty user, group, and direct-mention recipient lists without adding a notification audience. It also works with `--close` and `--reopen`. The `--dry-run` preview displays `Notify: NONE`.\n\n`--notify` automatically resolves IDs: group IDs are routed to the `groups` API field, user IDs to `recipients`. No special syntax needed.\n\n## Thread Comments\n\n```bash\ntdc comment # View a comment (shorthand for view)\ntdc comment view # View a single thread comment\ntdc comment view --raw # Show raw markdown\ntdc comment view --json # Output as JSON\ntdc comment view --ndjson # Output as newline-delimited JSON\ntdc comment view --json --full # Include all fields in JSON output\ntdc comment update \"new content\" # Update a thread comment\ntdc comment update \"content\" --json # Update and return updated comment as JSON\ntdc comment update \"content\" --json --full # Include all comment fields\ntdc comment delete # Preview comment deletion (requires --yes to execute)\ntdc comment delete --yes # Delete a thread comment\ntdc comment delete --yes --json # Delete and return status as JSON\n```\n\n## Conversations (DMs/Groups)\n\n```bash\ntdc conversation unread # List unread conversations\ntdc conversation list # List active conversations (DMs and groups)\ntdc conversation list --kind group # Only group conversations (3+ people)\ntdc conversation list --kind direct # Only 1:1 conversations (and your self-DM)\ntdc conversation list --participant \"Jane\" # Only conversations including these users (comma-separated)\ntdc conversation list --name \"release\" # Filter by title substring (case-insensitive)\ntdc conversation list --state archived # Archived conversations only (active|all|archived; default active)\ntdc conversation list --snippet # Include the latest message snippet\ntdc conversation list --limit 20 --json # Cap rows and output as JSON\ntdc conversation list --ids-only # Output only conversation IDs\ntdc conversation unread --ids-only # Output only unread conversation IDs\ntdc conversation # View conversation (shorthand for view)\ntdc conversation view # View conversation messages\ntdc conversation with # Find your 1:1 DM with a user\ntdc conversation with --snippet # Include the latest message preview\ntdc conversation with --include-groups # List any conversations with that user\ntdc conversation reply \"content\" # Send a message\ntdc conversation reply \"content\" --json # Send and return message as JSON\ntdc conversation reply \"content\" --json --full # Include all message fields\ntdc conversation reply \"content\" --file ./a.png # Attach a file (repeatable; content optional)\ntdc conversation done # Preview conversation archive (requires --yes to execute)\ntdc conversation done --yes # Archive conversation\ntdc conversation done --yes --json # Archive and return status as JSON\ntdc conversation undone --yes # Unarchive conversation; inverse of done\ntdc conversation undone --yes --json # Unarchive and return status as JSON\ntdc conversation mute # Mute conversation for 60 minutes (default)\ntdc conversation mute --minutes 480 # Mute for custom duration\ntdc conversation mute --json # Mute and return { id, mutedUntil } as JSON\ntdc conversation mute --json --full # Mute and return full conversation as JSON\ntdc conversation unmute # Unmute a muted conversation\ntdc conversation unmute --json # Unmute and return { id, mutedUntil } as JSON\n```\n\nAlias: `tdc convo` works the same as `tdc conversation`.\n\n## Conversation Messages\n\n```bash\ntdc msg # View a message (shorthand for view)\ntdc msg view # View a single conversation message\ntdc msg update \"content\" # Edit a conversation message\ntdc msg update \"content\" --json # Edit and return updated message as JSON\ntdc msg update \"content\" --json --full # Include all message fields\ntdc msg delete # Preview message deletion (requires --yes to execute)\ntdc msg delete --yes # Delete a conversation message\ntdc msg delete --yes --json # Delete and return status as JSON\n```\n\nAlias: `tdc message` works the same as `tdc msg`.\n\n## Search\n\n```bash\ntdc mentions # Show content mentioning current user\ntdc mentions --since 2026-04-01 --all # Fetch every mention since a date\ntdc mentions --type threads --json # Limit mentions to threads\ntdc search \"query\" # Search content\ntdc search \"query\" --type threads # Filter: threads, messages, conversations, or all\ntdc search \"name\" --type conversations # Find a group chat by title\ntdc search \"query\" --author # Filter by author\ntdc search \"query\" --to # Messages sent to user\ntdc search \"query\" --title-only # Search thread titles only\ntdc search \"query\" --mention-me # Results mentioning current user\ntdc search \"query\" --conversation # Limit to conversations (comma-separated refs)\ntdc search \"query\" --since # Content posted since date\ntdc search \"query\" --until # Content posted until date\ntdc search \"query\" --channel # Filter by channel refs (comma-separated)\ntdc search \"query\" --limit # Max results (default: 50)\ntdc search \"query\" --cursor # Pagination cursor\ntdc search \"query\" --all # Fetch all result pages\n```\n\n`--since` and `--until` filter by when the matching content was posted, not when a thread was last active, so a thread found by its title (`--title-only`) counts from when it was created.\n\nTo find a group chat by name, use `tdc search \"name\" --type conversations` first. It matches whole words in group chat titles, and skips chats without a title. Use `tdc conversation list --name` for partial words, or `--participant` for chats without a title. Both `--name` and `--participant` can be combined with `--kind` or `--state`.\n\n`--type conversations` can't be combined with `--to`, `--channel`, or `--mention-me`. `--author` and `--since`/`--until` match the chat's creator and creation date.\n\n## Users, Channels & Groups\n\n```bash\ntdc user # Show current user info\ntdc user --json # JSON output\ntdc user --json --full # All fields, except session credentials\ntdc users # List active workspace users\ntdc users --search # Filter by name/email\ntdc users --include-removed # Include users removed from the workspace\ntdc users --ids-only # Output only user IDs\ntdc status # Show your status (default login is enough)\ntdc status --json # Show it as { status } JSON (null when unset; --full for the whole user)\ntdc status set \"Deep work\" --emoji \uD83C\uDFAF --for 2h --pause-notifications # Set supported fields (needs --full-access)\ntdc status set \"On holiday\" --pause-activity # Pause Todoist Karma and streaks while it is active (independent of --pause-notifications)\ntdc status set \"On holiday\" --until 2026-10-20T09:00 # End at a date (YYYY-MM-DD, YYYY-MM-DDTHH:MM or a full ISO 8601 timestamp; local time unless it has Z or an offset)\ntdc status set \"Away\" --dry-run # Preview without setting\ntdc status set \"Away\" --json # Set and return { status } as JSON\ntdc status clear # Clear your status (--dry-run, --json supported)\ntdc channels # List active joined workspace channels (alias of: tdc channel list)\ntdc channels --state all # Include archived joined channels too\ntdc channels --scope discoverable # Active public channels you can see but have not joined\ntdc channels --scope public --state all --json # All visible public channels, with joined status\ntdc channels --ids-only # Output only channel IDs\ntdc channel create \"Engineering\" # Create a channel in the current workspace\ntdc channel create \"Leadership Team\" --private --users id:10,id:20 # Create private channel with initial members\ntdc channel create \"Product\" --workspace \"Doist\" --description \"Product discussions\" --json # Create and return channel as JSON\ntdc channel update \"New name\" # Rename a channel\ntdc channel update --name \"New name\" # Rename with an explicit flag\ntdc channel update --description \"Team discussions\" # Update channel description\ntdc channel update --clear-description # Clear channel description\ntdc channel update --public # Make a channel public (--private makes it private)\ntdc channel update --description \"Team discussions\" --json --full # Update and return all channel fields\ntdc channel delete --yes # Permanently delete a channel (requires --yes; usually admin-only)\ntdc channel delete --dry-run # Preview deletion\ntdc channel archive # Archive a channel (no-op if already archived)\ntdc channel unarchive id: # Unarchive a channel (pass id: for archived channels)\ntdc channel threads # List threads in a channel (fuzzy name, id:, or URL)\ntdc channel threads \"general\" --unread # Only unread threads\ntdc channel threads --archive-filter all # Include archived threads (active|archived|all)\ntdc channel threads --since 2026-01-01 # Filter by last-updated date (ISO)\ntdc channel threads --limit 20 # Max threads per page (default: 50)\ntdc channel threads --limit 20 --cursor # Paginate\ntdc channel threads --json # { results, nextCursor } with isUnread + url\ntdc channel threads --ids-only # Output only thread IDs; pagination notice goes to stderr\ntdc channel members # List a channel's members + groups fully in the channel\ntdc channel members --json # JSON with id, name, workspaceId, members\ntdc channel members --ids-only # Output only member user IDs\ntdc channel members add alice group:Design # Add users and/or expand group: members\ntdc channel members add a@d.com id:789 --json # Add refs, output result as JSON\ntdc channel members remove alice group:Frontend # Remove users and/or group members\ntdc channel members set group:Squad --apply # Replace membership with the resolved set\ntdc channel members set alice bob # Dry-run by default; refuses to remove you (--include-self to override)\ntdc groups # List workspace groups\ntdc groups --search \"frontend\" # Filter groups by name (case-insensitive)\ntdc groups --json # JSON output\ntdc groups --ids-only # Output only group IDs\ntdc groups --json --full # Include all fields in JSON output\ntdc groups view # Show group with member details\ntdc groups view --json # JSON output with id, name, workspaceId, members\ntdc groups view --json --full # Include all fields in JSON output\ntdc groups create \"Name\" # Create a new group\ntdc groups create \"Name\" --users alice@doist.com,bob@doist.com # Create with members\ntdc groups create \"Name\" --json # Output created group as JSON\ntdc groups rename \"New name\" # Rename a group\ntdc groups rename \"Name\" --json # Output renamed group as JSON\ntdc groups delete --yes # Delete a group (requires --yes)\ntdc groups delete --dry-run # Preview deletion\ntdc groups add-user user1 user2 # Add users to a group\ntdc groups add-user a@d.com,b@d.com # Comma-separated refs\ntdc groups add-user id:123 --json # Output result as JSON\ntdc groups remove-user user1 user2 # Remove users from a group\ntdc groups remove-user id:123,id:456 # Comma-separated ID refs\n```\n\nAll group *writes* (`groups create`, `rename`, `delete`, `add-user`, `remove-user`) need the `workspaces:write` scope, which only `tdc auth login --full-access` grants. Group *reads* (`groups`, `groups view`) work on a default login.\n\n`tdc status set` and `tdc status clear` need the `user:write` scope, which only `tdc auth login --full-access` grants. `tdc status` (show) works on a default login.\n\n`tdc status set` replaces the fields this CLI supports: omitted emoji, expiration and pause flags clear those values, while other fields and effects are preserved.\n\nOnly pass `--pause-notifications` when the user asks for it. It holds back Comms notifications only for now: each app has to read the status and hold its own notifications back, and Todoist does not yet. Held notifications are not sent later.\n\nOnly pass `--pause-activity` when the user asks for it. It pauses their Todoist Karma and streaks while the status is active. It is independent of `--pause-notifications`: it does not hold back notifications, and pausing notifications does not protect Karma.\n\nIf a channel is not found in `tdc channels`, widen with broader listings such as `tdc channels --scope public`, then `tdc channels --scope public --state all`. Check `tdc channels --help` for other available filters.\n\n`tdc channel threads` covers the whole channel: it pages back through threads, newest-first by last activity, until it has enough for the requested page. `--since` and `--until` are applied server-side, `--unread` client-side. In `--json` / `--ndjson`, the response includes a `nextCursor` string (opaque) you can pass via `--cursor` to fetch the next page; NDJSON emits the cursor as a final `{ \"_meta\": true, \"nextCursor\": \"...\" }` line.\n\nFor `tdc channel members add/remove/set`, refs accept user identifiers (`id:N`, email, name) or `group:`, which expands to the group's current members. Group expansion is one-shot \u2014 it is not a persistent link, so users added to the group later will not auto-join the channel. `set` replaces membership with the resolved set and is dry-run by default (pass `--apply` to mutate); it refuses to remove the acting user unless `--include-self` is passed.\n\n## Reactions\n\n```bash\ntdc react thread \uD83D\uDC4D # Add reaction to thread\ntdc react comment +1 # Add reaction (shortcode)\ntdc react message heart # Add reaction to DM message\ntdc react thread \uD83D\uDC4D --json # Output result as JSON\ntdc unreact thread \uD83D\uDC4D # Remove reaction\ntdc unreact thread \uD83D\uDC4D --json # Output result as JSON\n```\n\nSupported shortcodes: +1, -1, heart, tada, smile, laughing, thinking, fire, check, x, eyes, pray, clap, rocket, wave\n\n## Shell Completions\n\n```bash\ntdc completion install # Install tab completions (prompts for shell)\ntdc completion install bash # Install for specific shell\ntdc completion install zsh\ntdc completion install fish\ntdc completion uninstall # Remove completions\n```\n\n### Diagnostics\n\n```bash\ntdc doctor # Run local + network diagnostics\ntdc doctor --offline # Skip Comms and npm network checks\ntdc doctor --json # JSON output with per-check results\n```\n\n### Configuration\n\n```bash\ntdc config view # Pretty-printed config, token masked, labels actual token source\ntdc config view --json # Raw JSON, token masked\ntdc config view --show-token # Include the full token\ntdc config set unarchive-new-threads true # Persist: always unarchive new threads so they land in your Inbox\ntdc config set unarchive-new-threads false # Persist: keep Comms's default (thread auto-archived for author)\n```\n\nUser preferences are stored under `userSettings` in the config file. Currently supported keys: `unarchive-new-threads`. The flag on `tdc thread create` (`--unarchive` / `--no-unarchive`) overrides this default per-invocation.\n\n### Update\n\n```bash\ntdc update # Update CLI to latest version\ntdc update --check # Check for updates without installing, show channel\ntdc update --check --json # Same, JSON envelope\ntdc update --check --ndjson # Same, newline-delimited JSON envelope\ntdc update --channel # Show current update channel\ntdc update switch --stable # Switch to stable release channel\ntdc update switch --pre-release # Switch to pre-release (next) channel\ntdc update switch --pre-release --json # Same, JSON envelope\ntdc update switch --pre-release --ndjson # Same, newline-delimited JSON envelope\n```\n\n### Changelog\n```bash\ntdc changelog # Show last 5 versions\ntdc changelog -n 3 # Show last 3 versions\ntdc changelog --count 10 # Show last 10 versions\n```\n\n## Migration\n\nTranslate old `twist.com` URLs to their Comms equivalents (e.g. for rewriting bookmarks or history). The migration endpoint authenticates with a **Twist** token (not a Comms one). Prefer the `TWIST_AUTH_TOKEN` environment variable \u2014 a CLI flag exposes the token in process listings. `--twist-token` is supported for ad-hoc use and overrides the env var. If the Twist CLI (`tw`) is installed, populate the env var inline with `TWIST_AUTH_TOKEN=\"$(tw auth token view)\"`.\n\n```bash\n# Comma-separated list as an argument (token from the environment)\nTWIST_AUTH_TOKEN=\"$(tw auth token view)\" tdc migrate urls \"https://twist.com/a/1/ch/2/t/3,https://twist.com/a/1/ch/2/t/4\"\n\n# Or pipe URLs in with --stdin (comma- or newline-separated)\ncat old-urls.txt | TWIST_AUTH_TOKEN=\"$(tw auth token view)\" tdc migrate urls --stdin\n\n# --twist-token overrides the env var (visible in process lists \u2014 prefer the env var)\ntdc migrate urls \"https://twist.com/a/1/ch/2/t/3\" --twist-token \n\ntdc migrate urls \"\" --json # Structured output ({ oldUrl, newUrl } / { oldUrl, error })\ntdc migrate urls \"\" --ndjson # Newline-delimited JSON\n```\n\nOutput is one line per URL in input order: `old -> new` on success, `old \u2717 ` on failure (`invalid_url` / `not_imported`, or `API_ERROR` when the endpoint gives no code). Per-URL failures don't abort the run; the command exits non-zero if any URL fails to migrate.\n\n## Global Options\n\n```bash\n--no-spinner # Disable loading animations\n--progress-jsonl # Machine-readable progress events (JSONL to stderr)\n--progress-jsonl= # Same, but write events to instead of stderr\n--progress-jsonl # Same as above (space-separated form also accepted)\n--accessible # Add text labels to color-coded output (also: TDC_ACCESSIBLE=1)\n--non-interactive # Disable interactive prompts (auto-detected when stdin is not a TTY)\n--interactive # Force interactive mode even when stdin is not a TTY\n```\n\n## Output Formats\n\nList and view commands commonly support `--json`, `--ndjson`, and `--full`. List commands with one clear entity ID also support `--ids-only`; check command help for the exact surface.\n\n```bash\n--json # Output as JSON\n--ndjson # Output as newline-delimited JSON (for streaming)\n--ids-only # Output one stable ID per line; mutually exclusive with JSON/NDJSON\n--full # Include all fields (default shows essential fields only)\n```\n\n## Dry Run\n\nMutating commands accept `--dry-run` to preview the operation without making the change. Where a command performs pre-flight validation (e.g. fetching the target thread to check channel access or ownership), those checks still run in dry-run \u2014 only the mutating write is skipped. Commands that have no pre-flight validation parse the reference and print the preview without hitting the API. The preview is structured:\n\n```\n[dry-run] Would :\n : \n ...\nRun without --dry-run to execute.\n```\n\n## Reference System\n\nCommands accept flexible references:\n- **IDs**: `id:` (or a bare ID when unambiguous). Workspace/user IDs are numeric; most Comms entity IDs are opaque strings.\n- **Comms URLs**: Full `https://comms.todoist.com/...` URLs (parsed automatically)\n- **Fuzzy names**: For workspaces/users/channels/groups - `\"My Workspace\"` or partial matches\n\n## Piping Input\n\nCommands that accept content (`thread create`, `thread reply`, `thread update`, `comment update`, `conversation reply`, `msg update`) read it from stdin only with `--stdin`; without the flag, piped input is ignored. `--stdin` can't be combined with a content argument, and with nothing piped in (stdin is a terminal) it fails with `STDIN_IS_TTY` instead of waiting:\n\n```bash\ncat notes.md | tdc thread reply --stdin\ntdc thread create \"Title\" --stdin < body.md\necho \"Quick reply\" | tdc conversation reply --stdin\n```\n\nIf neither a content argument nor `--stdin` is given, the CLI opens `$EDITOR` for interactive input. In non-TTY environments (e.g. when called by an agent or in a pipeline), the editor is automatically skipped and the command fails fast with an actionable error message. Use `--non-interactive` to force this behavior even in a TTY, or `--interactive` to override auto-detection.\n\n`tdc thread mark-read` and `tdc thread mark-unread` read thread refs from stdin with `--stdin`, one per line (`#` lines are skipped), added to any refs passed as arguments:\n\n```bash\nprintf \"id:CbT8n2Kp4Qx6Rz9Lm3Va\\nid:CbT9m4Qr7Vz2Nx8Lp5Sa\\n\" | tdc thread mark-read --stdin --yes\n```\n\n## Common Workflows\n\n**View by URL (auto-routes to the right command):**\n```bash\ntdc view https://comms.todoist.com/1585/ch/CbC8n2Kp4Qx6Rz9Lm3Va/t/CbT8n2Kp4Qx6Rz9Lm3Va # View thread\ntdc view https://comms.todoist.com/a/1585/ch/CbC8n2Kp4Qx6Rz9Lm3Va/t/CbT8n2Kp4Qx6Rz9Lm3Va # View thread\ntdc view https://comms.todoist.com/a/1585/ch/CbC8n2Kp4Qx6Rz9Lm3Va/t/CbT8n2Kp4Qx6Rz9Lm3Va/c/CbM8n2Kp4Qx6Rz9Lm3Va # View comment\ntdc view https://comms.todoist.com/a/1585/msg/CbV8n2Kp4Qx6Rz9Lm3Va # View conversation\ntdc view https://comms.todoist.com/a/1585/msg/CbV8n2Kp4Qx6Rz9Lm3Va/m/CbS8n2Kp4Qx6Rz9Lm3Va --json # View message as JSON\n```\n\n**Check inbox and respond:**\n```bash\ntdc inbox --unread --json\ntdc inbox --mentions --json # Unread threads with an unread @mention of you\ntdc thread view --unread\ntdc thread reply \"Thanks, I'll look into this.\"\ntdc thread done --yes\ntdc thread undone --yes # Changed your mind: back to the inbox\n```\n\n**Search and review:**\n```bash\ntdc mentions --since 2026-04-01 --all --json\ntdc search \"deployment\" --type threads --json\ntdc thread view \n```\n\n**Check DMs:**\n```bash\ntdc conversation unread --json\ntdc search \"Release team\" --type conversations --json # find a group chat by name\ntdc conversation list --kind group --json # find a group DM by participants\ntdc conversation view \ntdc conversation with \"Alice Example\"\ntdc conversation reply \"Got it, thanks!\"\n```\n"; export declare const SKILL_FILE_CONTENT: string; //# sourceMappingURL=content.d.ts.map