@femtomc/mu-agent 26.2.50 → 26.2.51

package/dist/extensions/messaging-setup.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"messaging-setup.d.ts","sourceRoot":"","sources":["../../src/extensions/messaging-setup.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAGH,OAAO,KAAK,EAAE,YAAY,EAA6C,MAAM,+BAA+B,CAAC;AAuiC7G,wBAAgB,uBAAuB,CAAC,EAAE,EAAE,YAAY,QA+PvD;AAED,eAAe,uBAAuB,CAAC"}
+{"version":3,"file":"messaging-setup.d.ts","sourceRoot":"","sources":["../../src/extensions/messaging-setup.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAGH,OAAO,KAAK,EAAE,YAAY,EAA6C,MAAM,+BAA+B,CAAC;AAwiC7G,wBAAgB,uBAAuB,CAAC,EAAE,EAAE,YAAY,QA0PvD;AAED,eAAe,uBAAuB,CAAC"}

package/dist/extensions/messaging-setup.js

@@ -763,6 +763,7 @@ function buildAgentSetupPrompt(opts) {
     const verifyFlag = normalizedBase ? ` --public-base-url ${normalizedBase}` : "";
     return interpolateTemplate(MESSAGING_SETUP_BRIEF_TEMPLATE, {
         adapter_name: adapter.name,
+        adapter_id: adapter.id,
         state: opts.check.state,
         config_path: opts.configPath ?? ".mu/config.json",
         route: opts.plan.route,
@@ -875,11 +876,14 @@ export function messagingSetupExtension(pi) {
         public_base_url: Type.Optional(Type.String({
             description: "Optional public base URL used to compute expected webhook endpoints (e.g. https://example.ngrok.app)",
         })),
+        fields: Type.Optional(Type.Record(Type.String(), Type.String(), {
+            description: "Config field overrides for apply action. Keys are field names (e.g. bot_token, webhook_secret), values are the secrets/tokens to write.",
+        })),
     });
     pi.registerTool({
         name: "mu_messaging_setup",
         label: "Messaging Setup",
-        description: "Messaging setup workflow. Actions: check/preflight/guide/plan/apply/verify. Use plan -> apply -> verify.",
+        description: "Messaging setup workflow. Actions: check/preflight/guide/plan/apply/verify. For apply, pass field values via the fields parameter (e.g. fields={bot_token:'...', webhook_secret:'...'}).",
         parameters: SetupParams,
         async execute(_toolCallId, params, _signal, _onUpdate, ctx) {
             const adapterId = params.adapter ? normalizeAdapterId(params.adapter) : null;
@@ -936,18 +940,14 @@ export function messagingSetupExtension(pi) {
                     if (!check) {
                         return textResult(`Unknown adapter: ${adapterId}`);
                     }
-                    if (check.missing.length > 0) {
-                        return textResult(`Cannot apply ${adapterId}: missing required config fields (${check.missing.join(", ")}). Use /mu-setup apply ${adapterId} for guided input.`, { adapter: adapterId, missing_required_fields: check.missing });
-                    }
-                    if (!ctx.hasUI) {
-                        return textResult("Apply is blocked in non-interactive mode. Use `/mu-setup apply <adapter>` in an interactive `mu serve` session.", { adapter: adapterId, blocked: true });
-                    }
-                    const confirmed = await ctx.ui.confirm(`Apply ${adapterId} configuration?`, "This may write config and triggers control-plane reload.");
-                    if (!confirmed) {
-                        return textResult("Apply cancelled by user.", { adapter: adapterId, cancelled: true });
+                    const overrides = params.fields ?? {};
+                    const stillMissing = check.missing.filter((field) => !(field in overrides));
+                    if (stillMissing.length > 0) {
+                        return textResult(`Cannot apply ${adapterId}: missing required config fields (${stillMissing.join(", ")}). Pass them via the fields parameter or use /mu-setup apply ${adapterId} for guided input.`, { adapter: adapterId, missing_required_fields: stillMissing });
                     }
                     const outcome = await applyAdapterConfig({
                         adapterId,
+                        overrides,
                         presence: runtime.configPresence,
                     });
                     if (!outcome.ok) {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@femtomc/mu-agent",
-	"version": "26.2.50",
+	"version": "26.2.51",
 	"description": "Shared agent runtime for mu chat, orchestration roles, and serve extensions.",
 	"keywords": [
 		"mu",
@@ -23,7 +23,7 @@
 		"prompts/**"
 	],
 	"dependencies": {
-		"@femtomc/mu-core": "26.2.50",
+		"@femtomc/mu-core": "26.2.51",
 		"@mariozechner/pi-agent-core": "^0.52.12",
 		"@mariozechner/pi-ai": "^0.52.12",
 		"@mariozechner/pi-coding-agent": "^0.52.12",

package/prompts/skills/messaging-setup-brief.md

@@ -1,4 +1,4 @@
-Set up {{adapter_name}} messaging for mu control-plane. You have Bash, Read, Write, and Edit tools — use them to do the setup yourself.
+Set up {{adapter_name}} messaging for mu control-plane.
 
 [Diagnostics]
 state: {{state}}
@@ -16,7 +16,8 @@ missing fields: {{missing_fields}}
 [Instructions]
 1) Ask the user ONLY for values you cannot generate: secrets from external providers (e.g. bot tokens from @BotFather), public base URL.
 2) Generate values you CAN create yourself (e.g. webhook_secret — run `openssl rand -hex 32` via Bash).
-3) Use your tools to write the config file directly, call provider APIs (curl via Bash), and complete setup end-to-end.
-4) After setup, run {{verify_command}} to confirm everything works.
+3) Write config via mu_messaging_setup tool: call mu_messaging_setup(action="apply", adapter="{{adapter_id}}", fields={...}) with ALL missing field values. This writes config and reloads the control plane in one step.
+4) After config is applied, call provider APIs (e.g. Telegram setWebhook) via Bash/curl.
+5) Run {{verify_command}} to confirm everything works.
 
-Do NOT give the user copy-paste commands. Do the work yourself.
+Do NOT give the user copy-paste commands or tutorials. Do the work yourself.