Sidekick v1.1.0
Highlights
- Added a full local Sidekick deployment that MCP clients can launch directly through
npxand stdio, without requiring a dedicated server. - Preserved the existing dedicated/server deployment as a first-class topology.
- Reused the canonical MCP registration, governed dispatcher, validation, policy, approvals, execution context, redaction, auditing, and capability-pack paths.
- Added durable platform-aware local persistence outside npm/npx caches, including support for
SIDEKICK_HOME. - Added safe first-run initialization and local stdio integration coverage.
- Added package executable metadata for the
sidekickCLI and clean packaged-install testing. - Documented local and dedicated topologies, persistence, security, client configuration, Compute, capability packs, and pinned GitHub Release usage.
Verification
- Local stdio MCP integration passed.
- Clean npm package installation and stdio integration passed.
- MCP session and tool-registry regressions passed.
- Focused security, Compute, and capability-pack suites passed.
npm audit --omit=dev: 0 vulnerabilities.- Deployment verified healthy on merged main commit
e76d87fc352ee73194ae73f6aa53a8093c18c744.
Installation
For a pinned release:
{
"mcpServers": {
"sidekick": {
"command": "npx",
"args": ["-y", "github:geoffmcc/sidekick#v1.1.0"]
}
}
}This release is the same Sidekick product available through the dedicated/server deployment; local execution is an alternative deployment topology, not a reduced edition.