You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 11bfb29
Browse filesBrowse the repository at this point in the historyBrowse files
fix(install): expose altimate-code from the standalone installers (#1562)
* fix(install): expose `altimate-code` from the standalone installers
curl and PowerShell installs now put altimate-code next to altimate, as
npm, Homebrew and AUR do: a relative symlink, or on Windows a .cmd plus a
Git Bash shim that stays inert under WSL. Re-running the installer adds it.
The uninstall hint names these files.
Closes#1563
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(install): link the alias for a plain `altimate` --binary under Git Bash
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
The standalone install drops a single self-contained binary named `altimate`. The npm install exposes both `altimate` and `altimate-code` on PATH; the standalone install only exposes`altimate`. Alpine Linux (musl) and Windows on ARM64 are not currently supported by the standalone binary — use `apk add gcompat` on Alpine, or use WSL on Windows-on-ARM.
45
+
The standalone install drops a single self-contained binary named `altimate`, plus an `altimate-code` alias for it — the same two names the npm install exposes. On Windows that alias is an `altimate-code.cmd` shim, which passes its arguments through `cmd.exe` (`%VAR%` expands, unquoted `&``|``^` are interpreted), so scripts should call`altimate`. Alpine Linux (musl) and Windows on ARM64 are not currently supported by the standalone binary — use `apk add gcompat` on Alpine, or use WSL on Windows-on-ARM.
46
46
47
47
For GitHub, [install the Altimate Code App](https://github.com/apps/altimate-code-agent/installations/new)
48
48
to select repositories for interactive agent tasks. Automatic dbt pull-request
Copy file name to clipboardExpand all lines: docs/docs/reference/troubleshooting.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ description: "Fix common Altimate Code installation and runtime issues including
10
10
11
11
**Symptoms:**`altimate-code: command not found` after running `curl -fsSL https://www.altimate.sh/install | bash`.
12
12
13
-
As of v0.7.1 the curl-installed binary is named `altimate`, not `altimate-code`. The npm package continues to ship both names. If you scripted against the curl install:
13
+
As of v0.7.1 the curl-installed binary is named `altimate`, and curl installs from v0.7.1 until the `altimate-code` alias was added put only that name on PATH (v0.7.0 and earlier installed `altimate-code` under `~/.altimate-code/bin` instead). Re-run the installer — it adds `altimate-code` next to `altimate` in `~/.altimate/bin` — or call `altimate` directly:
14
14
15
15
```bash
16
16
# Before (v0.7.0 and earlier curl install):
@@ -20,8 +20,6 @@ As of v0.7.1 the curl-installed binary is named `altimate`, not `altimate-code`.
20
20
~/.altimate/bin/altimate run "..."
21
21
```
22
22
23
-
Or stay on the `altimate-code` name by installing via npm: `npm install -g altimate-code`.
print_message warning "${MUTED}Could not remove ${NC}$exe${MUTED}, which shadows the altimate-code.cmd alias${NC}"
520
+
fi
521
+
write_shim altimate-code '#!/bin/sh\ncase "$(uname -s)" in\n MINGW*|MSYS*|CYGWIN*) exec "$(dirname "$0")/altimate.exe" "$@" ;;\nesac\necho "altimate-code: this is the Windows build; it runs only from Git Bash, MSYS or Cygwin" >&2\nexit 127\n'||return 0
522
+
}
523
+
524
+
# Writes printf format $2 to $INSTALL_DIR/$1 as an executable file (Cygwin keeps
525
+
# POSIX modes, so the sh shim needs the bit), replacing a file or link there
526
+
# instead of writing through it. A real directory is left alone.
527
+
write_shim() {
528
+
local path="${INSTALL_DIR}/$1"
529
+
if [ -d"$path" ] && [ !-L"$path" ];then
530
+
print_message warning "${MUTED}Skipped the ${NC}$1${MUTED} alias: ${NC}$path${MUTED} is a directory${NC}"
0 commit comments