Where the work happens
YankyBot’s local workflow runs beside you on your Mac. Agents have a built-in browser and can use the native computer tools after you grant the necessary macOS permissions. File-based memory and chat history live locally. Relevant context still goes to the AI provider used for the task.
Grok Bot’s default workspace is a persistent cloud computer. Bots on the same account share its files and sessions, with separate screens for computer work. Cloud tasks can continue when your laptop is closed. Source: computer and apps documentation ↗
Local access is not exclusive to YankyBot
Grok Bot also documents optional execution of commands on your own computer. Its local-computer policy is separate from cloud approvals, with ask-every-time, always-allow and never-allow options. It is therefore inaccurate to say that Grok Bot can never reach a local machine. Source: local computer access ↗
The practical distinction is the default workspace and the access path. In YankyBot, direct Mac interaction is a core local workflow. Choose the path that matches the files and apps needed for the job, then review the actual permissions in the version you use.
Choose access for the job in front of you
| YankyBot mode | When it is useful | What to remember |
|---|---|---|
| Read only | Inspecting source material and preparing an analysis. | Keep changing or operating tools restricted. |
| Ask first | A task that may need an action you want to review. | Check the target and effect of the request before approving. |
| Full access | A trusted, bounded workflow needing fewer interruptions. | Broader tool permission still needs a clear scope and supervision. |
YankyBot shows an activity indicator during computer work, and ⌘⇧Esc is the emergency stop. macOS Accessibility and Screen Recording permissions are separate system requirements; a mode inside the app does not grant them.
Approvals are part of both workflows
Grok Bot describes Auto Review, action cards and user rules for consequential work. Its documentation distinguishes your instructions from text encountered in a page or email. Source: approvals and security ↗
Whichever product you use, be precise about actions such as sending a message, publishing a page or changing an account. “Prepare the draft” and “send the draft” are different tasks. Stop when the action or destination is unclear, then narrow the instruction.
Availability and data are different questions
YankyBot’s local schedules need the Mac awake and the app running. Grok Bot documents scheduled and event-driven routines in its cloud workflow. Source: skills and routines ↗
Local storage is useful when you want to inspect your files directly, but it is not a claim that data never leaves the machine. A cloud workspace is useful for continuity, but it should not receive material outside the task’s scope. Review the source data, credentials and services involved in either case.
Use the six-part agent brief to make that scope explicit, or compare the subscription trade-offs.
Put a little team to work.
YankyBot is a free Mac app in development. Your AI subscription is separate.
Explore early accessYankyBot is an independent product, not affiliated with xAI, OpenAI or Anthropic. Product names belong to their respective owners.
