Skip to content

feat(cli): add /upgrade and /privacy-settings slash commands#161

Merged
oratis merged 1 commit into
mainfrom
feat/cli-upgrade-privacy
Jun 4, 2026
Merged

feat(cli): add /upgrade and /privacy-settings slash commands#161
oratis merged 1 commit into
mainfrom
feat/cli-upgrade-privacy

Conversation

@oratis
Copy link
Copy Markdown
Owner

@oratis oratis commented Jun 4, 2026

Two Claude-Code parity slash commands (both were 🔄 in BEHAVIOR_PARITY.md):

  • /upgrade — prints the current version (core VERSION) + npm i -g deepcode-cli@latest (mirrors the deepcode upgrade subcommand; notes the macOS app auto-updates).
  • /privacy-settings — read-only summary of where data lives (credentials at chmod 600 or an OS keychain, local sessions/snapshots) and what's sent to the DeepSeek API. Grounded in docs/security-model.md — no invented claims.

Tests: parity-commands.test.ts +2 (version + update line; data locations + DeepSeek endpoint + security-model ref). cli 137, typecheck clean, repo-wide format:check clean. Flips the /upgrade + /privacy-settings rows → ✅.

🤖 Generated with Claude Code

Two more Claude-Code parity slash commands (both 🔄 in BEHAVIOR_PARITY):
- /upgrade — prints the current version (core VERSION) + the update command
  `npm i -g deepcode-cli@latest` (mirrors the `deepcode upgrade` subcommand;
  notes the macOS app auto-updates).
- /privacy-settings — read-only summary of where data lives (creds at 0600 or
  OS keychain, local sessions/snapshots) and what's sent to the DeepSeek API.
  Grounded in docs/security-model.md — no invented privacy claims.

Tests in parity-commands.test.ts (2 cases). cli 137. Flips both rows → ✅.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@oratis oratis merged commit c0cc681 into main Jun 4, 2026
3 checks passed
@oratis oratis deleted the feat/cli-upgrade-privacy branch June 4, 2026 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant