mirror of
https://github.com/hanzoai/dev.git
synced 2026-10-25 03:32:32 +00:00
zeekayandHanzo Dev
d3d1dfa1d3
hanzoai/dev went public defaulting to someone else's cloud. Four things were
wrong, and all four now have a test that fails if they come back.
DEFAULT PROVIDER AND MODEL. built_in_model_providers() gains `hanzo` -- the
Hanzo Cloud at api.hanzo.ai/v1, Responses wire, bearer from HANZO_USER_KEY --
and it is the default. The default model is zen5-coder. This was not cosmetic:
the old default is not in the gateway catalog, so it 400s against our own
cloud. Measured, not assumed:
POST api.hanzo.ai/v1/responses model=gpt-5-codex -> 400 "model is not
available. Use GET /v1/models to list available models"
POST api.hanzo.ai/v1/responses model=zen5-coder -> 200, clean output
Our own CLI already documented the bug from the other side -- dev.rs says
"Name the model too -- codex's built-in default is not in the gateway catalog
and would 400" and passes `-c model=` on every launch to work around it. It
also asserts that on the native gateway NO model_provider override is needed,
which is only true once `hanzo` is the built-in default. It is now.
zen5-coder over enso because dev is a coding agent and because enso returns
system-prompt text on the Responses wire that dev actually speaks; zen5-coder
returns the answer. Model ids were read from GET /v1/models with a bearer, not
guessed. Other providers stay fully configurable -- this is the default, not
the only choice.
THE LOGIN COMMAND. Messages said `code login` / `codex login`. The real command
is `hanzo auth login` (`hanzo login` is not a command -- it is swallowed as an
AI task). It now lives once, as auth::LOGIN_COMMAND, so no message can drift
into naming a command that does not exist. References to this binary's own
subcommand became `dev login`.
A BINARY NAMED dev. HEAD built `code` and `codex` and nothing named `dev`, so a
release cut today would ship no `dev` -- and `hanzo code` launches a bare `dev`
off PATH, so every new install would break. `dev` is now the canonical bin,
declared first; `code` remains as an alias to the same program, never the
reverse. The CLI identifies as `dev` / "Hanzo Dev", not "OpenAI Codex".
OUR NAMESPACES. The pipeline published to @just-every/* on npm and pushed
formulae to just-every/homebrew-tap. Both of ours already exist and are already
populated at v0.6.91 -- @hanzo/dev plus all five @hanzo/dev-<target> packages,
and hanzoai/homebrew-tap's Formula/hanzo-dev.rb, which installs `dev` and
expects assets named dev-<triple>. Nothing here is squatted; this is our own
distribution, reclaimed. Assets are renamed to match the formula.
Two live supply-chain bugs fell out of that, both worse than a naming problem:
postinstall.js (runs on every npm install) and the tui auto-updater fetched
from a third party's releases -- the updater also told our users to
`npm install -g @just-every/code@latest`. Worse, a shadowed `isWSL` const put
the two fast paths in the temporal dead zone, so their catch blocks swallowed
the error and EVERY install fell through to that download: the five published
platform packages were never used, and the third-party fetch was not an edge
case but the only path that ran. Fixed and exercised in a sandbox across all
three paths. codex-cli/.pack/ -- a committed `npm pack` artifact CI
regenerates, and the reason the bad URL had two homes -- is now untracked.
DURABILITY, because upstream-merge.yml merges openai/codex every 30 minutes.
A one-time edit to a default is a suggestion that survives until the next
merge. Two mechanisms:
- .github/merge-policy.json prefer_ours_globs listed only codex-rs/** while
the workspace that SHIPS is code-rs/**, so it protected nothing that
ships. The identity-bearing code-rs files are now listed.
- code-rs/core/tests/hanzo_identity.rs asserts all four properties -- the
provider, a Zen default, a bin named dev, and no third-party publish
target. Upstream has no such file, so a merge cannot conflict with it or
carry the guard away with the thing it guards. Policy can be edited;
a red build cannot be ignored.
The gate is not decorative: it failed on the un-retargeted pipeline
("release.yml still references `@just-every/`") and went green only when the
pipeline was actually fixed.
Verified: cargo build --bin dev clean; hanzo_identity 4/4; code-core lib
332 passed, 1 failed -- git_info::test_collect_git_info_with_remote, which
fails identically on a clean origin/main checkout here because this machine
has a global [email protected]:.insteadof rewrite. Pre-existing and
environmental, not from this change.
$ dev exec "say OK" # fresh profile, no config
Hanzo Dev v0.0.0
model: zen5-coder
provider: hanzo
Co-authored-by: Hanzo Dev <[email protected]>
70 lines
2.6 KiB
JavaScript
70 lines
2.6 KiB
JavaScript
#!/usr/bin/env node
|
|
// Windows-friendly preinstall: proactively free file locks from prior installs
|
|
// so npm/yarn/pnpm can stage the new package. No-ops on non-Windows.
|
|
|
|
import { platform } from 'os';
|
|
import { execSync } from 'child_process';
|
|
import { existsSync, readdirSync, rmSync, readFileSync, statSync } from 'fs';
|
|
import path from 'path';
|
|
import { fileURLToPath } from 'url';
|
|
|
|
function isWSL() {
|
|
if (platform() !== 'linux') return false;
|
|
try {
|
|
const rel = readFileSync('/proc/version', 'utf8').toLowerCase();
|
|
return rel.includes('microsoft') || !!process.env.WSL_DISTRO_NAME;
|
|
} catch { return false; }
|
|
}
|
|
|
|
const isWin = platform() === 'win32';
|
|
const wsl = isWSL();
|
|
const isWinLike = isWin || wsl;
|
|
|
|
// Scope: only run for global installs, unless explicitly forced. Allow opt-out.
|
|
const isGlobal = process.env.npm_config_global === 'true';
|
|
const force = process.env.CODE_FORCE_PREINSTALL === '1';
|
|
const skip = process.env.CODE_SKIP_PREINSTALL === '1';
|
|
if (!isWinLike || skip || (!isGlobal && !force)) process.exit(0);
|
|
|
|
function tryExec(cmd, opts = {}) {
|
|
try { execSync(cmd, { stdio: ['ignore', 'ignore', 'ignore'], shell: true, ...opts }); } catch { /* ignore */ }
|
|
}
|
|
|
|
// 1) Stop our native binary if it is holding locks. Avoid killing unrelated tools.
|
|
// Only available on native Windows; skip entirely on WSL to avoid noise.
|
|
if (isWin) {
|
|
tryExec('taskkill /IM dev-x86_64-pc-windows-msvc.exe /F');
|
|
}
|
|
|
|
// 2) Remove stale staging dirs from previous failed installs under the global
|
|
// @hanzo scope, which npm will reuse (e.g., .dev-XXXXX). Remove only
|
|
// old entries and never the current staging or live package.
|
|
try {
|
|
let scopeDir = '';
|
|
try {
|
|
const root = execSync('npm root -g', { stdio: ['ignore', 'pipe', 'ignore'], shell: true }).toString().trim();
|
|
scopeDir = path.join(root, '@hanzo');
|
|
} catch {
|
|
// Fall back to guessing from this script location: <staging>\..\..\
|
|
const here = path.resolve(path.dirname(fileURLToPath(import.meta.url)));
|
|
scopeDir = path.resolve(here, '..');
|
|
}
|
|
if (existsSync(scopeDir)) {
|
|
const now = Date.now();
|
|
const maxAgeMs = 2 * 60 * 60 * 1000; // 2 hours
|
|
const currentDir = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..');
|
|
for (const name of readdirSync(scopeDir)) {
|
|
if (!name.startsWith('.dev-')) continue;
|
|
const p = path.join(scopeDir, name);
|
|
if (path.resolve(p) === currentDir) continue; // never remove our current dir
|
|
try {
|
|
const st = statSync(p);
|
|
const age = now - st.mtimeMs;
|
|
if (age > maxAgeMs) rmSync(p, { recursive: true, force: true });
|
|
} catch { /* ignore */ }
|
|
}
|
|
}
|
|
} catch { /* ignore */ }
|
|
|
|
process.exit(0);
|