AideNote Recording Notes Local Agent Bridge

Problem it addresses

Meeting summaries, action items, shared recordings, and local knowledge files are scattered across the AideNote app, cloud service, and local agents. If an agent is asked directly, it may answer generically or treat a missing CLI as missing data. This skill connects AideNote voice notes, todos, and knowledge bases to a local MCP service so WorkBuddy, OpenClaw, Codex, and similar agents can answer from real records.

How it works

The core is the AideNote MCP tool set, not a usage guide. Useful tools include aidenote_list_recordings, aidenote_get_recording_detail, aidenote_list_todos, aidenote_find_knowledge_items, and aidenote_get_note_content. For meeting actions, the agent should read recent recordings first, then fetch a specific detail. For knowledge files, it should prefer fileId / folderId and return ambiguous same-name candidates instead of guessing.

The skill also bridges phone and desktop environments through a local bridge. WorkBuddy can use a Desktop bridge or fall back to ACP sessions by injecting the MCP configuration into a new session. OpenClaw, Hermes, and Codex connect through local ports, device approval, or project-directory authorization. Bulk reads should bound maxItems and maxChars; create, move, and copy operations default to conflictPolicy=error.

Boundaries and cautions

This skill only bridges the current signed-in user's local services and AideNote account. slonaide_* commands are mainly for OpenClaw / ClawHub-compatible environments; in WorkBuddy, MCP tools should be preferred. Transcripts and notes are private, so output should default to summaries. Overwriting same-name files requires an explicit instruction. If the bridge is offline, accounts do not match, or MCP has not loaded, check the real status before claiming that no data exists.