steerlabs/opensteer
Opensteer integration, Workspace, Thread, Trigger, Browser, and machine access workflows
For interactive websites, use Browser Sessions and profiles, or sign in with Chrome. For email, calendar, cloud files, CRM or messaging APIs, try Opensteer integrations first.
See and operate apps on a person's Mac, or a whole Android phone dedicated to agents, by writing JavaScript in the computer tool. Use for apps with no purpose-built integration, anything only an app's interface can do, mobile-only apps, and text messages from a phone's own number.
For another computer's files, commands, repositories or ports, use SSH. To see or operate apps on a person's Mac, use the computer tool (opensteer-computer-use). For Android phones, use the computer tool; they never use SSH.
For connected accounts, service APIs, MCP servers or Agent Plugins, discover Opensteer integrations. For Mac apps and phones, discover and request approval here, then follow opensteer-computer-use. Use for email, calendar, cloud files, CRM, messaging and project tools.
When establishing a specialist, learning standing preferences or fixing recurring mistakes, maintain durable Workspace instructions, knowledge, skills, scripts and task state.
For durable cross-Thread work, delegate/read/message Opensteer Threads. For bounded work inside this Run, prefer a harness-native worker.
For reminders, scheduled updates, webhooks or watches, create/inspect/repair/control an Opensteer Trigger. Load before authoring its program.
For a specialist or durable Workspace (not an ordinary folder), create/find/mount it and establish its AGENTS.md mission, scope and standing constraints.