Overview - Intent

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
perf-hooks-local-cli
35a722f3 docs: move the hooks reference update to the docs PR
by Sarah Gerrard
Succeeded
perf-hooks-local-cli
420d8f56 fix: derive the suggested load shim from the resolved local install The catalog could be built from @tanstack/intent resolved in a parent node_modules while the suggested load command pointed at a nearer, unrelated .bin/intent shim. resolveLocalIntentCli now returns the node_modules directory it found the package in, and the shim is looked up there only; without one the runner command is suggested. Docs and changeset state that condition. Tests cover a nested workspace with a stray shim and a local install without a shim.
by Sarah Gerrard
Succeeded
perf-hooks-local-cli
7d3ba987 perf: run the locally installed CLI from agent hooks The session-start hook built its skill catalog by running the package-manager runner (`npx @tanstack/intent@latest list ...`, or the pnpm/yarn/bun equivalent) through a shell. npx resolves the `latest` tag against the registry on every invocation, so each session start cost one to four seconds before the CLI even started (~1.4s even with `--offline`), and the same runner was suggested to the agent for every `load`. The generated runner now resolves `@tanstack/intent` from the project's node_modules (walking up from the event cwd), and when found executes its bin with the current Node binary and no shell. It falls back to the package-manager runner only when there is no local install. The catalog suggests `node_modules/.bin/intent load <package>#<skill>` when that shim exists, and the invocation parser accepts a path-prefixed `intent` so the edit gate recognizes it. An empty event cwd now falls back to process.cwd() instead of being passed to spawn. Measured on a project with 6 intent-enabled packages: session-start hook 300ms with the local CLI versus 600ms-3.8s through npx.
by Sarah Gerrard
Failed
perf-hooks-local-cli
0f1302ec perf: run the locally installed CLI from agent hooks The session-start hook built its skill catalog by running the package-manager runner (`npx @tanstack/intent@latest list ...`, or the pnpm/yarn/bun equivalent) through a shell. npx resolves the `latest` tag against the registry on every invocation, so each session start cost one to four seconds before the CLI even started (~1.4s even with `--offline`), and the same runner was suggested to the agent for every `load`. The generated runner now resolves `@tanstack/intent` from the project's node_modules (walking up from the event cwd), and when found executes its bin with the current Node binary and no shell. It falls back to the package-manager runner only when there is no local install. The catalog suggests `node_modules/.bin/intent load <package>#<skill>` when that shim exists, and the invocation parser accepts a path-prefixed `intent` so the edit gate recognizes it. An empty event cwd now falls back to process.cwd() instead of being passed to spawn. Measured on a project with 6 intent-enabled packages: session-start hook 300ms with the local CLI versus 600ms-3.8s through npx.
by Sarah Gerrard