honcho/docs/v3/documentation/introduction/vibecoding.mdx

101 lines
3.5 KiB
Plaintext

---
title: "Agentic Development"
icon: "wand-magic-sparkles"
description: "Let your coding agent help you integrate Honcho"
sidebarTitle: "Agentic Development"
keywords: ['vibecoding', 'vibe coding', 'ai coding', 'autonomous development']
---
Building a Honcho integration? These tools let your AI assistant do the scaffolding while you focus on the product.
## Agent Skills
Install the Honcho skill in Claude Code, Cursor, Windsurf, or any agent:
<CodeGroup>
```bash Install via npx (Recommended)
npx skills add plastic-labs/honcho
```
```bash Install as Claude Skill Manually
curl -o ~/.claude/skills/honcho-integration.md https://raw.githubusercontent.com/plastic-labs/honcho/main/docs/SKILL.md
```
</CodeGroup>
### `/honcho-integration`
**For new integrations.** Guided integration for adding Honcho to an existing Python or TypeScript codebase. The skill:
1. **Explores your codebase** to understand your language, framework, and existing AI/LLM integrations
2. **Interviews you** about which entities should be peers, your preferred integration pattern, and session structure
3. **Implements the integration** based on your answers—installing the SDK, creating peers, configuring sessions, and wiring up the chat endpoint
4. **Verifies the setup** to ensure everything is configured correctly
### `/migrate-honcho-py` / `/migrate-honcho-ts`
**For SDK upgrades.** Migrates code from v1.6.0 to v2.0.0 (required for Honcho 3.0.0+). Use when upgrading the SDK or seeing errors about removed APIs like `observations`, `Representation`, `.core`, or `get_config`.
Both skills handle: terminology changes (`Observation` → `Conclusion`), `Representation` class removal, method renames, and streaming API updates.
| Python | TypeScript |
|--------|------------|
| `/migrate-honcho-py` | `/migrate-honcho-ts` |
| `AsyncHoncho` → `.aio` accessor | `@honcho-ai/core` removal |
| | `snake_case` → `camelCase` |
---
## MCP Server
Give your coding agent (or any MCP client) direct access to Honcho during development.
### Bespoke Flow (High-Level)
For agents that just need memory without managing sessions:
| Tool | What it does |
| --- | --- |
| `start_conversation` | Creates a peer + session in one call |
| `add_turn` | Logs a user/assistant exchange |
| `get_personalization_insights` | Retrieves learned context about the peer |
### General Tools (Full API)
For fine-grained control over the Honcho data model:
- **Workspace:** `inspect_workspace`, `list_workspaces`, `search_workspace`, `get/set_workspace_metadata`
- **Peers:** `create_peer`, `list_peers`, `chat`, `get_peer_card`, `get_peer_context`, `get_representation`, `search_peer_messages`
- **Sessions:** `create_session`, `list_sessions`, `clone_session`, `add_messages`, `get_session_context`, `inspect_session`, `get_session_summaries`
- **Conclusions:** `list_conclusions`, `query_conclusions`, `create_conclusions`, `delete_conclusion`
- **System:** `schedule_dream`, `get_queue_status`
### Setup
Connect via SSE or Streamable HTTP transport:
```
URL: https://mcp.honcho.dev/mcp
Headers:
Authorization: Bearer <your-api-key>
X-Honcho-User-Name: <user-identifier>
```
Works with Claude Desktop, Cursor, Codeium, and any MCP-compatible client.
---
## CLI
Quick commands for local development and testing.
Coming soon.
---
## LLM-Friendly Docs
These docs are designed to be easily consumable by LLMs. Each page has a button that lets you copy the page as Markdown or paste directly into ChatGPT or Claude.
We follow the llms.txt standard:
- [llms.txt](/llms.txt)
- [llms-full.txt](/llms-full.txt)