Repository navigation
docs(grok-bot): the marketplace listing is not approved yet - #5465
Merged
Merged
Conversation
The README and the integration page both told people to search for Hindsight under Connect apps and add it from the marketplace. The listing is still in review, so that path does not work for anyone yet. Documents the two paths that do work today. Grok Bot gets a connect-prompt modelled on the Meta Muse one: it adds Hindsight as a custom connector and carries the same rules the skills carry, including the bounded handoff exception and the tools never to call. Cursor gets the local plugin folder, which is the install path Cursor documents. Adds tests for the prompt, matching the Meta Muse contract.
benfrank241
added a commit
that referenced
this pull request
Oct 9, 2026
Review feedback: we are not approved in the Grok Bot or Cursor marketplace yet, so the Connect apps path does not work for anyone. Replaces it with the two paths that do: the connect prompt for Grok Bot, and the local plugin folder for Cursor. Depends on #5465, which adds the connect prompt the post links to.
scripts/generate-docs-skill.sh mirrors hindsight-docs into skills/hindsight-docs/references. The install correction changed the source page, so the mirror was out of sync and verify-generated-files failed.
benfrank241
added a commit
that referenced
this pull request
Oct 9, 2026
* blog: Agent Memory That Survives the Run Grok Bot runs no plugin lifecycle hooks, so memory is driven entirely by skills. That is the architectural hook for the post, and it is what lets a scheduled routine recall its own last run and record this one, including when nothing changed. Also covers the handoff path: the three tags, handoff:any, and the narrow exception where a tagged handoff is the one case a memory may be read as an instruction rather than a fact, with the bounds the skill puts on it. Verified against hindsight-integrations/grok-bot on origin/main. * blog: reframe on cross-tool memory, put Grok Bot in the title Review feedback: the angle was wrong and the title did not name the product. The post now leads on a Bot reading the banks Claude Code, ChatGPT, Hermes and OpenClaw already wrote, with the discovery path from memory-context step 3 and the one-directional read rule as the spine. Routines and bot-to-bot handoffs are still covered, demoted to a section each rather than carrying the post. Adds the OAuth scope caveat: the grant reaches every bank in the authorised organisation, so read-only is a skill convention and not a server-side boundary. Cover retitled to match. * blog: correct the install section, the marketplace listing is pending Review feedback: we are not approved in the Grok Bot or Cursor marketplace yet, so the Connect apps path does not work for anyone. Replaces it with the two paths that do: the connect prompt for Grok Bot, and the local plugin folder for Cursor. Depends on #5465, which adds the connect prompt the post links to.
This was referenced Oct 14, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Grok Bot README and the integration docs page both told people to open Connect apps, search for Hindsight, and add it from the marketplace. The listing is still in review, so that path does not work for anyone today.
Flagged in review of #5461.
What changed
Both surfaces now say the listing is pending and document the two paths that work right now.
Grok Bot: a connect prompt. New
hindsight-integrations/grok-bot/connect-prompt.md, modelled on the Meta Muse one. Pasting it to a Bot gets Hindsight added as a custom connector, walks the OAuth sign-in, and then carries the same rules the skills carry:grok-bot::shared, and the matching banks fromlist_bankswhen the task touches the user's wider workhandoff:anyand the four things a handoff may never ask fordelete_bank,clear_memories,invalidate_memory,delete_documentordelete_mental_modelCursor: the local plugin folder.
~/.cursor/plugins/local, which is the path Cursor's own docs give for loading a plugin outside the marketplace. Clone, copy the directory, reload the window.Tests. New
tests/test_connect_prompt.py, matching the Meta Muse contract: the root cloud URL with no/mcp/, every required tool named, every destructive tool forbidden, no credentials in the text, and the README documenting the manual path. Adds a case for the handoff bounds.Verification
That is the full grok-bot suite, which includes the existing manifest and skill tests, so the marketplace submission checklist still passes.
Grepped both surfaces for any remaining claim that the plugin is installable from a marketplace. The only hits left are the "after the listing lands" paragraph, which is explicitly future tense, and the Development section's reference to the Cursor Marketplace submission checklist, which is accurate.
Note for the reviewer
The Cursor path is from Cursor's published docs. The Grok Bot path is not independently verified. The prompt asks the Bot to add a custom connector, which is the same approach Meta Muse uses against a different host. If Grok Bot does not expose custom connectors to users today, that section needs changing and I would rather hear it from someone who has tried it.
🤖 Generated with Claude Code