Ultron.
Start here / Ultron

Ultron in Claude Cowork

Use Ultron inside Cowork for user-defined research, native schedules and phone notifications.

Updated September 8, 2026 · Independent beta

Your AI is the workspace

Use Claude Cowork for recurring research and native phone notifications. Connect Ultron once through remote MCP, then keep the conversation, tools, provider setup and research approvals inside your AI. Regular chat remains useful for one-off questions.

Use a successful Ultron tool call to verify the connection. For repeatable work, keep Ultron enabled in the task and put its tool names in the saved instructions. The optional Ultron plugin includes a scheduled-research skill.

Context that survives the next run

Cowork scheduled tasks start fresh sessions. Store the objective, cadence, timezone, tools and notification conditions in the task prompt or attached skill. Use get_task_context and save_task_context with one stable taskKey for small baselines and delivered-result IDs. Version checks prevent concurrent overwrites.

Remote connector-only tasks do not depend on a laptop staying awake. Local folders, local tools and Dispatch have their own execution requirements. Keep source material in an accessible account project or connected service.

Notifications belong to your AI

Create and manage the task using Cowork’s native scheduler. Enable the host’s notifications and test once on the intended device. A successful test does not guarantee every future run; monitor failed runs and expired connections.

Ultron does not require a separate mobile app, PWA, device pairing, Telegram or Discord. Avoid duplicating the same scan in both Cowork and Ultron server routines. Use a server monitor only when persistent collection is part of the selected workflow.

Your rules, not a preset strategy

Conditions remain user-defined. Preserve exact metrics and intervals; do not substitute FDV for market cap or a different volume window. Missing observations are unknown. A crossing requires a prior observation, while an above-threshold snapshot does not.

get_schedule_readiness reports Ultron permissions and connection expiry. It cannot inspect the host’s schedule. Reconnect through the host when credentials expire. Paid social requests require the explicit in-AI review; recurring scans do not silently spend on new paid research.

ChatGPT Work and other AI apps

Use the native scheduled-task surface when it supports Ultron’s connected tools. Feature and notification availability depend on the host, plan and workspace. Remote web tasks and local desktop project tasks have different requirements.

The same Ultron task-context tools and scheduled-research skill work without assuming a specific scheduler API. Verify a run and delivery in the selected app; do not claim identical support across every client.

Need a concrete starting point?

Build something →Track something →