Repository navigation
Rename the server binary to tokamak-server - #249
Merged
Merged
Conversation
A checkout that pulled the rename but has not rebuilt has only the old executable on disk. stop and status failed there with ENOENT, so a running old server could not be found or stopped. They now fall back to the old name. start still needs the renamed build.
This was referenced Nov 20, 2026
JustKira
marked this pull request as draft
November 20, 2026 14:07
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
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.
Summary
Scripts, test helpers, help text, and docs use the new name. Server subcommands and local discovery through
server.jsonwork as before. The app name, storage paths, and environment variables stay the same.Linear: TKM-161
Evidence
dev, the Cargo binary target wastokamak.cargo build -p serverpassed;test -x target/debug/tokamak-server && test ! -e target/debug/tokamakpassed. The new binary printed a 64-character build ID and advertised the unchanged subcommands under its new name.bash .ci/check.sh lintbash .ci/check.sh tsbash .ci/check.sh rustcargo test -p serverproto run bun -- e2e/run.tscargo test -p tokamak-appcd app && proto run bun -- run tauri build --debug --no-sign --bundles appContents/MacOS/tokamak-serverand noContents/MacOS/tokamak.--build-id,--local-dir <temp> --plugins <bundle resources>)docker info --format '{{.ServerVersion}}'git grep -nI -P 'CARGO_BIN_EXE_tokamak(?!-server)|(?:target/[^\s"]*/|dist/|/bin/)tokamak(?!-server|-app)(?![\w-])|dist/tokamak-(?!server)|--bin(?:\s+|", ")tokamak(?![\w-])|\btokamak (?=(?:invite|members|revoke|plugin|--local-dir|--local-path)(?:\s|$))|(?:format!\(|ENTRYPOINT \[)"tokamak(?=[{"])|^name = "tokamak"$'No hits. A broader
git grep -nI -w tokamak -- ':!bun.lock'audit still includes the new hyphenated name, product and package identifiers, web and storage keys, Vite and lint helpers, repository URLs, and the Docker image, container, account, and resource paths. Those do not name the old server executable.Merge Danger
Door: Two-way.
Blast Radius: Packaging. External scripts invoking the standalone server by filename must switch to
tokamak-server. The desktop app can still replace an older local server through discovery.