docs_skill

This skill helps you integrate Honcho into Python or TypeScript apps to enable memory-driven agents and seamless session management.
  • Python

358

GitHub Stars

6

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill plastic-labs/honcho --skill docs

  • bun.lock239.0 KB
  • docs.json23.0 KB
  • favicon.svg3.5 KB
  • package.json504 B
  • README.md1.1 KB
  • SKILL.md14.0 KB

Overview

This skill integrates Honcho memory and social cognition into Python or TypeScript codebases to build stateful, personalized AI agents. It guides setup of the SDK, peer and session modeling, message storage, and recommended patterns for querying user context. Use it to add continual learning, representations, and context-aware responses to existing chat or agent systems.

How this skill works

The skill inspects your repo to detect language, frameworks, existing LLM integrations, session handling, and message flow. After a short interview to map peers, integration pattern, and session logic, it provides concrete implementation code: initializing the Honcho client, creating peers, configuring sessions, adding messages, and wiring the dialectic chat endpoint as a tool or pre-fetch step. It also includes verification and checklist steps to ensure messages and workspace configuration are correct.

When to use it

  • Adding long-term user memory and personalization to chatbots or agents
  • Integrating Honcho SDK into Python (FastAPI, LangChain) or TypeScript (Express, Next.js) projects
  • Implementing function-calling or tool-call patterns for agent access to user context
  • Mapping existing conversation/session models to Honcho sessions
  • Ensuring consistent message storage and workspace configuration across the app

Best practices

  • Use a single workspace ID for the entire application to centralize memory
  • Create peers for all entities (human users and AI assistants); set AI peers observe_me=false
  • Choose the integration pattern that fits your architecture: tool-call for agents, pre-fetch for simpler flows, or context() for LLM-ready history
  • Always call add_messages() after exchanges so Honcho can build user representations
  • Document and surface HONCHO_API_KEY and workspace ID in environment configuration

Example use cases

  • Expose Honcho as an OpenAI function/tool so an agent queries user context on-demand during reasoning
  • Pre-fetch targeted user attributes (communication style, goals, preferences) to build a system prompt before each LLM call
  • Use session.context() to produce LLM-formatted conversation history with summaries for long threads
  • Add multi-peer sessions for group chats with per-peer observation settings
  • Stream Honcho chat responses for real-time UX while feeding exchanges back into Honcho

FAQ

Use one workspace per application or product. Avoid splitting a single app across multiple workspaces; manage environments via workspace naming or environment flags.

Should Honcho model my AI assistants?

No—create peers for AI assistants but set observe_me=false unless you explicitly want Honcho to learn about the AI's behavior.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
docs skill by plastic-labs/honcho | VeilStrat