# Honcho Grok Bot

Conventions for using Honcho memory as a Grok Bot.

- Repository: https://github.com/plastic-labs/honcho (7877 stars)
- Category: Engineering
- License: AGPL-3.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add plastic-labs/honcho --skill honcho-grok-bot -g -a claude-code -y`
Codex: `npx skills add plastic-labs/honcho --skill honcho-grok-bot -g -a codex -y`
Cursor: `npx skills add plastic-labs/honcho --skill honcho-grok-bot -g -a cursor -y`
Gemini CLI: `npx skills add plastic-labs/honcho --skill honcho-grok-bot -g -a gemini-cli -y`

## Description

Conventions for using Honcho memory as a Grok Bot. Apply whenever you are a Grok Bot (an xAI or Cursor Bot with its own cloud computer) and Honcho is connected, together with the honcho-memory skill. Covers how each Bot names its peer and sessions, how several Bots on one account share the user's memory, group chats, routines, and per-turn logging without hooks.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Honcho for Grok Bots

Grok Bot loads only two parts of this plugin: the Honcho MCP server and the
skills. There are no lifecycle hooks, so nothing is recorded unless you record
it. Apply the `honcho-memory` skill for the loop and use the conventions below
so that every Bot on the account writes to Honcho the same way.

## Identity

- **The user** is the account owner. Use the `user_peer` stored in the
  workspace metadata, exactly as the `honcho-memory` skill describes. Every Bot
  on the account shares that one peer; that is what makes the user's memory
  continuous across Bots.
- **You** are one peer per Bot: your Bot name in kebab-case (`nori`,
  `research-bot`). Do not create a peer per conversation and do not reuse
  another Bot's peer. If your name changes, keep the old peer id and store the
  display name with `set_metadata` on your peer.
- **Other Bots** in a group chat are their own peers, named the same way.

## Sessions

Pick the first that applies:

1. **A group chat** (more than one Bot, or several people): `group-<group-name>-<id>`
   when the chat has a stable id you can read, otherwise
   `group-<group-name>-<YYYY-MM-DD>`. Add the user and every participating Bot
   as peers. Each Bot records its own messages (see "Logging each turn").
2. **A direct conversation with a stable id you can read**: `<bot>-conv-<id>`.
3. **A direct chat without an id**: one session per Bot per day,
   `<bot>-chat-<YYYY-MM-DD>` in the user's time zone.
4. **A routine run** (scheduled or event-triggered work with no user in the
   loop): `<bot>-routine-<routine-name>-<YYYY-MM-DD>`. Record what you did as
   your own messages. Do not record user messages you did not receive.

Ids may contain only letters, digits, `_` and `-`, so lowercase names and
replace anything else with `-`.

Stay in the session you picked for the whole conversation, even when the topic
changes. Honcho reasons over and summarizes each session as one piece.

## Logging each turn

The rest: https://github.com/plastic-labs/honcho/blob/HEAD/integrations/cursor/skills/honcho-grok-bot/SKILL.md