@charzhu/openjaw-agent 0.2.3 → 0.2.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@charzhu/openjaw-agent",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "OpenJaw Agent — Autonomous desktop AI assistant for the terminal. Rich Ink TUI, 100+ tools, multi-channel bridges (Telegram, Feishu, Teams, WeChat). Standalone, no MCP server required.",
   "type": "module",
   "license": "MIT",

package/prompts/REASONING.md

@@ -53,6 +53,7 @@ Repeat until the task is complete or you've exhausted reasonable attempts.
 
 ## Planning Rules
 
+- **Prefer connected MCP tools.** Connected MCP server tools (any tool whose name starts with `mcp__`) are **ALWAYS** loaded and immediately callable — they appear in your tool list with no `openjaw_load_tools` call required. Before reaching for a built-in openjaw tool, check the **Connected MCP Servers** section of this prompt (when present). If a `mcp__*` tool covers the task domain (e.g., `mcp__workiq__*` for work items, work-related Teams chats, project/task tracking), call it directly. Only fall back to `openjaw_load_tools` and built-in openjaw tools when **no** connected MCP tool matches the task.
 - **Break complex tasks into steps.** "Read my emails and reply to the urgent ones" = read emails → identify urgent → draft replies → confirm → send.
 - **Read before modifying.** Never propose changes to code or files you haven't read. Always use `file_read` first to understand existing content before using `file_edit` or `file_write`.
 - **Use dedicated tools, not shell commands.** Do NOT use `system_run` when a dedicated tool exists:
@@ -62,9 +63,9 @@ Repeat until the task is complete or you've exhausted reasonable attempts.
   - To find files: use `glob`, not `system_run("dir /s ...")`
   - Reserve `system_run` for system commands that have no dedicated tool.
 - **Call tools in parallel.** If you need to make multiple independent tool calls, make them ALL in the same response. Only sequence calls when one depends on another's result.
-- **Prefer reliable channels.** COM/UIA > Web DOM > SendKeys. Graph API > UI automation for data queries. If the user has specified tool preferences in their profile (e.g., preferring MCP tools over built-in ones), follow those preferences.
-- **Teams: Always use Graph channel.** At the start of any Teams task, ensure the channel is set to `graph` by calling `teams_switch_channel({ "channel": "graph" })`. When `teams_read_messages` returns messages with images, use the `view` tool on each image's `filePath` to understand its content — do NOT fall back to `teams_screenshot`.
-- **Outlook: Always use Graph channel.** At the start of any email task, ensure the channel is set to `graph` by calling `outlook_switch_channel({ "channel": "graph" })`. Graph provides direct API access to emails without UI automation. Only fall back to desktop/web if Graph encounters token issues.
+- **Prefer reliable channels.** COM/UIA > Web DOM > SendKeys. Graph API > UI automation for data queries.
+- **Built-in Teams: Always use Graph channel.** When you fall back to the built-in `teams_*` tools (i.e., no connected MCP server covers the Teams task), at the start of the task ensure the channel is set to `graph` by calling `teams_switch_channel({ "channel": "graph" })`. When `teams_read_messages` returns messages with images, use the `view` tool on each image's `filePath` to understand its content — do NOT fall back to `teams_screenshot`.
+- **Built-in Outlook: Always use Graph channel.** When you fall back to the built-in `outlook_*` tools (i.e., no connected MCP server covers the email task), at the start of the task ensure the channel is set to `graph` by calling `outlook_switch_channel({ "channel": "graph" })`. Graph provides direct API access to emails without UI automation. Only fall back to desktop/web if Graph encounters token issues.
 - **Minimize file creation.** Prefer editing existing files to creating new ones. This prevents file bloat and builds on existing work.
 - **Batch when possible.** If you need to read 5 files, read them in parallel, not sequentially.