Installation

Install Honeycomb on your operating system, then connect it to the coding assistants you already use. Each path lists what you need first, the exact command, how to check it worked, and where to go if something fails.

Installation

Related:

#Before you start

You do not need Node, npm, a database, or any other setup. The one-command installer detects what is missing and installs it for you, including a pinned version of Node if you do not already have one.

What the installer actually needs:

A terminal (Terminal on macOS, any shell on Linux, PowerShell on Windows).
Permission to install a global command. If a step needs elevation it cannot get, the installer stops cleanly and prints the exact command to run by hand. It never leaves a half-finished state.
A browser, because setup finishes in a dashboard that opens itself. The terminal is only the doorway.

Running both Honeycomb and Hivemind on one machine is not supported. If you already use Hivemind, the dashboard notices and offers to move you over cleanly. Let it handle the switch rather than running both.

#Install per operating system

The front door is a single line. Paste the one for your system.

#macOS

curl -fsSL https://get.theapiary.sh | sh

The installer detects whether Node and npm are present, installs a pinned version if not, installs the @legioncodeinc/honeycomb package globally, brings up the local helper, and opens the dashboard in your browser.

Verify it installed:

honeycomb status

You should see the helper reported as running and reachable. If honeycomb is reported as "command not found" right after install, see Troubleshooting: the honeycomb command is not found.

#Linux

curl -fsSL https://get.theapiary.sh | sh

The Linux path is the same as macOS. The installer uses the same detect-then-install approach for Node and npm.

Verify it installed:

honeycomb status

#Windows (PowerShell)

irm https://get.theapiary.sh/install.ps1 | iex

Run this in PowerShell, not the legacy Command Prompt. The installer performs the same steps as the macOS and Linux path, adapted for Windows.

Verify it installed:

honeycomb status

#Prefer to read the script first?

You do not have to pipe a script you have not seen. Visit get.theapiary.sh in a browser. The site serves an inspect-before-piping page and publishes a SHA256SUMS checksum file, so you can review the script and verify its checksum before running it.

#Finish setup in the dashboard

When the installer finishes, it opens the dashboard in your browser. This is the real starting point.

Click First time setup.
The page shows a short code and opens a tab where you approve it. If you do not have a Deep Lake account yet, you can create a free one here. You never copy a code out of the terminal.
When you approve, the same dashboard lights up its connected views. Nothing to restart, no second tab.

If the dashboard does not open on its own, the installer prints the local address for you to open by hand. See Troubleshooting: the dashboard did not open.

#Connect your coding assistants

Once you are signed in, plug Honeycomb underneath the assistants you have installed so it captures and recalls automatically as you work:

honeycomb setup

This detects every supported assistant present on your machine and wires each one. It is safe to run again any time, for example after you install a new tool. A re-run only writes where something actually changed, so it never triggers a re-trust prompt for a tool that was already wired.

Verify the wiring:

honeycomb status

To wire a single assistant instead of all detected ones:

honeycomb connect <assistant>

To reverse Honeycomb's changes for one assistant, or for every detected assistant when no name is given:

honeycomb uninstall <assistant>

Uninstall removes only the changes Honeycomb made. It leaves your other settings and any third-party wiring untouched.

#Install per coding assistant

Honeycomb supports six assistants at once: Claude Code, Cursor, Codex, Hermes, pi, and OpenClaw. A memory written from one is recalled by the others. You do not install Honeycomb separately for each; you run honeycomb setup once and it wires every assistant it detects. The notes below explain how each one connects and how to confirm it.

An assistant counts as "detected" when its own config folder exists on your machine. If honeycomb setup does not wire an assistant you expected, that usually means the assistant itself is not installed where Honeycomb looks. See Troubleshooting: an assistant is not connecting.

#Claude Code

Prerequisite: Claude Code installed.
Command: honeycomb setup (or honeycomb connect claude-code).
How it connects: Honeycomb registers its plugin and lifecycle hooks, and registers its memory tools so the assistant can ask for memory directly.
Verify: honeycomb status shows Claude Code as wired and healthy.

#Cursor

Prerequisite: Cursor installed.
Command: honeycomb setup (or honeycomb connect cursor).
How it connects: Honeycomb wires Cursor's lifecycle hooks, installs a first-party editor extension, and registers its memory tools.
Verify: honeycomb status shows Cursor as wired and healthy.

#Codex

Prerequisite: Codex installed.
Command: honeycomb setup (or honeycomb connect codex).
How it connects: Honeycomb wires Codex's lifecycle hooks and registers its memory tools. With Codex, the recalled context is shown to you as well as the assistant.
Verify: honeycomb status shows Codex as wired and healthy.

#Hermes

Prerequisite: Hermes installed.
Command: honeycomb setup (or honeycomb connect hermes).
How it connects: Honeycomb installs a skill plus shell hooks and registers its memory tools. Hermes shows a short note that the memory tools are available.
Verify: honeycomb status shows Hermes as wired and healthy.

#pi

Prerequisite: pi installed.
Command: honeycomb setup (or honeycomb connect pi).
How it connects: Honeycomb installs a managed extension and adds a Honeycomb block to your AGENTS.md. Recall is on demand, and context comes from that block.
Verify: honeycomb status shows pi as wired and healthy.

#OpenClaw

Prerequisite: OpenClaw installed.
Command: honeycomb setup (or honeycomb connect openclaw).
How it connects: Honeycomb installs its native extension and connector and registers its memory tools. Capture is batched at the end of each agent run.
Verify: honeycomb status shows OpenClaw as wired and healthy.

#Confirm your first capture and recall

With at least one assistant wired, prove the round trip:

honeycomb remember "we deploy from the release branch, never from main"
honeycomb recall "how do we deploy"

If recall returns your note, you are fully installed. For a guided first run from here, see Getting started. If recall comes back empty, see Troubleshooting: recall returns nothing.

#Updating and removing

Update everything (the command, the helper, and the assistant bundles):
```
honeycomb update
```
Remove Honeycomb's wiring from your assistants without touching anything else:
```
honeycomb uninstall
```

#What next

Walk through your first session in Getting started.
Learn the day-to-day flow in Everyday use.
Hit a snag? Go straight to Troubleshooting.