[drakulavich]

Closes #146, closes #150.

What

• TOKEN_MISSING from sync and fetch names the token file with ~ (No Oura access token at ~/.oura-token.), through the same homePath that doctor uses. The multi-line token error (TOKEN_INVALID) names the file the same way. README's error table now shows the short form. (Token path: doctor prints ~/.oura-token, sync/fetch TOKEN_MISSING print the full home path #146)
• formatError colours the error: line only when stderr would take colour: shouldDisableColor applied to stderr's TTY state, so NO_COLOR, --no-color and FORCE_COLOR keep their meaning. Before this, chalk's level followed stdout alone. (Error colour follows stdout, not stderr: sync 2>err.log on a terminal writes ANSI into the file #150)

Why

Both reproduced on main:

• Without a token, sync printed No Oura access token at /Users/<name>/.oura-token. while doctor printed ~/.oura-token.
• script -q /dev/null bash -c 'oura-cli sync 2>err.log' (stdout a pty, stderr a file) left ^[[31merror: …^[[39m in err.log. After the fix the file holds plain text, and a pty on both streams is still red.

How checked

• New tests: src/api/client.test.ts (a token path under the home directory that does not exist; exact message) and src/lib/errors.test.ts (chalk forced on; exact text with colour false and true).
• Mutations, one per issue, each reverted after one run of the test file:
  • Token path: doctor prints ~/.oura-token, sync/fetch TOKEN_MISSING print the full home path #146: `No Oura access token at ${homePath(source)}.` → `No Oura access token at ${source}.` in client.ts: 1 of 35 fails (the new test).
  • Error colour follows stdout, not stderr: sync 2>err.log on a terminal writes ANSI into the file #150: const head = colour ? chalk.red(`error: ${message}`) : `error: ${message}`; → const head = chalk.red(`error: ${message}`); in errors.ts: 1 of 18 fails (the new test).
• bun run check: typecheck, Biome, Knip clean; 713 tests pass.
• Codex review: Approve, no findings (report in the first comment).

🤖 Generated with Claude Code

https://claude.ai/code/session_018qh9xqviBHYmzVtmQWSKqA

[drakulavich]

Codex review (gpt-6-luna, final, ebcf1cc..122d2c7):

Reviewed origin/main...HEAD across the six files in scope. The token messages use the existing display-only homePath helper, and JSON errors return before applying color. No Required or Optional findings.

The two touched test files passed: 53 tests, 0 failures. git diff --check was clean. The pre-existing assets/demo.gif working-tree change was left untouched.

Simplification: not needed

Verdict: Approve

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge, with one non-blocking test gap from the previous review.

Findings

1.  Stderr choice stays untested ▶

Summary

The PR shortens home-directory token paths in errors and prevents colour codes in redirected stderr.

• Token errors shorten home-folder paths to ~.
• Text errors color their heading based on stderr.

_{Reviews (2) · Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." · Reviewed by Greptile}

[greptile-apps]

Stderr choice stays untested

Both calls pass colour explicitly, so neither checks the stderr-based default that fixes #150. Changing process.stderr.isTTY back to process.stdout.isTTY would leave this test passing. Add a test with different stdout and stderr TTY states, and omit the fourth argument.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!