Grok Bot Integration

Persistent memory for multi-agent Grok Bot teams

One dedicated Grok Bot seat runs local gnosys so your team never blocks on the CLI. Shared SQLite brain, project-scoped memory, and SendToAgent messaging keep every agent in sync.

Get Started Read Full Docs
Architecture

How it works

One Grok Bot seat named "Gnosys" runs the CLI directly. Sibling Grok Bots message that seat through SendToAgent for RECALL, QUERY, SAVE, and REINFORCE operations. No MCP attachment is required on the Grok Bot computer.

Sibling Grok Bots
Code, debug, docs
Gnosys Grok Bot Seat
Runs gnosys via Shell
dedicated operator
~/.gnosys/gnosys.db
SQLite brain on operator's computer
local disk only
No cloud storage, no MCP on Grok Bot machines

The live database stays on the operator's local disk. Do not put it on iCloud, Dropbox, or SMB. Sibling Grok Bots never attach gnosys-mcp directly; they message the dedicated seat instead.

Installation

Set up in three steps

Install gnosys, initialize your first project, and configure the dedicated Grok Bot seat. Bare install: the packaged Gnosys bot ships with skill gnosys-bot-operating-system only.

1

Install gnosys (once per machine)

Requires Node.js 20.12 or newer. Install globally, then optionally configure LLM providers for advanced features.

npm install -g gnosys
gnosys setup
which gnosys && gnosys --version

Optional: gnosys setup configures LLM providers, API keys, and IDE integrations. MCP features work without a provider; configure one only for synthesis or multimodal tasks.

2

Initialize your first project

Navigate to your project directory (or your Grok Bot working folder) and register it with gnosys.

cd "/absolute/path/to/project"
gnosys init

Or specify the directory and name explicitly:

gnosys init -d "/abs/path" -n "Project Name"

Recommended first project: Your Grok Bot ops folder or working directory, named "Grok Bot".

3

Bootstrap the Gnosys Grok Bot seat

Install or share the packaged Gnosys bot and note its current agent ID. Confirm the CLI and brain are accessible, then update sibling Grok Bots to message this seat.

  • Install/share the Gnosys bot; note its current agent ID (never a stale template ID)
  • Confirm CLI + brain; init your ops project
  • Patch sibling bots: recall sends to Gnosys seat via SendToAgent; durable decisions SendToAgent SAVE to the Gnosys seat (only that seat runs gnosys add-structured)
  • Optional: migrate that install's own agent memories only; never another operator's data; skip secrets
  • Local-exec / Shell must be allowed for the Gnosys seat on the machine holding gnosys
Message protocol for sibling agents

Sibling Grok Bots SendToAgent these messages to the Gnosys seat. Only the Gnosys seat runs gnosys CLI commands.

  • RECALL/QUERY: project (absolute cwd or federated), query, author
  • SAVE: project, title, category, content, relevance, author, tags {"agent":"SeatName"}
  • REINFORCE: memory id + useful | not_relevant | outdated
  • The Gnosys seat translates SAVE to gnosys add-structured (no freeform gnosys add). add-structured has no -d flag; the seat must cd to the project directory first.
Benefits

Why this pattern works

Persistent shared memory, no CLI contention, project-scoped context, and bare-install simplicity.

No CLI blocking

One dedicated seat owns the gnosys CLI and brain. Sibling Grok Bots never compete for local access or wait on initialization.

Project-scoped memory

Memories are scoped to registered projects in the central SQLite DB. FTS5 keyword search and optional embeddings keep context relevant.

SendToAgent coordination

Sibling agents send RECALL, QUERY, SAVE, and REINFORCE messages to the Gnosys seat. No MCP attachment or gnosys CLI required on sibling machines.

Local-first data

The live SQLite database stays on the operator's local disk. No cloud storage concurrency, no iCloud/Dropbox corruption risk.

Bare install

The packaged Gnosys bot ships with skill gnosys-bot-operating-system only. No prior memories, no stale project context, no operator-specific paths.

Author + tag tracking

Each write includes author and tags {"agent":"SeatName"}. Trace who contributed what, filter by seat, and manage multi-agent knowledge.

Ready to give your Grok Bot team a shared brain?

Install gnosys on your machine, init your ops project, and bootstrap the dedicated Gnosys seat. Open source, MIT licensed, local-first.

Get Started Full Documentation