fix(site): the CLI is its own install, not a PATH workaround - #258
Merged
Conversation
The macOS tab ended on `ln -sf ~/.cix/runtime/current/cix /usr/local/bin/cix`, which put a symlink trick inside the one route whose whole point is that it needs no terminal. Installing the app IS the macOS install: the server runs, the account exists, both halves keep themselves updated. The `cix` command is a separate thing and the same on every platform, so it becomes the first of the shared steps instead — install.sh, once, on whichever machine you search from. It needs no configuration after the app either, because first run already wrote ~/.cix/config.yaml with the server and an API key. The detail is not duplicated here: the dashboard's home page carries the full version (ConnectClaudeCode.tsx — four steps with a connect command derived from that deployment's own host), and it cannot go stale the way a copy on this site would, so the step points at it. The `cix config show` output in the block is transcribed from a real run rather than invented, and the install line now carries CLI_VERSION. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #255.
The macOS tab ended on a
ln -sf ~/.cix/runtime/current/cix /usr/local/bin/cixstep — a symlink trick inside the one route whose whole point is that it needs no terminal. Installing the app is the macOS install: the server runs, the account exists, and both halves keep themselves updated. That tab now ends there, with a closing line instead of a fourth "step".The
cixcommand is a separate install and identical on every platform, so it becomes the first shared step —install.sh, once, on whichever machine you search from. After the macOS app it needs no configuration either: first run already wrote~/.cix/config.yamlwith the server and an API key.The detail is deliberately not duplicated on the site. The dashboard's home page already carries the full version —
ConnectClaudeCode.tsx, four steps with a connect command derived from that deployment's own host — and it cannot drift the way a copy here would, so the step points at it.Also: the
cix config showoutput in that block is transcribed from a real run instead of invented (servers (1):/* local url=… key=(set)), and the install line carriesCLI_VERSION.Verified
npm run buildclean; forbidden-claims check passesdist/served with the production CSP from_headers: renders, no violations🤖 Generated with Claude Code