Skip to content

fix: allow channel threads with read-only tokens - #85

Merged
nats12 merged 1 commit into
mainfrom
codex/fix-read-only-channel-threads
Oct 20, 2026
Merged

nats12 merged 1 commit into
mainfrom
codex/fix-read-only-channel-threads

Conversation

@nats12

@nats12 nats12 commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Treat threads.getThreads as a read operation so tdc channel threads works with read-only OAuth tokens.

Reproduction

From the PR branch, run the following with a staging account. The channel and workspace IDs shown are from the recorded run; substitute IDs your account can access if needed.

npm ci
npm run build
export COMMS_BASE_URL=https://comms.staging.todoist.com
node dist/index.js auth login --read-only
node dist/index.js channel threads id:CfXLoRoEbMQKH6naSt8h9 4170 --json
  • JSON is returned with a results array
  • There is no READ_ONLY error.

Account effects: auth login --read-only may add a read-only Comms CLI authorization to the staging account and replaces the locally active CLI token. channel threads only reads data and does not change Comms content. The build commands affect local files only.

Recordings

Before — read-only token returns READ_ONLY:

before.mp4

After — the same command returns threads:

after.mp4

Verification

  • npm run build
  • npm test — 973 passed
  • npm run type-check
  • npm run lint:check
  • npm run check:skill-sync

Fixes #51.

@nats12
nats12 requested a review from doistbot October 19, 2026 13:53

@doistbot doistbot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR updates fix: allow channel threads with read-only tokens. No issues were flagged in the reviewed diff.

Share Feedback • Review Logs

@nats12
nats12 marked this pull request as ready for review October 19, 2026 14:06
@nats12
nats12 requested review from a team and scottlovegrove and removed request for a team October 19, 2026 14:06
Comment thread artifacts/issue-51/after.mp4 Outdated
@nats12
nats12 force-pushed the codex/fix-read-only-channel-threads branch from ed1463a to 2547c30 Compare October 20, 2026 10:26
@nats12
nats12 merged commit 0c5d928 into main Oct 20, 2026
8 checks passed
@nats12
nats12 deleted the codex/fix-read-only-channel-threads branch October 20, 2026 10:32
doist-release-bot Bot added a commit that referenced this pull request Oct 20, 2026
## [3.6.4](v3.6.3...v3.6.4) (2026-10-20)

### Bug Fixes

* allow channel thread listing with read-only tokens ([#85](#85)) ([0c5d928](0c5d928))
@doist-release-bot

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 3.6.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tdc channel threads fails with READ_ONLY for a read-only token, while sibling read commands succeed

3 participants