Skip to content

✨ agents: disable CLI auto-memory by default and add clear_memory_on_kick #17032

Closed

Description

@clubanderson

Summary

Even with per-agent CLI homes, each agent still accumulates persistent CLI auto-memory across kicks: Claude Code's ~/.claude/projects/<slug>/memory/MEMORY.md, Codex's $CODEX_HOME/memories, Copilot CLI's per-agent memory, Gemini's GEMINI.md. Hive never disables the feature and never clears it. ClearOnKick (src/crux/agent/manager_kick.go:296-304) only sends /clear, which resets the conversation.

Greg Hunt (2026-11-05 community meeting): "I absolutely hate the agentic memory that's built into Claude CLI or Codex CLI. I had to go turn it off in my hive … they make inferences and add things to your memories that are false sometimes or that are off of a one-off." Doug: "there was a one-off and all of a sudden it's asking if it wants to do that one-off every single time."

A hive agent is a lane worker that should start every kick from the kick prompt + beads + the knowledge primer — not from whatever it inferred last Tuesday.

Proposal

New fleet-level block, encoded under agents: beside session_recycle (AgentsSessionRecycle, src/crux/config/agent_config.go:134-137):

agents:
  cli_memory:
    auto_memory: false     # default false: seed each CLI's "disable auto-memory" setting
    clear_on_kick: false   # default false: wipe the per-agent memory store before every kick
  • auto_memory: false (default) — seed the documented per-CLI disable: Claude Code's autoMemoryEnabled: false in the settings seed (manager_homes.go inferenceSettingsSeed for inference agents; ensureClaudeRemoteControlDefault for interactive agents); Codex config.toml [features] memories = false merged like codexConfigWithUpdateCheckDisabled; Copilot CLI / Gemini equivalents where one exists. When auto_memory: true, nothing is seeded and an operator's explicit setting wins.
  • clear_on_kick: true — in deliverKickLocked next to /clear, remove that agent's ~/.claude/projects/*/memory, $CODEX_HOME/memories, Copilot memory dir and Gemini memory file. Belt-and-braces for operators who want memory on but scoped to one kick.

Settings parity (internal/settingsparity) and the operator reference need the new leaves. Depends on the per-agent home isolation issue so a wipe never touches another agent's state.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 7, 2026
  2. hivecommons-hive commented on Nov 7, 2026

    @hivecommons-hive
    Contributor

    🔓 Claim by @Karibhou released (lease revoked).

    Claim history
    • 2026-11-07 18:21 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-07 18:21 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-07 18:36 UTC — released by Karibhou (contributor; lease revoked)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions