Skip to content

Grok Bot proactivity talking points - #7

Draft
AayushDongre wants to merge 2 commits into
mainfrom
cursor/grok-bot-proactivity-talking-points-3425
Draft

AayushDongre wants to merge 2 commits into
mainfrom
cursor/grok-bot-proactivity-talking-points-3425

Conversation

@AayushDongre

@AayushDongre AayushDongre commented Aug 27, 2026 •

Copy link
Copy Markdown
Contributor

Draft talking points for a content piece on baking @refix/proactivity into Grok Bot.

The brief is in content/grok-bot-proactivity-talking-points.md (not product docs). It is based on the full 14-page Grok Bot docs corpus plus this repo’s plugin pattern.

Answer: yes, it is possible. It is a weaker integration — and that is the plugin path this SDK already documents for hosts it does not own (Eve, OpenClaw, Hermes), not a Grok Bot-only failure.

Grok Bot would be closest to Eve: static cron (routines) plus a due-gate. Extra weakenings vs OpenClaw: no documented tool-intercept hook, so computer-use cannot be governed; connector/MCP writes can. No model picker for a cheaper reflection.model.

Do not wrap Grok Bot in proactive(). Layer goals, briefing, cadence, and governance onto the loop it already owns.

Open in Web Open in Cursor 

cursoragent and others added 2 commits August 27, 2026 12:15
Draft brief for a content piece: what Grok Bot already ships (routines,
skills, approvals), what this SDK adds (self-pacing, goal memory,
crash-safe governance), and how to layer it on as a plugin rather than
wrapping Grok Bot in proactive().

Co-authored-by: Aayush Dongre <AayushDongre@users.noreply.github.com>
Spell out what “weaker” means against proactive() and against
OpenClaw/Hermes/Eve: cadence rides routines, no inject/transcript APIs,
and computer-use cannot be governed. Fill in the Grok Bot pages the
first pass missed (faq, mobile, get-started, files, troubleshooting).

Co-authored-by: Aayush Dongre <AayushDongre@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants