Abigail/minor fix (#351)

* fix: updating vibecoding

* fix: brooken links
This commit is contained in:
ajspig 2026-01-27 11:18:41 -05:00 committed by GitHub
parent a4a341e8b5
commit ac49a7cedb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
11 changed files with 49 additions and 43 deletions

View File

@ -10,7 +10,7 @@ Advanced features give you fine-grained control over Honcho's behavior and imple
## Configuration & Monitoring
- [Queue Status](/v3/documentation/features/advanced/queue-status) - Monitor background processing and reasoning tasks
- [Configuration](/v3/documentation/features/advanced/toggle-reasoning) - Configure reasoning models and behavior
- [Configuration](/v3/documentation/features/advanced/reasoning-configuration) - Configure reasoning models and behavior
- [Summarizer](/v3/documentation/features/advanced/summarizer) - Automatic session summarization
## Querying & Filtering

View File

@ -1,7 +1,7 @@
---
title: "AI-Powered Honcho Setup"
icon: "wand-magic-sparkles"
description: "Universal starter prompt and Claude Code skill for building with Honcho"
description: "Agent skills and starter prompt for building with Honcho"
sidebarTitle: 'Vibecoding Setup'
---
@ -14,38 +14,44 @@ We follow the llms.txt standard. There are both an llms.txt and llms-full.txt av
---
## Claude Code Skill
## Agent Skills
If you're using [Claude Code](https://docs.anthropic.com/en/docs/claude-code/overview), you can install the Honcho integration skill for a guided, interactive setup experience. The skill will explore your codebase, ask targeted questions about your integration needs, and implement Honcho step by step.
### Installation
We provide agent skills for coding assistants like Claude Code, Cursor, Windsurf, and others.
<CodeGroup>
```bash Global Installation (all projects)
# Add to your global skills directory
curl -o ~/.claude/skills/honcho-integration.md https://raw.githubusercontent.com/plastic-labs/honcho/main/docs/SKILL.md
```bash Install via npx (Recommended)
npx skills add plastic-labs/honcho
```
```bash Project-specific Installation
# Add to your project's .claude directory
mkdir -p .claude/skills
curl -o .claude/skills/honcho-integration.md https://raw.githubusercontent.com/plastic-labs/honcho/main/docs/SKILL.md
```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>
### Usage
### Available Skills
Once installed, invoke the skill in Claude Code:
#### honcho-integration
```
/honcho-integration
```
**For new integrations.** This skill helps you add Honcho to an existing Python or TypeScript codebase. It provides a guided, interactive experience:
The skill will:
1. **Explore your codebase** to understand your language, framework, and existing AI/LLM integrations
2. **Interview you** about which entities should be peers, your preferred integration pattern, and session structure
3. **Implement the integration** based on your answers
4. **Verify the setup** to ensure everything is configured correctly
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
Invoke with `/honcho-integration` in your coding agent.
#### 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` |
---

View File

@ -879,7 +879,7 @@ If `created_at` is not provided, messages will use the server's current timestam
### Metadata and Filtering
See [Using Filters](/v3/guides/using-filters) for more examples on how to use filters.
See [Using Filters](/v3/documentation/features/advanced/using-filters) for more examples on how to use filters.
<CodeGroup>
```python Python

View File

@ -237,7 +237,7 @@ and Bob. We:
As soon as you save a message in Honcho, it will start to reason about it to
pull out insights and develop a profile of the user. This is the default
behavior and can be toggled off via [the configuration](/v3/documentation/core-concepts/configuration).
behavior and can be toggled off via [the configuration](/v3/documentation/features/advanced/reasoning-configuration).
## Next Steps

View File

@ -53,7 +53,7 @@ This feature is illustrated in the graphic below:
We can enable local representation for a `Peer` by setting `observe_others=True`.
This is shown in the [Configure
Reasoning](/v3/documentation/core-concepts/configuration) page.
Reasoning](/v3/documentation/features/advanced/reasoning-configuration) page.
Now if we used Bob's local representation of Alice then Bob would only get
insights on what they've seen Alice say to them.

View File

@ -97,7 +97,7 @@ results = storage.search("query", filters={
})
```
For the full filter syntax including logical operators (AND, OR, NOT), comparison operators, and metadata filtering, see the [Using Filters](https://docs.honcho.dev/v3/documentation/core-concepts/features/using-filters) documentation.
For the full filter syntax including logical operators (AND, OR, NOT), comparison operators, and metadata filtering, see the [Using Filters](https://docs.honcho.dev/v3/documentation/features/advanced/using-filters) documentation.
<Note>
For comprehensive details about CrewAI's memory system, see the [official CrewAI Memory documentation](https://docs.crewai.com/en/concepts/memory).
@ -282,13 +282,13 @@ Now that you have a working CrewAI integration with Honcho, you can:
<Card title="Honcho Architecture" icon="sitemap" href="/v3/documentation/core-concepts/architecture">
Understand Honcho's peer-based model and core primitives
</Card>
<Card title="Get Context" icon="messages" href="/v3/documentation/core-concepts/features/get-context">
<Card title="Get Context" icon="messages" href="/v3/documentation/features/get-context">
Learn about retrieving and formatting conversation context
</Card>
<Card title="Dialectic API" icon="brain" href="/v3/documentation/core-concepts/features/dialectic">
<Card title="Chat API" icon="brain" href="/v3/documentation/features/chat">
Query `peer` representations for deeper understanding
</Card>
<Card title="LangGraph Integration" icon="diagram-project" href="/v3/integrations/langgraph">
<Card title="LangGraph Integration" icon="diagram-project" href="/v3/guides/integrations/langgraph">
Build stateful agents with LangGraph and Honcho
</Card>
</CardGroup>

View File

@ -227,7 +227,7 @@ const graph = new StateGraph(StateAnnotation)
### Understanding get_context()
The [`get_context()`](/v3/documentation/core-concepts/features/get-context) method retrieves comprehensive conversation context and formats it for your LLM. It automatically:
The [`get_context()`](/v3/documentation/features/get-context) method retrieves comprehensive conversation context and formats it for your LLM. It automatically:
- **Manages conversation history** - Tracks all messages and determines what's relevant
- **Respects token limits** - Stays within context window constraints without manual counting
@ -248,7 +248,7 @@ That's it. Call `session.get_context().to_openai(assistant)` and you get properl
</Tip>
<Note>
For more details on all available parameters, see [`get_context() documentation`](/v3/documentation/core-concepts/features/get-context)
For more details on all available parameters, see [`get_context() documentation`](/v3/documentation/features/get-context)
</Note>
## Chat Loop
@ -354,10 +354,10 @@ Now that you have a working LangGraph integration with Honcho, you can:
## Related Resources
<CardGroup cols={2}>
<Card title="Get Context" icon="messages" href="/v3/documentation/core-concepts/features/get-context">
<Card title="Get Context" icon="messages" href="/v3/documentation/features/get-context">
Learn more about retrieving and formatting conversation context
</Card>
<Card title="MCP Integration" icon="star-of-life" href="/v3/integrations/mcp">
<Card title="MCP Integration" icon="star-of-life" href="/v3/guides/integrations/mcp">
Use Honcho in Claude Desktop with MCP
</Card>
</CardGroup>

View File

@ -259,14 +259,14 @@ Reference the [API Comparison](#api-comparison) to replace your Mem0 API calls w
Mem0 requires manual assembly of context from `search()` results. Honcho's `session.get_context()` returns a ready-to-use `SessionContext` object with built-in token limits, auto-included summaries, and format helpers (`.to_openai()`, `.to_anthropic()`).
<Card title="Get Context" icon="window-restore" href="../../documentation/core-concepts/features/get-context">
<Card title="Get Context" icon="window-restore" href="../../documentation/features/get-context">
Learn more about token-optimized context retrieval
</Card>
Mem0's `search()` returns basic vector, semantic, or raw memory matches. Honcho's `peer.chat()` enables your agent to *reason* about what it knows—returning synthesized natural language insights with streaming support and scoped queries.
<Card title="Dialectic Endpoint" icon="brain" href="../../documentation/core-concepts/features/dialectic-endpoint">
<Card title="Chat Endpoint" icon="brain" href="../../documentation/features/chat">
Learn more about inference-powered queries
</Card>
@ -285,7 +285,7 @@ Additional features with **no Mem0 equivalent**:
<Card title="Architecture" icon="rocket" href="../../documentation/core-concepts/architecture">
Understand peers and sessions
</Card>
<Card title="Dialectic API" icon="brain" href="../../documentation/core-concepts/features/dialectic-endpoint">
<Card title="Chat API" icon="brain" href="../../documentation/features/chat">
Inference responses
</Card>
<Card title="Guides" icon="book" href="../../guides/overview">

View File

@ -16,10 +16,10 @@ Each guide focuses on a specific use case with practical examples. The goal is t
Quick integration guides to get up and running:
<CardGroup cols={2}>
<Card title="MCP Integration" icon="link" href="/v3/integrations/mcp">
<Card title="MCP Integration" icon="link" href="/v3/guides/integrations/mcp">
Get Honcho running with a single prompt in Claude Code
</Card>
<Card title="LangGraph" icon="diagram-project" href="/v3/integrations/langgraph">
<Card title="LangGraph" icon="diagram-project" href="/v3/guides/integrations/langgraph">
Add persistent memory and theory of mind to your LangGraph agents
</Card>
</CardGroup>

View File

@ -42,7 +42,7 @@ Once a `Message` is saved in Honcho, it will kick off a background task that
looks at the new data to generate insights about the `Peer` that sent the `Message`
This is the default behavior of Honcho and can be turned off by [configuring the
Peer or Session](/v3/documentation/core-concepts/configuration)
Peer or Session](/v3/documentation/features/advanced/reasoning-configuration)
This pattern of having a Peer, Session, and Messages is highly flexible and
works for many different use cases and agent setups. Some use cases may only

View File

@ -259,14 +259,14 @@ Reference the [API Comparison](#api-comparison) to replace your Mem0 API calls w
Mem0 requires manual assembly of context from `search()` results. Honcho's `session.get_context()` returns a ready-to-use `SessionContext` object with built-in token limits, auto-included summaries, and format helpers (`.to_openai()`, `.to_anthropic()`).
<Card title="Get Context" icon="window-restore" href="../../documentation/core-concepts/features/get-context">
<Card title="Get Context" icon="window-restore" href="../../documentation/features/get-context">
Learn more about token-optimized context retrieval
</Card>
Mem0's `search()` returns basic vector, semantic, or raw memory matches. Honcho's `peer.chat()` enables your agent to *reason* about what it knows—returning synthesized natural language insights with streaming support and scoped queries.
<Card title="Dialectic Endpoint" icon="brain" href="../../documentation/core-concepts/features/dialectic-endpoint">
<Card title="Chat Endpoint" icon="brain" href="../../documentation/features/chat">
Learn more about inference-powered queries
</Card>
@ -285,7 +285,7 @@ Additional features with **no Mem0 equivalent**:
<Card title="Architecture" icon="rocket" href="../../documentation/core-concepts/architecture">
Understand peers and sessions
</Card>
<Card title="Dialectic API" icon="brain" href="../../documentation/core-concepts/features/dialectic-endpoint">
<Card title="Chat API" icon="brain" href="../../documentation/features/chat">
Inference responses
</Card>
<Card title="Guides" icon="book" href="../../guides/overview">