@mono-agent/agent-app 0.11.4 → 0.11.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mono-agent/agent-app",
-  "version": "0.11.4",
+  "version": "0.11.5",
   "description": "Config-first mono-agent host: builds a responder and starts every configured communication channel and traceability from one mono-agent.config.json.",
   "type": "module",
   "license": "GPL-3.0-only",
@@ -37,20 +37,20 @@
     "@clack/prompts": "^1.7.0",
     "@earendil-works/pi-ai": "0.80.6",
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@mono-agent/agent-contracts": "0.11.4",
-    "@mono-agent/agent-harness": "0.11.4",
-    "@mono-agent/config": "0.11.4",
-    "@mono-agent/cron-adapter": "0.11.4",
-    "@mono-agent/operator-adapter": "0.11.4",
-    "@mono-agent/memory": "0.11.4",
-    "@mono-agent/observability": "0.11.4",
-    "@mono-agent/openai-api-adapter": "0.11.4",
-    "@mono-agent/runtime-adapter": "0.11.4",
-    "@mono-agent/session-web": "0.11.4",
-    "@mono-agent/slack-adapter": "0.11.4",
-    "@mono-agent/telegram-adapter": "0.11.4",
-    "@mono-agent/tui": "0.11.4",
-    "@mono-agent/webhook-adapter": "0.11.4",
+    "@mono-agent/agent-contracts": "0.11.5",
+    "@mono-agent/agent-harness": "0.11.5",
+    "@mono-agent/config": "0.11.5",
+    "@mono-agent/cron-adapter": "0.11.5",
+    "@mono-agent/operator-adapter": "0.11.5",
+    "@mono-agent/memory": "0.11.5",
+    "@mono-agent/observability": "0.11.5",
+    "@mono-agent/openai-api-adapter": "0.11.5",
+    "@mono-agent/runtime-adapter": "0.11.5",
+    "@mono-agent/session-web": "0.11.5",
+    "@mono-agent/slack-adapter": "0.11.5",
+    "@mono-agent/telegram-adapter": "0.11.5",
+    "@mono-agent/tui": "0.11.5",
+    "@mono-agent/webhook-adapter": "0.11.5",
     "undici": "8.7.0",
     "zod": "^4.4.3"
   },

package/skills/mono-agent-composer/references/config-blueprint.md

@@ -257,11 +257,12 @@ new agent.
     "modelId": "my-agent"                  // model id advertised to API clients
   },
 
-  // Telegram & Slack deliver only the FINAL answer by default (no streamed
-  // interim edits) while showing a working indicator — Telegram a "typing…"
-  // action, Slack a 👀 "seen" reaction. This is built-in behavior (not a JSON
-  // field); restoring live interim streaming needs a custom channel driver with
-  // stream.finalOnly=false. The OpenAI-compatible endpoint still streams tokens.
+  // Telegram & Slack do not stream ANSWER tokens by default. They first show a
+  // working indicator; inbound tool starts then edit one temporary, redacted
+  // activity ledger that the final answer replaces. Proactive turns suppress
+  // the ledger. This is built-in behavior (not a JSON field); a custom channel
+  // driver can set stream.showHints=false or stream.finalOnly=false. The
+  // OpenAI-compatible endpoint still streams tokens.
   "telegram": {
     "enabled": true,                       // opt-in; defaults to false (off → "disabled")
     // Put MONO_AGENT_TELEGRAM_BOT_TOKEN in .env; do not inline botToken here.

package/skills/mono-agent-composer/references/package-map.md

@@ -96,7 +96,7 @@ Communication adapters are edge packages. They accept an `AgentResponder` and ow
 | Surface | Package | First smoke |
 | --- | --- | --- |
 | Telegram | `@mono-agent/telegram-adapter` | Allowed chat sends a message |
-| Slack | `@mono-agent/slack-adapter` | Allowed channel or DM gets a streamed reply |
+| Slack | `@mono-agent/slack-adapter` | Allowed channel or DM gets the final reply |
 | WhatsApp | `@mono-agent/whatsapp-adapter` (external channel plugin) | Allowed sender/group trigger produces a reply |
 | OpenAI-compatible API | `@mono-agent/openai-api-adapter` | `curl /v1/models` and `/v1/chat/completions` |
 | Operator endpoints | `@mono-agent/operator-adapter` | `mono-agent tui` connects; `mono-agent web` observes live runs |

package/skills/mono-agent-composer/references/playbooks.md

@@ -14,7 +14,7 @@ Flow, check whether one of these fits and adapt it. Verify every key against
 ## 1. Personal Telegram assistant with BuJo memory
 **For:** an individual wanting a private assistant that remembers.
 **Goal:** a Telegram bot (long polling) that captures every turn into BuJo memory with scheduled consolidation and recalls past notes semantically.
-**Features:** `telegram.long-polling`, `channel.final-only-delivery`, `memory.bujo`, `memory.per-turn-capture`, `memory.bujo-consolidation`, `memory.recall-tool`, `memory.embeddings`.
+**Features:** `telegram.long-polling`, `channel.final-only-delivery`, `channel.transient-tool-activity`, `memory.bujo`, `memory.per-turn-capture`, `memory.bujo-consolidation`, `memory.recall-tool`, `memory.embeddings`.
 
 Put `MONO_AGENT_TELEGRAM_BOT_TOKEN=...` in `.env`; the source config omits the credential.
 
@@ -31,12 +31,12 @@ Put `MONO_AGENT_TELEGRAM_BOT_TOKEN=...` in `.env`; the source config omits the c
 }
 ```
 **Steps:** `ollama pull nomic-embed-text:v1.5 && ollama pull qwen3.6:latest` → `mono-agent init --model claude:claude-sonnet-4-6 --memory bujo` → add telegram + fill embeddings/llm + `writeMode: capture` → `mono-agent validate` (confirm memory liveness + consolidation cadence) → `mono-agent start`.
-**Smoke:** send a fact from the allowed chat, then ask a paraphrased question later; confirm `MemoryRecall` in the run JSONL and that the answer uses it.
+**Smoke:** send a fact from the allowed chat, then ask a paraphrased question later; confirm the temporary memory-tool activity is replaced by the final answer, `MemoryRecall` appears in the run JSONL, and the answer uses it.
 
 ## 2. Slack team bot with MCP tools
 **For:** a DevOps engineer running a shared team bot.
 **Goal:** a mention-triggered Slack Socket Mode bot with a custom MCP tool, Read/Grep, and `SlackSendMessage` for proactive posts.
-**Features:** `slack.socket-mode`, `tool-policy.allowlist`, `tool-policy.mcp-servers`, `agent-app.adapter-send-tools`, `runtime.concurrency`.
+**Features:** `slack.socket-mode`, `channel.transient-tool-activity`, `tool-policy.allowlist`, `tool-policy.mcp-servers`, `agent-app.adapter-send-tools`, `runtime.concurrency`.
 
 Put `MONO_AGENT_SLACK_BOT_TOKEN` and `MONO_AGENT_SLACK_APP_TOKEN` in `.env`; the source config omits credentials.
 
@@ -49,7 +49,7 @@ Put `MONO_AGENT_SLACK_BOT_TOKEN` and `MONO_AGENT_SLACK_APP_TOKEN` in `.env`; the
 }
 ```
 **Steps:** create a Slack app (Socket Mode app token + bot token) → `mono-agent init` (allow-all by default) → write `mcp.json` (the MCP tool becomes available from the server declaration — MCP tools aren't gated by `allowedTools`) → add slack; `SlackSendMessage` is auto-available under allow-all, or name it if you narrow to a specific allowlist → `validate` → `start`.
-**Smoke:** mention the bot in an allowed channel; confirm the 👀 reaction, final answer, the MCP tool firing in the artifact, and that `SlackSendMessage` posts only to allowed channels.
+**Smoke:** mention the bot in an allowed channel; confirm the 👀/assistant status, the temporary MCP-tool activity message being replaced by the final answer, the tool firing in the artifact, and `SlackSendMessage` posting only to allowed channels.
 
 ## 3. Fully local Ollama agent (no cloud)
 **For:** a privacy-focused user with no cloud budget.

package/skills/mono-agent-composer/references/validation.md

@@ -94,8 +94,8 @@ pnpm run test:demo
 | Surface | Smoke |
 | --- | --- |
 | TUI | Start the host, connect with ordinary `mono-agent tui`, and complete one real prompt against the running responder. |
-| Telegram | Send one allowed chat message and verify the reply. |
-| Slack | Send one allowed DM or channel message and verify formatting. |
+| Telegram | Send one allowed chat message that uses a tool; verify one transient activity ledger is replaced by the final reply. |
+| Slack | Send one allowed DM or channel message that uses a tool; verify formatting and one transient activity ledger replaced by the final reply. |
 | Adapter send tools | When `SlackSendMessage` / `TelegramSendMessage` are available (allow-all, or an explicit `tools.allowedTools` entry) with the channel enabled, call them from a non-Slack/Telegram surface such as TUI, cron, or OpenAI API to an allowed destination; verify delivery, then reply at the destination and verify the exact sent text appears in replayed history. |
 | WhatsApp | Send one allowed sender/group trigger and verify the reply. |
 | OpenAI API | `curl /v1/models` and `/v1/chat/completions`. |