Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

setup-imessage-node

Estrellas2

Forks1

Actualizado15 de junio de 2026, 23:19

Guide setting up a Mac as an iMessage node — relays incoming texts to the main agent (trigger word) and answers iMessage searches.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Spshulem

Spshulem/openAGI

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	setup-imessage-node
description	Guide setting up a Mac as an iMessage node — relays incoming texts to the main agent (trigger word) and answers iMessage searches.

Walk the user through turning a Mac (signed into iMessage) into an iMessage node. macOS-only, and it needs system permissions you can't grant for them — so produce clear, copy-pasteable steps and explain each grant. Substitute <host>, <port>, <secret>, <TriggerWord> for their values; never hardcode real numbers/tokens.

Two processes (run from the openAGI repo on that Mac):

openagi imessage-bridge --respond trigger --trigger <TriggerWord> --allow <handle,handle> --allow-chat <chatId> --capture all Reads ~/Library/Messages/chat.db read-only, relays messages containing the trigger to the main, and replies via Messages. Omit --allow* to respond to everyone; --allow-chat opts a group thread in.
openagi imessage-server --token <secret> --port <port> (optional) Serves iMessage SEARCH to the main, giving it a search_imessages tool.

Steps to give the user:

Clone/run the openAGI repo on the Mac.
System Settings → Privacy & Security: grant the runtime that launches these (the node binary; Terminal while testing) Full Disk Access (read chat.db) and Automation → Messages (send replies).
Run the bridge (and optionally the search server). For persistence install a launchd USER agent (RunAtLoad + KeepAlive) that runs the command; restart it with launchctl kickstart -k gui/$(id -u)/<label>.
On the MAIN agent host, point at the node: OPENAGI_IMESSAGE_NODE=http://<host>:<port> and OPENAGI_IMESSAGE_NODE_TOKEN=<secret>, then restart.

Gotchas to mention:

chat.db MUST be opened read-only — a read-write connection on the live WAL database can hang/crash Messages.
On recent macOS the message text often lives only in attributedBody (the text column is NULL); the bridge decodes that typedstream blob.
A process launched by launchd needs its OWN TCC grant — granting Terminal is not enough; the launchd-spawned node must be approved separately.
Track messages by date, not ROWID (a chat.db rebuild renumbers ROWIDs non-chronologically).

User asked: {{input}}

Más de este repositorio

mismo repositorio

setup-proactive-outreach

Spshulem/openAGI

Guide configuring proactive outreach so the main reaches out (digest + live decisions) and the Mac app surfaces it with notifications, an overlay list, and inline buttons.

2026-06-172

deploy-update-node

Spshulem/openAGI

Roll out new openAGI code to the main and to Mac nodes (iMessage / computer-use), and restart them safely.

2026-06-152

diagnose-agent-tool-errors

Spshulem/openAGI

Troubleshoot opaque model/tool failures and runaway budget — and their usual root causes.

2026-06-152

diagnose-no-imessage-replies

Spshulem/openAGI

Troubleshoot why the agent stopped replying to iMessages, in priority order.

2026-06-152

connect-mcp

Spshulem/openAGI

Connect an MCP server (catalog or custom URL/stdio) and make its tools usable — including completing OAuth on a headless host.

2026-06-152

drive-computer-use

Spshulem/openAGI

Operate a connected computer-use node to accomplish an on-screen task — screenshot, reason, act in a loop.

2026-06-152

name	setup-imessage-node
description	Guide setting up a Mac as an iMessage node — relays incoming texts to the main agent (trigger word) and answers iMessage searches.

Two processes (run from the openAGI repo on that Mac):

openagi imessage-bridge --respond trigger --trigger <TriggerWord> --allow <handle,handle> --allow-chat <chatId> --capture all Reads ~/Library/Messages/chat.db read-only, relays messages containing the trigger to the main, and replies via Messages. Omit --allow* to respond to everyone; --allow-chat opts a group thread in.
openagi imessage-server --token <secret> --port <port> (optional) Serves iMessage SEARCH to the main, giving it a search_imessages tool.

Steps to give the user:

Clone/run the openAGI repo on the Mac.
System Settings → Privacy & Security: grant the runtime that launches these (the node binary; Terminal while testing) Full Disk Access (read chat.db) and Automation → Messages (send replies).
Run the bridge (and optionally the search server). For persistence install a launchd USER agent (RunAtLoad + KeepAlive) that runs the command; restart it with launchctl kickstart -k gui/$(id -u)/<label>.
On the MAIN agent host, point at the node: OPENAGI_IMESSAGE_NODE=http://<host>:<port> and OPENAGI_IMESSAGE_NODE_TOKEN=<secret>, then restart.

Gotchas to mention:

chat.db MUST be opened read-only — a read-write connection on the live WAL database can hang/crash Messages.
On recent macOS the message text often lives only in attributedBody (the text column is NULL); the bridge decodes that typedstream blob.
A process launched by launchd needs its OWN TCC grant — granting Terminal is not enough; the launchd-spawned node must be approved separately.
Track messages by date, not ROWID (a chat.db rebuild renumbers ROWIDs non-chronologically).

User asked: {{input}}