create-snipara 2.2.0 → 2.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +19 -3
- package/dist/index.js +2 -2
- package/dist/managed-toolchain.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,11 +1,27 @@
|
|
|
1
1
|
# create-snipara
|
|
2
2
|
|
|
3
|
-
**
|
|
3
|
+
**Set up local coding work or connect your project to Snipara context.**
|
|
4
4
|
|
|
5
5
|
`create-snipara` connects a local project to Snipara so AI agents can start
|
|
6
6
|
with project-owned context, reviewed memory, shared guidance, and optional code
|
|
7
7
|
impact tooling instead of starting cold every session.
|
|
8
8
|
|
|
9
|
+
## Choose your first step
|
|
10
|
+
|
|
11
|
+
| Goal | Command | Requirements |
|
|
12
|
+
| --- | --- | --- |
|
|
13
|
+
| Track and verify local coding work | `npx create-snipara@latest init --profile local-work --client codex` | Supported Node.js and Python; no Snipara account |
|
|
14
|
+
| Connect sourced project context | `npx create-snipara@latest` | Authorized Snipara project connection |
|
|
15
|
+
| Connect an existing self-hosted server | Use `--self-hosted` with its endpoint | Running server and operator credentials |
|
|
16
|
+
|
|
17
|
+
Use `--client claude-code` for Claude Code. Local work prepares compatible
|
|
18
|
+
Companion, Orchestrator and Sandbox tools. It does not install Docker or
|
|
19
|
+
dependency images, run tests or call a model. Hosted context is optional for
|
|
20
|
+
local work; add `--connect-context` when you want to set it up explicitly.
|
|
21
|
+
See [install profiles](#install-profiles) for the full contract.
|
|
22
|
+
|
|
23
|
+
## Connect project context
|
|
24
|
+
|
|
9
25
|
The shortest path is three moments: connect the folder your agent already uses,
|
|
10
26
|
let Snipara index its project context, then ask one question that only the
|
|
11
27
|
project can answer.
|
|
@@ -24,7 +40,7 @@ npx create-snipara@latest --self-hosted \
|
|
|
24
40
|
--client claude-code
|
|
25
41
|
```
|
|
26
42
|
|
|
27
|
-
Both modes aim to finish with the same visible proof:
|
|
43
|
+
Both context connection modes aim to finish with the same visible proof:
|
|
28
44
|
|
|
29
45
|
```text
|
|
30
46
|
✓ Endpoint connected
|
|
@@ -36,7 +52,7 @@ Both modes aim to finish with the same visible proof:
|
|
|
36
52
|
`create-snipara` is the single activation engine for the agent path. It detects
|
|
37
53
|
or asks where Snipara should run, writes the right MCP config, seeds a small
|
|
38
54
|
README/docs corpus, and automatically verifies a first project-grounded answer.
|
|
39
|
-
The default path is Cloud
|
|
55
|
+
The default context path is Cloud; the same
|
|
40
56
|
flow works with an existing self-hosted Snipara Server.
|
|
41
57
|
It is also the canonical activation engine behind editor setup docs: VS Code can
|
|
42
58
|
surface activation as a native command, Cursor can pair OpenVSX UI with Hosted
|
package/dist/index.js
CHANGED
|
@@ -14,7 +14,7 @@ import { homedir as homedir2 } from "os";
|
|
|
14
14
|
// package.json
|
|
15
15
|
var package_default = {
|
|
16
16
|
name: "create-snipara",
|
|
17
|
-
version: "2.2.
|
|
17
|
+
version: "2.2.1",
|
|
18
18
|
description: "Onboard Snipara Cloud or self-hosted MCP with an automatic project-grounded proof of value",
|
|
19
19
|
main: "dist/index.js",
|
|
20
20
|
type: "module",
|
|
@@ -219,7 +219,7 @@ function parseManagedToolchainManifest(value) {
|
|
|
219
219
|
|
|
220
220
|
// src/managed-versions.json
|
|
221
221
|
var managed_versions_default = {
|
|
222
|
-
companion: "4.2.
|
|
222
|
+
companion: "4.2.1",
|
|
223
223
|
orchestrator: "1.16.0",
|
|
224
224
|
sandbox: "3.0.0"
|
|
225
225
|
};
|