catence 0.2.1-beta.10 → 0.2.1-beta.12

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.
@@ -3,7 +3,7 @@
3
3
  * Keep these values synchronized with release/manifest.json; release checks
4
4
  * deliberately reject drift before a package can be published.
5
5
  */
6
- export declare const CATENCE_RUNTIME_VERSION = "0.2.1-beta.10";
6
+ export declare const CATENCE_RUNTIME_VERSION = "0.2.1-beta.12";
7
7
  export declare const CATENCE_PROTOCOL_VERSION = 1;
8
8
  export type CatenceRuntimeCapabilities = {
9
9
  mcp: true;
@@ -3,7 +3,7 @@
3
3
  * Keep these values synchronized with release/manifest.json; release checks
4
4
  * deliberately reject drift before a package can be published.
5
5
  */
6
- export const CATENCE_RUNTIME_VERSION = '0.2.1-beta.10';
6
+ export const CATENCE_RUNTIME_VERSION = '0.2.1-beta.12';
7
7
  export const CATENCE_PROTOCOL_VERSION = 1;
8
8
  export function catenceRuntimeHealth() {
9
9
  return {
@@ -96,6 +96,7 @@ The Console model configuration. `defaultProfile` must name one of
96
96
  "console": {
97
97
  "defaultProfile": "openai",
98
98
  "limits": { "toolRounds": 8, "toolResultCharacters": 24000 },
99
+ "defaultToolServers": true,
99
100
  "mcpServers": { … },
100
101
  "profiles": { … }
101
102
  }
@@ -169,21 +170,39 @@ replaced.
169
170
 
170
171
  ### `console.mcpServers`
171
172
 
172
- Extra MCP tool servers the Console agent connects to alongside the Catence
173
- runtime. This is how the Console gains capabilities Catence does not provide,
174
- such as web search. HTTP (Streamable HTTP) servers only; each entry is keyed by
175
- a short server name used in tool step labels.
173
+ MCP tool servers the Console agent connects to alongside the Catence runtime.
174
+ This is how the Console gains capabilities Catence does not provide, such as web
175
+ search. HTTP (Streamable HTTP) servers only; each entry is keyed by a short
176
+ server name used in tool step labels.
177
+
178
+ The Console ships one default entry, **Exa Web Search** — the hosted endpoint
179
+ works without a key (rate-limited), so search is available out of the box:
176
180
 
177
181
  ```jsonc
178
182
  "mcpServers": {
179
183
  "exa": {
180
184
  "label": "Exa Web Search",
181
- "url": "https://mcp.exa.ai/mcp",
185
+ "url": "https://mcp.exa.ai/mcp?tools=web_search_exa,web_fetch_exa"
186
+ }
187
+ }
188
+ ```
189
+
190
+ To use an Exa API key instead (higher limits), add an `exa` entry of your own —
191
+ it replaces the built-in one wholesale:
192
+
193
+ ```jsonc
194
+ "mcpServers": {
195
+ "exa": {
196
+ "label": "Exa Web Search",
197
+ "url": "https://mcp.exa.ai/mcp?tools=web_search_exa,web_fetch_exa",
182
198
  "headers": { "x-api-key": "$EXA_API_KEY" }
183
199
  }
184
200
  }
185
201
  ```
186
202
 
203
+ Set `"defaultToolServers": false` in the `console` section to remove the
204
+ built-in server entirely.
205
+
187
206
  Allowed entry fields (strict):
188
207
 
189
208
  | Field | Required | Meaning |
@@ -199,17 +218,14 @@ after the runtime has started and applies to the next chat turn. A server
199
218
  whose credentials are missing is skipped with a warning step; other servers
200
219
  and Catence itself keep working. Tool names from extra servers are used as-is
201
220
  unless they collide with a Catence tool, in which case they are prefixed with
202
- the server name (`exa_web_search_exa`).
203
-
204
- The hosted Exa server (`https://mcp.exa.ai/mcp`) also works without a key
205
- (rate-limited) and offers `web_search_exa` and `web_fetch_exa` by default.
206
- Add `?tools=…` to the URL to expose a different tool set, e.g.
207
- `https://mcp.exa.ai/mcp?tools=web_search_exa,web_fetch_exa`.
208
-
209
- The **Settings → Accounts** tab (admin only) lists each configured server and
210
- its credential readiness, and lets an admin save or clear values without
211
- restarting the Console. Stored values live in
212
- `<data directory>/console/tool_server_secrets.json` (mode 0600) and take
221
+ the server name (`exa_web_search_exa`). The built-in default deliberately
222
+ references no environment variable: a missing credential would mark it unready
223
+ and skip it, so a key is attached by overriding `exa` as shown above.
224
+
225
+ The **Settings → Accounts** tab (admin only) lists each configured server
226
+ (including the built-in Exa entry) and its credential readiness, and lets an
227
+ admin save or clear values without restarting the Console. Stored values live
228
+ in `<data directory>/console/tool_server_secrets.json` (mode 0600) and take
213
229
  precedence over the process environment. `catence-console doctor` reports each
214
230
  server's readiness as well.
215
231
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "catence",
3
- "version": "0.2.1-beta.10",
3
+ "version": "0.2.1-beta.12",
4
4
  "description": "Local MCP access to normalized Garmin, Intervals.icu, and targeted Strava fitness data.",
5
5
  "license": "AGPL-3.0-or-later",
6
6
  "repository": {