Manage Taskboard

This skill serves the local-first Codex Taskboard product, including its configured LAN and cloud services.

Apply the workflow below only to work explicitly targeting Codex Taskboard or already established as belonging to it in the conversation. An issue identifier, repository, or generic request to manage tasks, sync status, or add comments does not establish that scope. For GitHub, Phabricator, or another external tracker, use that system's tools and workflow; do not query, claim, or mirror its issues in Taskboard unless the user asks for that board operation. When the target is unclear, clarify it before running taskctl.

Within that scope, use taskctl for every project, issue, relation, and comment operation. Consume its JSON output. Use the exact issue identifier returned by the taskboard or supplied in the prompt. Never assume, derive, or rewrite an identifier prefix.

Open only the relevant section of references/cli.md when command syntax is needed.

Select the CLI and active service

• Use the exact taskctl binary and Taskboard URL supplied by the task or injected runtime. Do not replace them with a global CLI, the default port, or another board.
• On Windows, when no binary is injected and the desktop app is installed, use & "$env:LOCALAPPDATA\Codex Taskboard\bin\taskctl.cmd" issue get ID --json in PowerShell. The packaged wrapper reads the active launcher runtime. If this packaged path is absent, stop and ask for the exact installed taskctl.cmd path; do not switch to a global CLI or guess the service URL.
• On macOS, when no binary is injected and the desktop app is installed, use '/Applications/Codex Taskboard.app/Contents/Resources/bin/taskctl' issue get ID --json. Keep the single quotes because the path contains a space. The packaged wrapper reads the active launcher runtime; do not search the filesystem for another CLI or reconstruct the tokenized URL.
• On Linux, when no binary is injected and Codex was started by the desktop app, use taskctl issue get ID --json. The desktop app adds its packaged wrapper to the managed Codex PATH; do not search the filesystem for another CLI or reconstruct the tokenized URL.
• If that exact command reaches a sandbox restriction on the loopback service, retry the same command with the required permission. Do not switch binaries or endpoints.

Terminology: local companion