← Back to Skills Marketplace
vvoruganti

Long Term Memory with Honcho

by Vineeth Voruganti · GitHub ↗ · v1.0.4 · MIT-0
cross-platform ⚠ suspicious
876
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install honcho
Description
Install the @honcho-ai/openclaw-honcho plugin and run initial setup. Runs `openclaw plugins install`, `openclaw honcho setup` (which prompts for your API key...
README (SKILL.md)

Honcho Setup

Install the @honcho-ai/openclaw-honcho plugin. The plugin includes openclaw honcho setup, which handles API key configuration and migration of any legacy memory files to Honcho.

⚠️ DATA UPLOAD WARNING: openclaw honcho setup (run in Step 2) will offer to upload your workspace memory files (USER.md, MEMORY.md, IDENTITY.md, memory/, canvas/, SOUL.md, AGENTS.md, BOOTSTRAP.md, TOOLS.md) to an external API. HEARTBEAT.md is excluded. By default, data is sent to api.honcho.dev. For self-hosted instances, data is sent to your configured HONCHO_BASE_URL. The setup command will show exactly which files will be uploaded and ask for explicit confirmation before proceeding.

No local files are deleted, moved, or modified. Originals remain exactly in place.

Step 1: Install the Plugin

Install the Honcho plugin using the OpenClaw plugin system. Use this exact command — do not install @honcho-ai/sdk directly or use npm install in the workspace.

openclaw plugins install @honcho-ai/openclaw-honcho

Then enable it:

openclaw plugins enable openclaw-honcho

Verify the plugin loaded without errors. If the gateway logs show Cannot find module '@honcho-ai/sdk', install dependencies manually:

cd ~/.openclaw/extensions/openclaw-honcho && npm install

This is a known issue with the OpenClaw plugin installer not running dependency resolution for plugin packages.

Step 2: Run Setup

Run the setup command that ships with the plugin:

openclaw honcho setup

This command will:

  1. Prompt interactively for your Honcho API key
  2. Write configuration to ~/.openclaw/openclaw.json
  3. Scan for legacy memory files and offer to migrate them to Honcho

Follow the prompts. Migration is optional — if you have no legacy files or want to skip, you can skip the upload step.

For managed Honcho, you need an API key from https://app.honcho.dev. For self-hosted instances, set HONCHO_BASE_URL to your instance URL and the API key is optional.

Step 3: Restart the Gateway

openclaw gateway restart

Step 4: Confirm

Verify the plugin is active by checking gateway logs or running:

openclaw honcho status

Honcho memory is now active.

Ongoing behavior after setup: Once enabled, the plugin will persistently observe conversations in this workspace and send conversation data to api.honcho.dev (or your configured HONCHO_BASE_URL) to build and retrieve memory. This is ongoing network activity that continues across sessions. Memory is made available via honcho_recall, honcho_search, honcho_profile, and related tools. To stop this behavior, disable the plugin with openclaw plugins disable openclaw-honcho.

Security & Privacy Disclosure

This skill has been designed with transparency and safety as priorities. Below is a complete disclosure of what this skill does:

What This Skill Does

This skill runs three commands: openclaw plugins install, openclaw honcho setup, and openclaw gateway restart. The data upload and file access described below is performed by openclaw honcho setup, not by this skill directly.

Data Upload

  • uploaded_content: USER.md, MEMORY.md, IDENTITY.md, all files under memory/, all files under canvas/, SOUL.md, AGENTS.md, BOOTSTRAP.md, TOOLS.md — uploaded by openclaw honcho setup during migration
  • not_uploaded: HEARTBEAT.md — excluded by design, never read or uploaded
  • Where it goes: By default to api.honcho.dev (managed Honcho cloud service). For self-hosted instances, to your configured HONCHO_BASE_URL
  • User control: openclaw honcho setup always requires explicit interactive confirmation before any upload, even when HONCHO_API_KEY is pre-set in the environment. You will see the exact list of files and the destination URL
  • Purpose: Migrating file-based memory system to Honcho API for AI agent personalization and memory

File Modifications

  • Config written: openclaw honcho setup writes API key and config to ~/.openclaw/openclaw.json
  • Workspace files: Never modified — originals remain exactly in place
  • HEARTBEAT.md: Never read or uploaded — excluded by design

Credentials

  • HONCHO_API_KEY: Required only for managed Honcho (api.honcho.dev). Not required for self-hosted instances. Stored in ~/.openclaw/openclaw.json by the setup command.
  • No other credentials: This skill does not access, read, or transmit any other credentials or secrets

Network Access

  • Managed mode: Connects to api.honcho.dev (Honcho cloud service)
  • Self-hosted mode: Connects to your configured HONCHO_BASE_URL (e.g., http://localhost:8000)

Ongoing Behavior After Setup

  • Persistent observation: Once enabled, the plugin observes all conversations in the workspace and transmits conversation data to the configured Honcho endpoint on an ongoing basis
  • Network activity: Continues across sessions as long as the plugin is enabled — this is not a one-time migration
  • How to stop: Run openclaw plugins disable openclaw-honcho to stop all observation and network activity

Open Source

  • Honcho SDK: Open source at https://github.com/plastic-labs/honcho
  • Plugin code: Available at ~/.openclaw/extensions/openclaw-honcho after installation
  • This skill: You are reading the complete skill instructions - there is no hidden behavior
Usage Guidance
This plugin will upload many of your workspace memory files to an external API (api.honcho.dev by default) and then continuously send conversation data until you disable the plugin. That behavior is described in SKILL.md and requires interactive confirmation before uploads, but you should verify before installing: 1) Resolve the metadata mismatch — confirm whether node/npm and HONCHO_API_KEY are required (the SKILL.md says yes while the registry summary says no). 2) Inspect the plugin source (GitHub repo listed in SKILL.md / publisher) or the installed package under ~/.openclaw/extensions/openclaw-honcho before consenting to uploads. 3) Prefer running the setup in a disposable/test workspace first to see which files the tool proposes to upload. 4) If you cannot trust the managed endpoint, self-host Honcho (set HONCHO_BASE_URL) or decline migration. 5) Back up your local memory files before migration and check ~/.openclaw/openclaw.json after setup for stored keys. 6) If you do not want ongoing remote observation, do not enable the plugin or disable it with openclaw plugins disable openclaw-honcho after testing. If you want a safer recommendation, ask for the plugin's exact npm package name and repository URL so you (or an admin) can review the code before installing.
Capability Analysis
Type: OpenClaw Skill Name: honcho Version: 1.0.4 The 'honcho' skill installs a plugin that uploads a wide range of sensitive workspace files (including USER.md, IDENTITY.md, SOUL.md, and the entire memory/ and canvas/ directories) to an external cloud service (api.honcho.dev). While the SKILL.md documentation is transparent about this behavior and claims to require interactive user confirmation, the broad scope of data exfiltration and the persistent monitoring of all future conversations represent significant privacy and security risks. Files involved: SKILL.md, ~/.openclaw/openclaw.json.
Capability Assessment
⚠ Purpose & Capability
The SKILL.md describes exactly the expected capability: installing the @honcho-ai/openclaw-honcho plugin, migrating and uploading workspace memory files to api.honcho.dev (or a self-hosted HONCHO_BASE_URL), and then persistently observing conversations. That capability aligns with the described 'long term memory' purpose. However, the registry-level 'Requirements' section at the top of the submission says 'Required binaries: none' and 'Required env vars: none', while the SKILL.md metadata lists node/npm as required binaries and optional HONCHO_API_KEY and HONCHO_BASE_URL environment variables. This mismatch between top-level metadata and the SKILL.md is an incoherence you should resolve (either the registry metadata is incomplete or the SKILL.md is overstating requirements).
ℹ Instruction Scope
The runtime instructions explicitly instruct running: openclaw plugins install @honcho-ai/openclaw-honcho, openclaw honcho setup, and openclaw gateway restart. The setup command will scan for and offer to upload a large set of workspace files (USER.md, MEMORY.md, IDENTITY.md, memory/, canvas/, SOUL.md, AGENTS.md, BOOTSTRAP.md, TOOLS.md) to an external endpoint, and writes configuration to ~/.openclaw/openclaw.json. Upload behavior is explicit and requires interactive confirmation before sending data. The scope is consistent with migration-to-remote-memory, but the instructions involve highly sensitive data and ongoing network activity; ensure you review which files will be uploaded at the prompt before consenting.
ℹ Install Mechanism
This is an instruction-only skill (no install spec), so it instructs the user to use the OpenClaw plugin installer which will fetch & install the plugin package (likely from npm). The SKILL.md also documents a manual fallback: cd ~/.openclaw/extensions/openclaw-honcho && npm install. That fallback will run npm to install dependencies on disk (moderate risk — code from npm will be written/executed). The install mechanism is not a download from an arbitrary URL, but installing third-party plugin packages and their npm dependencies is inherent risk that should be audited if you do not trust the publisher.
ℹ Credentials
The SKILL.md declares HONCHO_API_KEY (optional for self-hosted, required for managed Honcho) and HONCHO_BASE_URL as expected environment settings for a memory service; requesting these is proportionate to the stated functionality. However, the registry summary earlier claimed no required env vars; that inconsistency should be resolved. The skill reads/writes ~/.openclaw/openclaw.json to store API keys/config — this is expected. No unrelated secrets are requested, but the net effect is that sensitive workspaces and conversation content will be sent to an external service if you consent.
ℹ Persistence & Privilege
always:false (not force-included) which is appropriate. The important behavior: after setup the plugin 'persistently observes conversations and transmits data to Honcho across sessions' until you disable it. That persistent observation and ongoing network activity increases privacy risk compared with single-shot tools. This is expected for a long-term-memory plugin, but you should treat it as an always-on data flow and explicitly disable the plugin if you no longer want remote memory.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install honcho
  3. After installation, invoke the skill by name or use /honcho
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.4
- BREAKING: Migration and setup flow now runs via openclaw honcho setup, not custom migration logic. - No workspace or memory files are deleted, moved, or modified—setup is non-destructive. - HEARTBEAT.md is now excluded from migration, as it is not memory. - Explicit interactive user confirmation is always required before any data upload, even if the API key is preset. - After setup, the plugin continuously observes and uploads conversation data to Honcho until disabled. - Plugin config is written to ~/.openclaw/openclaw.json; other credentials or workspace files remain untouched.
v1.0.0
Initial release of honcho-setup skill: migrate OpenClaw file-based memory to Honcho. - Installs the @honcho-ai/openclaw-honcho plugin for OpenClaw. - Detects legacy memory and configuration files (USER.md, MEMORY.md, IDENTITY.md, memory/, canvas/, SOUL.md, AGENTS.md, BOOTSTRAP.md, TOOLS.md, HEARTBEAT.md) in the workspace. - Requests explicit user confirmation before uploading sensitive workspace content to Honcho API (cloud or self-hosted). - Offers managed (api.honcho.dev, requires HONCHO_API_KEY) and self-hosted (custom HONCHO_BASE_URL, no key needed) modes. - Backs up files to a local archive before any removal; updates workspace docs to reference Honcho tools after migration. - Only uploads or deletes files after user confirmation and ensures connection with the Honcho instance before proceeding.
Metadata
Slug honcho
Version 1.0.4
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Long Term Memory with Honcho?

Install the @honcho-ai/openclaw-honcho plugin and run initial setup. Runs `openclaw plugins install`, `openclaw honcho setup` (which prompts for your API key... It is an AI Agent Skill for Claude Code / OpenClaw, with 876 downloads so far.

How do I install Long Term Memory with Honcho?

Run "/install honcho" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Long Term Memory with Honcho free?

Yes, Long Term Memory with Honcho is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Long Term Memory with Honcho support?

Long Term Memory with Honcho is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Long Term Memory with Honcho?

It is built and maintained by Vineeth Voruganti (@vvoruganti); the current version is v1.0.4.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments