@synapsor/runner 0.1.0-alpha.6 → 0.1.0-alpha.7
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 +21 -0
- package/dist/runner.mjs +3 -3
- package/docs/mcp-client-setup.md +34 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -181,6 +181,27 @@ examples/openai-agents-http/
|
|
|
181
181
|
Use `--mode review` only when you are ready to create proposal tools and test
|
|
182
182
|
guarded writeback with a separate trusted write credential.
|
|
183
183
|
|
|
184
|
+
## Sanity Check The Agent Connection
|
|
185
|
+
|
|
186
|
+
Before asking an agent to solve a real task, confirm it can call a Runner tool:
|
|
187
|
+
|
|
188
|
+
```bash
|
|
189
|
+
synapsor-runner tools preview --config ./synapsor.runner.json --store ./.synapsor/local.db
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
Then ask the agent:
|
|
193
|
+
|
|
194
|
+
```text
|
|
195
|
+
Use the Synapsor Runner MCP tool to inspect invoice INV-3001.
|
|
196
|
+
Do not answer from memory.
|
|
197
|
+
Return the tool name called, the evidence handle, and whether raw SQL was available.
|
|
198
|
+
```
|
|
199
|
+
|
|
200
|
+
Expected result: the agent calls a semantic tool, returns an evidence handle or
|
|
201
|
+
local ledger reference, and says raw SQL/write/approval tools were not
|
|
202
|
+
available. If it gives generic advice or unrelated prose without a tool call,
|
|
203
|
+
Runner is not connected yet.
|
|
204
|
+
|
|
184
205
|
The disposable reference app includes proposal-first write examples for:
|
|
185
206
|
|
|
186
207
|
- `billing.propose_late_fee_waiver`
|
package/dist/runner.mjs
CHANGED
|
@@ -2685,7 +2685,7 @@ function createMcpRuntime(config, options = {}) {
|
|
|
2685
2685
|
}
|
|
2686
2686
|
function createSynapsorMcpServer(runtime) {
|
|
2687
2687
|
const server = new McpServer(
|
|
2688
|
-
{ name: "synapsor-runner", version: "0.1.0-alpha.
|
|
2688
|
+
{ name: "synapsor-runner", version: "0.1.0-alpha.7" },
|
|
2689
2689
|
{ capabilities: { tools: {}, resources: {} } }
|
|
2690
2690
|
);
|
|
2691
2691
|
if (runtime.config.mode === "cloud") {
|
|
@@ -7977,7 +7977,7 @@ async function cloudConnect(args) {
|
|
|
7977
7977
|
return 1;
|
|
7978
7978
|
}
|
|
7979
7979
|
const runnerId = String(parsed.cloud.runner_id || process2.env.SYNAPSOR_RUNNER_ID || "synapsor_runner_local").trim();
|
|
7980
|
-
const runnerVersion = String(parsed.cloud.runner_version || process2.env.npm_package_version || "0.1.0-alpha.
|
|
7980
|
+
const runnerVersion = String(parsed.cloud.runner_version || process2.env.npm_package_version || "0.1.0-alpha.7").trim();
|
|
7981
7981
|
const engines = normalizeEngines(parsed.cloud.engines);
|
|
7982
7982
|
const capabilities = normalizeCapabilities(parsed.cloud.capabilities);
|
|
7983
7983
|
const client = new ControlPlaneClient({
|
|
@@ -11435,7 +11435,7 @@ function starterCloudConfig() {
|
|
|
11435
11435
|
base_url_env: "SYNAPSOR_CLOUD_BASE_URL",
|
|
11436
11436
|
runner_token_env: "SYNAPSOR_RUNNER_TOKEN",
|
|
11437
11437
|
runner_id: "synapsor_runner_local",
|
|
11438
|
-
runner_version: "0.1.0-alpha.
|
|
11438
|
+
runner_version: "0.1.0-alpha.7",
|
|
11439
11439
|
project_id: "token_scope",
|
|
11440
11440
|
adapter_id: "mcp.your_adapter",
|
|
11441
11441
|
source_id: "src_replace_me",
|
package/docs/mcp-client-setup.md
CHANGED
|
@@ -127,7 +127,7 @@ npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve-http \
|
|
|
127
127
|
"-y",
|
|
128
128
|
"-p",
|
|
129
129
|
"@synapsor/runner@alpha",
|
|
130
|
-
"synapsor",
|
|
130
|
+
"synapsor-runner",
|
|
131
131
|
"mcp",
|
|
132
132
|
"serve",
|
|
133
133
|
"--config",
|
|
@@ -161,6 +161,39 @@ approve_proposal
|
|
|
161
161
|
commit_proposal
|
|
162
162
|
```
|
|
163
163
|
|
|
164
|
+
## Sanity Check The Agent Connection
|
|
165
|
+
|
|
166
|
+
After installing the MCP client snippet, restart the client and run a deliberately
|
|
167
|
+
small tool-call test.
|
|
168
|
+
|
|
169
|
+
First confirm what Runner exposes:
|
|
170
|
+
|
|
171
|
+
```bash
|
|
172
|
+
npx -y -p @synapsor/runner@alpha synapsor-runner tools preview \
|
|
173
|
+
--config ./synapsor.runner.json \
|
|
174
|
+
--store ./.synapsor/local.db
|
|
175
|
+
```
|
|
176
|
+
|
|
177
|
+
Then ask the MCP client:
|
|
178
|
+
|
|
179
|
+
```text
|
|
180
|
+
Use the Synapsor Runner MCP tool to inspect invoice INV-3001.
|
|
181
|
+
Do not answer from memory.
|
|
182
|
+
Return the tool name called, the evidence handle, and whether raw SQL was available.
|
|
183
|
+
```
|
|
184
|
+
|
|
185
|
+
Expected result:
|
|
186
|
+
|
|
187
|
+
- the client calls a tool such as `billing.inspect_invoice`;
|
|
188
|
+
- the response includes an evidence handle or local ledger reference;
|
|
189
|
+
- the model reports that raw SQL, write credentials, approval tools, and commit
|
|
190
|
+
tools were not available.
|
|
191
|
+
|
|
192
|
+
If the answer is generic prose or unrelated task planning with no tool call and
|
|
193
|
+
no evidence handle, Synapsor Runner is not connected to that agent session yet.
|
|
194
|
+
Check the MCP config path, restart the client, set trusted context env vars, and
|
|
195
|
+
run `tools/list` or `synapsor-runner tools preview` again.
|
|
196
|
+
|
|
164
197
|
## Claude Desktop / Cursor / VS Code
|
|
165
198
|
|
|
166
199
|
Use the matching checked-in example as the starting point:
|