clickup-connectlisted

# ClickUp Connect — Discover Once, Write It Down An agent that can read your task board closes the loop: work items, code, servers, and review all become visible from one session. But an agent rediscovering list IDs on every invocation spends its context on lookups. So do it once, and have it **write its own reference file**. That file — not the chat — is what the next session reads. The shape here transfers to Jira, Linear, Asana, or GitHub Projects unchanged: token → verify → discover the hierarchy → write notes → record the quirks → document the refresh. Only the endpoints differ. --- ## STEP 1: TOKEN — gitignore first, then write it Order matters. Ignore the file *before* it contains a secret. ```bash mkdir -p <workspace>/task-board && cd <workspace>/task-board printf '.env\n*.local\n' > .gitignore git check-ignore -v .env || echo "NOT IGNORED — stop" printf 'CLICKUP_API_TOKEN=<paste token>\n' > .env chmod 600 .env ``` Use a **Personal API Token** (ClickUp: Settings → Apps → API Token). Note the quirk: the header is `Authorization: <token>` with **no `Bearer` prefix**. Sending `Bearer` fails with an auth error that reads like a bad token, which is a good half hour if you don't know. The token carries the permissions of the human who issued it. It is not scoped down. Treat it accordingly: gitignored, `chmod 600`, never pasted into an issue, rotated when a project ends. --- ## STEP 2: VERIFY ```bash set -a; source .env; set +a curl -s -H "Authorization: $CLICKU