Menu
Roll out new openAGI code to the main and to Mac nodes (iMessage / computer-use), and restart them safely.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
Troubleshoot opaque model/tool failures and runaway budget — and their usual root causes.
Troubleshoot why the agent stopped replying to iMessages, in priority order.
Connect an MCP server (catalog or custom URL/stdio) and make its tools usable — including completing OAuth on a headless host.
Operate a connected computer-use node to accomplish an on-screen task — screenshot, reason, act in a loop.
Set up a recurring check that only does work (and spends tokens) when there's something new — e.g. "every hour, check BuildBetter for new calls".
| name | deploy-update-node |
| description | Roll out new openAGI code to the main and to Mac nodes (iMessage / computer-use), and restart them safely. |
Roll out updated code. Critical fact: the MAIN self-updates its own git checkout, but each NODE runs off its OWN separate checkout and does NOT receive the main's update — every node must pull and restart itself.
Main agent host:
main and restarts the daemon). After it comes back, confirm the new commit is live before assuming the fix is deployed.Each Mac node (iMessage bridge, iMessage search server, computer-server):
git pull origin main.launchctl kickstart -k gui/$(id -u)/<label> (e.g. app.openagi.imessage-bridge, app.openagi.computer-server).openagi <subcommand> line./health, a test search_imessages, or a test /screenshot.Guidance for the user (you usually can't SSH their nodes):
git pull + restart commands for each affected node.User asked: {{input}}