Skip to content

Sidecar defaults to the latest stackql release (crate 0.2.0); re-pin to v0.10.601 #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jeffreyaven wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Sidecar defaults to the latest stackql release (crate 0.2.0); re-pin to v0.10.601 #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
37ce849
Add stackql-agent demo + self-healing bundle cache; talk kit
jeffreyaven Jun 17, 2026
f53e469
demo updates
jeffreyaven Jun 17, 2026
b4a88cc
Bump pinned stackql release to v0.10.601; crate 0.1.1
jeffreyaven Aug 18, 2026
b0f4847
Sidecar defaults to the latest stackql release; crate 0.2.0
jeffreyaven Aug 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 11 additions & 6 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,10 @@ stance.

Two acquisition modes, both behind one API:

1. Sidecar (default feature): download the platform's .mcpb at first run,
verify sha256 against pins baked into the crate, cache, spawn over stdio
1. Sidecar (default feature): resolve the latest stackql release, download
the platform's .mcpb at first run, verify sha256 against the release's
.sha256 asset (or the pins baked into the crate for
BundleVersion::Pinned), cache, spawn over stdio
2. Vendored (`vendored` feature): caller embeds the binary with
`include_bytes!` (we provide the macro/helper + extract-on-first-run) -
the single-shippable-binary story for compiled agent apps
Expand All @@ -27,17 +29,20 @@ justify anything beyond that.

Source of truth: stackql/stackql-mcpb-packaging (the packaging repo).

- Per-version sha256 pins from the release .sha256 assets (a consolidated
platforms.json release asset is planned - prefer it once present); pins
are baked at crate build/render time like npm's platforms.json
- Default release is latest: resolved at start-up from
github.com/stackql/stackql/releases/latest and verified against that
release's .sha256 asset (a consolidated platforms.json release asset is
planned - prefer it once present). Per-version sha256 pins are still
baked into the crate for BundleVersion::Pinned and as the offline
fallback; STACKQL_MCP_VERSION=latest|pinned|<version> overrides
- Canonical launch args (cwd-independence mandatory):
`mcp --mcp.server.type=stdio --approot <home>/.stackql
--mcp.config {"server": {"mode": "<mode>", "audit": {"disabled": true}}}`
- Default `read_only`; escalation is explicit caller opt-in
- Shared binary cache: `~/.stackql/mcp-server-bin/<version>/<platform-key>/`
(same as npm/pypi wrappers - check before downloading)
- Platform keys: linux-x64, linux-arm64, windows-x64, darwin-universal
- Env overrides honored: STACKQL_MCP_BIN, STACKQL_MCP_BUNDLE
- Env overrides honored: STACKQL_MCP_BIN, STACKQL_MCP_BUNDLE, STACKQL_MCP_VERSION
- Conformance: packaging repo's scripts/smoke-test.py --cmd must pass
against the crate's example launcher; port the same checks to Rust tests

Expand Down
Loading