fix: links
This commit is contained in:
vintro
parent
1dc17afdcf
commit
69f823aed1
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/keys
|
||||
openapi: post /v2.6.0-alpha/keys
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/sessions/{session_id}/messages/
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/messages/
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/sessions/{session_id}/messages/upload
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/messages/upload
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/sessions/{session_id}/messages/{message_id}
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/messages/{message_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/sessions/{session_id}/messages/list
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/messages/list
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: put /v2/workspaces/{workspace_id}/sessions/{session_id}/messages/{message_id}
|
||||
openapi: put /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/messages/{message_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/observations
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/observations
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: delete /v2/workspaces/{workspace_id}/observations/{observation_id}
|
||||
openapi: delete /v2.6.0-alpha/workspaces/{workspace_id}/observations/{observation_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/observations/list
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/observations/list
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/observations/query
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/observations/query
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/peers/{peer_id}/chat
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/peers/{peer_id}/chat
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/peers
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/peers
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/peers/{peer_id}/card
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/peers/{peer_id}/card
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/peers/{peer_id}/context
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/peers/{peer_id}/context
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/peers/list
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/peers/list
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/peers/{peer_id}/sessions
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/peers/{peer_id}/sessions
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/peers/{peer_id}/representation
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/peers/{peer_id}/representation
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/peers/{peer_id}/search
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/peers/{peer_id}/search
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: put /v2/workspaces/{workspace_id}/peers/{peer_id}/card
|
||||
openapi: put /v2.6.0-alpha/workspaces/{workspace_id}/peers/{peer_id}/card
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: put /v2/workspaces/{workspace_id}/peers/{peer_id}
|
||||
openapi: put /v2.6.0-alpha/workspaces/{workspace_id}/peers/{peer_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/sessions/{session_id}/peers
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/peers
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/sessions/{session_id}/clone
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/clone
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: delete /v2/workspaces/{workspace_id}/sessions/{session_id}
|
||||
openapi: delete /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/sessions
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/sessions/{session_id}/peers/{peer_id}/config
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/peers/{peer_id}/config
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/sessions/{session_id}/context
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/context
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/sessions/{session_id}/peers
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/peers
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/sessions/{session_id}/summaries
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/summaries
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/sessions/list
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions/list
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: delete /v2/workspaces/{workspace_id}/sessions/{session_id}/peers
|
||||
openapi: delete /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/peers
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/sessions/{session_id}/search
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/search
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/sessions/{session_id}/peers/{peer_id}/config
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/peers/{peer_id}/config
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: put /v2/workspaces/{workspace_id}/sessions/{session_id}/peers
|
||||
openapi: put /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/peers
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: put /v2/workspaces/{workspace_id}/sessions/{session_id}
|
||||
openapi: put /v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: delete /v2/workspaces/{workspace_id}/webhooks/{endpoint_id}
|
||||
openapi: delete /v2.6.0-alpha/workspaces/{workspace_id}/webhooks/{endpoint_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/webhooks
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/webhooks
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/webhooks
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/webhooks
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/webhooks/test
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/webhooks/test
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: delete /v2/workspaces/{workspace_id}
|
||||
openapi: delete /v2.6.0-alpha/workspaces/{workspace_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/list
|
||||
openapi: post /v2.6.0-alpha/workspaces/list
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: get /v2/workspaces/{workspace_id}/deriver/status
|
||||
openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/deriver/status
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces
|
||||
openapi: post /v2.6.0-alpha/workspaces
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/search
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/search
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: post /v2/workspaces/{workspace_id}/trigger_dream
|
||||
openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/trigger_dream
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
---
|
||||
openapi: put /v2/workspaces/{workspace_id}
|
||||
openapi: put /v2.6.0-alpha/workspaces/{workspace_id}
|
||||
---
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ title: 'Introduction'
|
|||
This section documents all available API endpoints in the Honcho Server. Each
|
||||
endpoint provides CRUD operations for our core primitives. For information
|
||||
about these primitives, see
|
||||
[Architecture](/v2/documentation/core-concepts/architecture).
|
||||
[Architecture](/v2.6.0-alpha/documentation/core-concepts/architecture).
|
||||
|
||||
<Warning>
|
||||
We strongly recommend using our official SDKs instead of calling these APIs directly. The SDKs provide better error handling, type safety, and developer experience.
|
||||
|
|
|
|||
|
|
@ -276,8 +276,8 @@ const client = new Honcho({
|
|||
|
||||
### Next Steps
|
||||
|
||||
- **Explore the API**: Check out the [API Reference](/v2/api-reference/introduction)
|
||||
- **Try the SDKs**: See our [guides](/v2/guides) for examples
|
||||
- **Explore the API**: Check out the [API Reference](/v2.6.0-alpha/api-reference/introduction)
|
||||
- **Try the SDKs**: See our [guides](/v2.6.0-alpha/guides) for examples
|
||||
- **Configure Honcho**: Visit the [Configuration Guide](./configuration) for detailed settings
|
||||
- **Join the community**: [Discord](https://discord.gg/plasticlabs)
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ icon: "sitemap"
|
|||
sidebarTitle: "Architecture"
|
||||
---
|
||||
|
||||
Honcho is memory infrastructure that continuously [*reasons*](/v2/documentation/core-concepts/reasoning) about data to build rich representations of peers (users, agents, or any entity) over time. This document explains the data model, system components, and how data flows through Honcho.
|
||||
Honcho is memory infrastructure that continuously [*reasons*](/v2.6.0-alpha/documentation/core-concepts/reasoning) about data to build rich representations of peers (users, agents, or any entity) over time. This document explains the data model, system components, and how data flows through Honcho.
|
||||
|
||||
## Data Model
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Authentication is scoped to the workspace level, and configuration settings can
|
|||
|
||||
### <Icon icon="user" /> Peers
|
||||
|
||||
Peers are the most important entity in Honcho--everything revolves around building and maintaining their [*representations*](/v2/documentation/core-concepts/representation). A peer represents any individual user, agent, or entity in a workspace. Treating humans and agents the same way lets you build arbitrary combinations for multi-agent or group chat scenarios.
|
||||
Peers are the most important entity in Honcho--everything revolves around building and maintaining their [*representations*](/v2.6.0-alpha/documentation/core-concepts/representation). A peer represents any individual user, agent, or entity in a workspace. Treating humans and agents the same way lets you build arbitrary combinations for multi-agent or group chat scenarios.
|
||||
|
||||
Each peer has a unique identifier within a workspace and is a container for reasoning across all their sessions. This cross-session context means conclusions drawn about a peer in one session can inform interactions in completely different sessions. Peers can be configured to control whether Honcho reasons about them.
|
||||
|
||||
|
|
@ -90,13 +90,13 @@ Honcho's architecture follows a few core principles. Everything revolves around
|
|||
<Card title="Get an API Key" icon="key" href="https://app.honcho.dev">
|
||||
Sign up for the Honcho platform and start building
|
||||
</Card>
|
||||
<Card title="Quickstart" icon="rocket" href="/v2/documentation/introduction/quickstart">
|
||||
<Card title="Quickstart" icon="rocket" href="/v2.6.0-alpha/documentation/introduction/quickstart">
|
||||
Get started with your first integration
|
||||
</Card>
|
||||
<Card title="Reasoning" icon="gears" href="/v2/documentation/core-concepts/reasoning">
|
||||
<Card title="Reasoning" icon="gears" href="/v2.6.0-alpha/documentation/core-concepts/reasoning">
|
||||
Learn how Honcho reasons about messages to build memory
|
||||
</Card>
|
||||
<Card title="Peer Representations" icon="user-magnifying-glass" href="/v2/documentation/core-concepts/representation">
|
||||
<Card title="Peer Representations" icon="user-magnifying-glass" href="/v2.6.0-alpha/documentation/core-concepts/representation">
|
||||
Understand what peer representations are and how they work
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -84,13 +84,13 @@ Without exhaustive reasoning, you're stuck with surface-level retrieval or someo
|
|||
<Card title="Get an API Key" icon="key" href="https://app.honcho.dev">
|
||||
Sign up for the Honcho platform and start building
|
||||
</Card>
|
||||
<Card title="Quickstart" icon="rocket" href="/v2/documentation/introduction/quickstart">
|
||||
<Card title="Quickstart" icon="rocket" href="/v2.6.0-alpha/documentation/introduction/quickstart">
|
||||
Get started with your first integration
|
||||
</Card>
|
||||
<Card title="Architecture" icon="sitemap" href="/v2/documentation/core-concepts/architecture">
|
||||
<Card title="Architecture" icon="sitemap" href="/v2.6.0-alpha/documentation/core-concepts/architecture">
|
||||
See how reasoning fits into Honcho's overall architecture
|
||||
</Card>
|
||||
<Card title="Peer Representations" icon="user-magnifying-glass" href="/v2/documentation/core-concepts/representation">
|
||||
<Card title="Peer Representations" icon="user-magnifying-glass" href="/v2.6.0-alpha/documentation/core-concepts/representation">
|
||||
Learn how reasoning produces peer representations
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ When you write messages to Honcho, the reasoning models extract premises, draw c
|
|||
|
||||
## What's in a Representation?
|
||||
|
||||
A peer representation is made up of several types of artifacts that Honcho generates through [*reasoning*](/v2/documentation/core-concepts/reasoning):
|
||||
A peer representation is made up of several types of artifacts that Honcho generates through [*reasoning*](/v2.6.0-alpha/documentation/core-concepts/reasoning):
|
||||
|
||||
**Conclusions** are insights derived through formal logic. Deductive conclusions are things Honcho can be certain about based on extracted premises. Inductive conclusions identify patterns across multiple messages. Abductive conclusions infer the simplest explanations for observed behavior. For example, if a user frequently mentions work deadlines and rarely mentions hobbies, Honcho might inductively conclude they're time-constrained or career-focused.
|
||||
|
||||
|
|
@ -25,7 +25,7 @@ These enable continuous improvement. Each new message refines conclusions, updat
|
|||
|
||||
Honcho can build different representations based on what each peer observes. This enables sophisticated multi-peer scenarios where understanding is relative to what was actually witnessed.
|
||||
|
||||
There are two observation modes controlled by [configuration](/v2/documentation/features/advanced/configuration):
|
||||
There are two observation modes controlled by [configuration](/v2.6.0-alpha/documentation/features/advanced/configuration):
|
||||
|
||||
**Honcho observing peers** (`observe_me`): When enabled (default), Honcho forms a representation of the peer based on all messages they've sent across all sessions. This is Honcho's understanding of that peer, built from everything they've said and done in your system. Set `observe_me: false` if you don't want Honcho to reason about that peer at all.
|
||||
|
||||
|
|
@ -54,13 +54,13 @@ Humans reconstruct the past from imperfect recollections, then act on those reco
|
|||
<Card title="Get an API Key" icon="key" href="https://app.honcho.dev">
|
||||
Sign up for the Honcho platform and start building
|
||||
</Card>
|
||||
<Card title="Quickstart" icon="rocket" href="/v2/documentation/introduction/quickstart">
|
||||
<Card title="Quickstart" icon="rocket" href="/v2.6.0-alpha/documentation/introduction/quickstart">
|
||||
See representations in action with a working example
|
||||
</Card>
|
||||
<Card title="Architecture" icon="sitemap" href="/v2/documentation/core-concepts/architecture">
|
||||
<Card title="Architecture" icon="sitemap" href="/v2.6.0-alpha/documentation/core-concepts/architecture">
|
||||
Understand how representations fit into Honcho's architecture
|
||||
</Card>
|
||||
<Card title="Chat Endpoint" icon="comments" href="/v2/documentation/features/chat">
|
||||
<Card title="Chat Endpoint" icon="comments" href="/v2.6.0-alpha/documentation/features/chat">
|
||||
Learn how to query representations with natural language
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -9,12 +9,12 @@ Advanced features give you fine-grained control over Honcho's behavior and imple
|
|||
|
||||
## Configuration & Monitoring
|
||||
|
||||
- [Queue Status](/v2/documentation/features/advanced/queue-status) - Monitor background processing and reasoning tasks
|
||||
- [Configuration](/v2/documentation/features/advanced/toggle-reasoning) - Configure reasoning models and behavior
|
||||
- [Summarizer](/v2/documentation/features/advanced/summarizer) - Automatic session summarization
|
||||
- [Queue Status](/v2.6.0-alpha/documentation/features/advanced/queue-status) - Monitor background processing and reasoning tasks
|
||||
- [Configuration](/v2.6.0-alpha/documentation/features/advanced/toggle-reasoning) - Configure reasoning models and behavior
|
||||
- [Summarizer](/v2.6.0-alpha/documentation/features/advanced/summarizer) - Automatic session summarization
|
||||
|
||||
## Querying & Filtering
|
||||
|
||||
- [Search](/v2/documentation/features/advanced/search) - Search across peers, sessions, and messages
|
||||
- [Filters](/v2/documentation/features/advanced/using-filters) - Filter queries with advanced parameters
|
||||
- [Streaming Responses](/v2/documentation/features/advanced/streaming-response) - Stream dialectic responses in real-time
|
||||
- [Search](/v2.6.0-alpha/documentation/features/advanced/search) - Search across peers, sessions, and messages
|
||||
- [Filters](/v2.6.0-alpha/documentation/features/advanced/using-filters) - Filter queries with advanced parameters
|
||||
- [Streaming Responses](/v2.6.0-alpha/documentation/features/advanced/streaming-response) - Stream dialectic responses in real-time
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: Learn how to check the status of Honcho's reasoning
|
|||
icon: "lines-leaning"
|
||||
---
|
||||
|
||||
Whenever messages are stored in Honcho, a background process kicks off to [reason](/v2/documentation/core-concepts/reasoning) about the conversation and generate insights.
|
||||
Whenever messages are stored in Honcho, a background process kicks off to [reason](/v2.6.0-alpha/documentation/core-concepts/reasoning) about the conversation and generate insights.
|
||||
|
||||
Reasoning is an asynchronous process and, depending on load, may not immediately
|
||||
generate insights for the latest message you've sent. To help with this, Honcho
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@ You may therefore disable observation of a peer by setting the `observe_me` flag
|
|||
If the peer has a session-level configuration, it will override this configuration. If the flag is not set, or is set to `true`, the peer will be observed.
|
||||
|
||||
<Info>
|
||||
For session-level observation controls and local representations (where peers build separate models of each other), see [Representation Scopes](/v2/documentation/features/advanced/representation-scopes).
|
||||
For session-level observation controls and local representations (where peers build separate models of each other), see [Representation Scopes](/v2.6.0-alpha/documentation/features/advanced/representation-scopes).
|
||||
</Info>
|
||||
|
||||
<CodeGroup>
|
||||
|
|
|
|||
|
|
@ -172,7 +172,7 @@ When you call `peer.chat(query)`:
|
|||
3. Combines them with segments of source messages, if needed, to gather more context
|
||||
4. Synthesizes them into a coherent natural language response to your query
|
||||
|
||||
Honcho [reasoning](/v2/documentation/core-concepts/reasoning) runs continuously in the background, processing new messages and updating representations. The chat endpoint always has access to Honcho's latest conclusions about the peer.
|
||||
Honcho [reasoning](/v2.6.0-alpha/documentation/core-concepts/reasoning) runs continuously in the background, processing new messages and updating representations. The chat endpoint always has access to Honcho's latest conclusions about the peer.
|
||||
|
||||
## Best Practices
|
||||
|
||||
|
|
@ -188,4 +188,4 @@ Don't just use chat for LLM prompts - use it to drive application logic, routing
|
|||
### Combine with get_context()
|
||||
Use `get_context()` for conversation context and `peer.chat()` for specific insights. They complement each other.
|
||||
|
||||
For more ideas on using the chat endpoint, see our [guides](/v2/guides/overview).
|
||||
For more ideas on using the chat endpoint, see our [guides](/v2.6.0-alpha/guides/overview).
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@ context = session.get_context(summary=False, tokens=2000)
|
|||
|
||||
### Peer Representation in Context
|
||||
|
||||
You can include a peer's [representation](/v2/documentation/core-concepts/representation) and peer card in the context by specifying `peer_target`. This is useful for providing the LLM with knowledge about a specific peer.
|
||||
You can include a peer's [representation](/v2.6.0-alpha/documentation/core-concepts/representation) and peer card in the context by specifying `peer_target`. This is useful for providing the LLM with knowledge about a specific peer.
|
||||
|
||||
<CodeGroup>
|
||||
```python Python
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Honcho is an open source memory library with a managed service for building stat
|
|||
<Card title="Get an API Key" icon="key" href="https://app.honcho.dev">
|
||||
Sign up and start building with Honcho
|
||||
</Card>
|
||||
<Card title="Quickstart" icon="rocket" href="/v2/documentation/introduction/quickstart">
|
||||
<Card title="Quickstart" icon="rocket" href="/v2.6.0-alpha/documentation/introduction/quickstart">
|
||||
Build your first stateful agent in minutes
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
@ -63,7 +63,7 @@ Honcho has four storage primitives that work together:
|
|||
- **Sessions** - Interaction threads between peers with temporal boundaries
|
||||
- **Messages** - Units of data that trigger reasoning (conversations, events, activity, documents, and more)
|
||||
|
||||
When you write messages to Honcho, they're stored and processed in the background. Custom reasoning models perform formal logical [*reasoning*](/v2/documentation/core-concepts/reasoning) to generate conclusions about each peer. These conclusions are stored as [*representations*](/v2/documentation/core-concepts/representation) that you can query to provide rich context for your agents.
|
||||
When you write messages to Honcho, they're stored and processed in the background. Custom reasoning models perform formal logical [*reasoning*](/v2.6.0-alpha/documentation/core-concepts/reasoning) to generate conclusions about each peer. These conclusions are stored as [*representations*](/v2.6.0-alpha/documentation/core-concepts/representation) that you can query to provide rich context for your agents.
|
||||
|
||||
|
||||
|
||||
|
|
@ -87,13 +87,13 @@ Welcome to Honcho. We're excited to have you at the frontier of AI with us 🫡.
|
|||
<Card title="Get an API Key" icon="key" href="https://app.honcho.dev">
|
||||
Sign up for the Honcho platform and get your API key
|
||||
</Card>
|
||||
<Card title="Quickstart" icon="rocket" href="/v2/documentation/introduction/quickstart">
|
||||
<Card title="Quickstart" icon="rocket" href="/v2.6.0-alpha/documentation/introduction/quickstart">
|
||||
Build your first stateful agent in minutes
|
||||
</Card>
|
||||
<Card title="Architecture" icon="sitemap" href="/v2/documentation/core-concepts/architecture">
|
||||
<Card title="Architecture" icon="sitemap" href="/v2.6.0-alpha/documentation/core-concepts/architecture">
|
||||
Deep dive into how Honcho's primitives fit together
|
||||
</Card>
|
||||
<Card title="Reasoning" icon="gears" href="/v2/documentation/core-concepts/reasoning">
|
||||
<Card title="Reasoning" icon="gears" href="/v2.6.0-alpha/documentation/core-concepts/reasoning">
|
||||
Learn how Honcho reasons about data to build memory
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -230,7 +230,7 @@ user.chat("What should I know about this user? 3 sentences max").then((response)
|
|||
</CodeGroup>
|
||||
|
||||
<Tip>
|
||||
Honcho needs a short amount of time to process messages you write to it. There are several utilities to [check the status](/v2/documentation/features/advanced/queue-status) of the queue. Honcho also offers numerous ways to query reasoning to fit latency needs: see the [Get Context](/v2/documentation/features/get-context) page.
|
||||
Honcho needs a short amount of time to process messages you write to it. There are several utilities to [check the status](/v2.6.0-alpha/documentation/features/advanced/queue-status) of the queue. Honcho also offers numerous ways to query reasoning to fit latency needs: see the [Get Context](/v2.6.0-alpha/documentation/features/get-context) page.
|
||||
</Tip>
|
||||
|
||||
The response will look something like this:
|
||||
|
|
@ -389,16 +389,16 @@ console.log(response);
|
|||
From here, you can explore how to use Honcho's features in your own applications:
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Get Context" icon="messages" href="/v2/documentation/features/get-context">
|
||||
<Card title="Get Context" icon="messages" href="/v2.6.0-alpha/documentation/features/get-context">
|
||||
Learn how to fetch the right context for your agent's next response
|
||||
</Card>
|
||||
<Card title="Architecture" icon="sitemap" href="/v2/documentation/core-concepts/architecture">
|
||||
<Card title="Architecture" icon="sitemap" href="/v2.6.0-alpha/documentation/core-concepts/architecture">
|
||||
Deep dive into how Honcho's primitives fit together
|
||||
</Card>
|
||||
<Card title="Chat Endpoint" icon="comments" href="/v2/documentation/features/chat">
|
||||
<Card title="Chat Endpoint" icon="comments" href="/v2.6.0-alpha/documentation/features/chat">
|
||||
Query representations with natural language
|
||||
</Card>
|
||||
<Card title="Guides" icon="book" href="/v2/guides/overview">
|
||||
<Card title="Guides" icon="book" href="/v2.6.0-alpha/guides/overview">
|
||||
Integration patterns and advanced use cases
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -23,9 +23,9 @@ I want to start building with Honcho - an open source memory library for buildin
|
|||
|
||||
**Documentation:**
|
||||
- Main docs: https://docs.honcho.dev
|
||||
- API Reference: https://docs.honcho.dev/v2/api-reference/introduction
|
||||
- Quickstart: https://docs.honcho.dev/v2/documentation/introduction/quickstart
|
||||
- Architecture: https://docs.honcho.dev/v2/documentation/core-concepts/architecture
|
||||
- API Reference: https://docs.honcho.dev/v2.6.0-alpha/api-reference/introduction
|
||||
- Quickstart: https://docs.honcho.dev/v2.6.0-alpha/documentation/introduction/quickstart
|
||||
- Architecture: https://docs.honcho.dev/v2.6.0-alpha/documentation/core-concepts/architecture
|
||||
|
||||
**Code & Examples:**
|
||||
- Core repo: https://github.com/plastic-labs/honcho
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ Expand the `Peers` list from the `Workspace` dashboard to see a detailed view of
|
|||
<img src="/images/app-screenshots/peer-dash.png" alt="Peer Dashboard" width="1200" height="800" loading="lazy" decoding="async" fetchpriority="low" />
|
||||
</Frame>
|
||||
|
||||
Click into any peer to navigate to their respective utilities page. Next to the `Peer` name you can edit the [Global Peer Configuration](/v2/documentation/core-concepts/configuration), and in the tabs below, explore all utilities for the `Peer`.
|
||||
Click into any peer to navigate to their respective utilities page. Next to the `Peer` name you can edit the [Global Peer Configuration](/v2.6.0-alpha/documentation/core-concepts/configuration), and in the tabs below, explore all utilities for the `Peer`.
|
||||
|
||||
<Frame>
|
||||
<img src="/images/app-screenshots/peer-utilities.png" alt="Peer Management Dashboard" width="1200" height="800" loading="lazy" decoding="async" fetchpriority="low" />
|
||||
|
|
@ -108,7 +108,7 @@ Utilities include:
|
|||
</Frame>
|
||||
|
||||
- **Session logs** view which `Sessions` the `Peer` is active
|
||||
- **Peer configuration and metadata management** including [Session-Peer Configuration](/v2/documentation/core-concepts/configuration#session-peer-configuration)
|
||||
- **Peer configuration and metadata management** including [Session-Peer Configuration](/v2.6.0-alpha/documentation/core-concepts/configuration#session-peer-configuration)
|
||||
|
||||
<Frame>
|
||||
<img src="/images/app-screenshots/peer-utilities.png" alt="Peer Management Dashboard" width="1200" height="800" loading="lazy" decoding="async" fetchpriority="low" />
|
||||
|
|
@ -153,9 +153,9 @@ The [Members](https://app.honcho.dev/members) page provides organization adminis
|
|||
|
||||
## Go Further
|
||||
|
||||
View the [Architecture](/v2/documentation/core-concepts/architecture) to see how Honcho works under the hood.
|
||||
View the [Architecture](/v2.6.0-alpha/documentation/core-concepts/architecture) to see how Honcho works under the hood.
|
||||
|
||||
Dive into our [API Reference](/v2/api-reference) to explore all available endpoints.
|
||||
Dive into our [API Reference](/v2.6.0-alpha/api-reference) to explore all available endpoints.
|
||||
|
||||
## Next Steps
|
||||
|
||||
|
|
@ -166,10 +166,10 @@ Dive into our [API Reference](/v2/api-reference) to explore all available endpoi
|
|||
<Card title="Join our Discord" icon="discord" href="http://discord.gg/plasticlabs">
|
||||
Connect with 1000+ developers building with Honcho
|
||||
</Card>
|
||||
<Card title="Contribute to Honcho" icon="code" href="/v2/contributing/guidelines">
|
||||
<Card title="Contribute to Honcho" icon="code" href="/v2.6.0-alpha/contributing/guidelines">
|
||||
View our guidelines and explore the codebase
|
||||
</Card>
|
||||
<Card title="Explore Examples" icon="book" href="/v2/guides">
|
||||
<Card title="Explore Examples" icon="book" href="/v2.6.0-alpha/guides">
|
||||
See Honcho in action with real examples
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -944,7 +944,7 @@ const response = await openai.chat.completions.create({
|
|||
When creating messages, you can optionally specify a custom `created_at` timestamp instead of using the server's current time:
|
||||
|
||||
```bash
|
||||
curl -X POST "https://api.honcho.dev/v2/workspaces/{workspace_id}/sessions/{session_id}/messages" \
|
||||
curl -X POST "https://api.honcho.dev/v2.6.0-alpha/workspaces/{workspace_id}/sessions/{session_id}/messages" \
|
||||
-H "Authorization: Bearer $API_KEY" \
|
||||
-H "Content-Type: application/json" \
|
||||
-d '{
|
||||
|
|
@ -968,7 +968,7 @@ If `created_at` is not provided, messages will use the server's current timestam
|
|||
|
||||
### Metadata and Filtering
|
||||
|
||||
See [Using Filters](/v2/guides/using-filters) for more examples on how to use filters.
|
||||
See [Using Filters](/v2.6.0-alpha/guides/using-filters) for more examples on how to use filters.
|
||||
|
||||
<CodeGroup>
|
||||
```python Python
|
||||
|
|
|
|||
|
|
@ -150,13 +150,13 @@ for query in user_queries:
|
|||
## Related Features
|
||||
|
||||
<CardGroup cols={3}>
|
||||
<Card title="Basic Get Context" icon="database" href="/v2/documentation/core-concepts/features/get-context">
|
||||
<Card title="Basic Get Context" icon="database" href="/v2.6.0-alpha/documentation/core-concepts/features/get-context">
|
||||
Learn about basic context retrieval
|
||||
</Card>
|
||||
<Card title="Summaries" icon="align-left" href="/v2/documentation/core-concepts/summarizer">
|
||||
<Card title="Summaries" icon="align-left" href="/v2.6.0-alpha/documentation/core-concepts/summarizer">
|
||||
Understand session summarization
|
||||
</Card>
|
||||
<Card title="Dialectic API" icon="comments" href="/v2/documentation/core-concepts/features/dialectic-endpoint">
|
||||
<Card title="Dialectic API" icon="comments" href="/v2.6.0-alpha/documentation/core-concepts/features/dialectic-endpoint">
|
||||
Chat with Honcho for insights
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -237,19 +237,19 @@ 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](/v2/documentation/core-concepts/configuration).
|
||||
behavior and can be toggled off via [the configuration](/v2.6.0-alpha/documentation/core-concepts/configuration).
|
||||
|
||||
## Next Steps
|
||||
|
||||
<CardGroup cols={3}>
|
||||
<Card title="Architecture" icon="rocket"
|
||||
href="/v2/documentation/core-concepts/architecture">
|
||||
href="/v2.6.0-alpha/documentation/core-concepts/architecture">
|
||||
Learn about the data primitives in Honcho and how they work together
|
||||
</Card>
|
||||
<Card title="Start Building" icon="brain" href="https://app.honcho.dev">
|
||||
Sign up for Managed Honcho and get started building agents now.
|
||||
</Card>
|
||||
<Card title="Guides" icon="book" href="/v2/guides/overview">
|
||||
<Card title="Guides" icon="book" href="/v2.6.0-alpha/guides/overview">
|
||||
Check out spellbooks to see different examples apps built with Honcho
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -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](/v2/documentation/core-concepts/configuration) page.
|
||||
Reasoning](/v2.6.0-alpha/documentation/core-concepts/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.
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ This tutorial uses the Honcho demo server at https://demo.honcho.dev which runs
|
|||
The `honcho_crewai` package provides `HonchoStorage`, a storage provider that implements CrewAI's `Storage` interface using Honcho's session-based memory.
|
||||
|
||||
<Note>
|
||||
Before proceeding, it's important to understand Honcho's core concepts (`Peers` and `Sessions`). Review the [Honcho Architecture](/v2/documentation/core-concepts/architecture) to familiarize yourself with these primitives.
|
||||
Before proceeding, it's important to understand Honcho's core concepts (`Peers` and `Sessions`). Review the [Honcho Architecture](/v2.6.0-alpha/documentation/core-concepts/architecture) to familiarize yourself with these primitives.
|
||||
</Note>
|
||||
|
||||
`HonchoStorage` implements CrewAI's `Storage` interface using Honcho's `peer` and `session` primitives.
|
||||
|
|
@ -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/v2/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/v2.6.0-alpha/documentation/core-concepts/features/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).
|
||||
|
|
@ -279,16 +279,16 @@ Now that you have a working CrewAI integration with Honcho, you can:
|
|||
## Related Resources
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Honcho Architecture" icon="sitemap" href="/v2/documentation/core-concepts/architecture">
|
||||
<Card title="Honcho Architecture" icon="sitemap" href="/v2.6.0-alpha/documentation/core-concepts/architecture">
|
||||
Understand Honcho's peer-based model and core primitives
|
||||
</Card>
|
||||
<Card title="Get Context" icon="messages" href="/v2/documentation/core-concepts/features/get-context">
|
||||
<Card title="Get Context" icon="messages" href="/v2.6.0-alpha/documentation/core-concepts/features/get-context">
|
||||
Learn about retrieving and formatting conversation context
|
||||
</Card>
|
||||
<Card title="Dialectic API" icon="brain" href="/v2/documentation/core-concepts/features/dialectic">
|
||||
<Card title="Dialectic API" icon="brain" href="/v2.6.0-alpha/documentation/core-concepts/features/dialectic">
|
||||
Query `peer` representations for deeper understanding
|
||||
</Card>
|
||||
<Card title="LangGraph Integration" icon="diagram-project" href="/v2/integrations/langgraph">
|
||||
<Card title="LangGraph Integration" icon="diagram-project" href="/v2.6.0-alpha/integrations/langgraph">
|
||||
Build stateful agents with LangGraph and Honcho
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@ const llm = new OpenAI({
|
|||
Define your state schema to pass data through the graph. The state stores Honcho objects directly along with the current user message and assistant response.
|
||||
|
||||
<Note>
|
||||
Before proceeding, it's important to understand Honcho's core concepts (`Peers` and `Sessions`). Review the [Honcho Architecture](/v2/documentation/core-concepts/architecture) to familiarize yourself with these primitives.
|
||||
Before proceeding, it's important to understand Honcho's core concepts (`Peers` and `Sessions`). Review the [Honcho Architecture](/v2.6.0-alpha/documentation/core-concepts/architecture) to familiarize yourself with these primitives.
|
||||
</Note>
|
||||
|
||||
<CodeGroup>
|
||||
|
|
@ -227,7 +227,7 @@ const graph = new StateGraph(StateAnnotation)
|
|||
|
||||
### Understanding get_context()
|
||||
|
||||
The [`get_context()`](/v2/documentation/core-concepts/features/get-context) method retrieves comprehensive conversation context and formats it for your LLM. It automatically:
|
||||
The [`get_context()`](/v2.6.0-alpha/documentation/core-concepts/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`](/v2/documentation/core-concepts/features/get-context)
|
||||
For more details on all available parameters, see [`get_context() documentation`](/v2.6.0-alpha/documentation/core-concepts/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="/v2/documentation/core-concepts/features/get-context">
|
||||
<Card title="Get Context" icon="messages" href="/v2.6.0-alpha/documentation/core-concepts/features/get-context">
|
||||
Learn more about retrieving and formatting conversation context
|
||||
</Card>
|
||||
<Card title="MCP Integration" icon="star-of-life" href="/v2/integrations/mcp">
|
||||
<Card title="MCP Integration" icon="star-of-life" href="/v2.6.0-alpha/integrations/mcp">
|
||||
Use Honcho in Claude Desktop with MCP
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ description: 'Helpful guides and design patterns for building with Honcho'
|
|||
icon: 'hat-wizard'
|
||||
---
|
||||
|
||||
<Note> Before you start a guide, follow [Quickstart](/v2/documentation/introduction/quickstart) to get up and running with Honcho in your language of choice. </Note>
|
||||
<Note> Before you start a guide, follow [Quickstart](/v2.6.0-alpha/documentation/introduction/quickstart) to get up and running with Honcho in your language of choice. </Note>
|
||||
|
||||
These guides provide concrete examples and implementation patterns for building with Honcho. Whether you're integrating Honcho into existing platforms, exploring advanced features, or getting up and running quickly, you'll find working code you can adapt to your needs.
|
||||
|
||||
|
|
@ -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="/v2/integrations/mcp">
|
||||
<Card title="MCP Integration" icon="link" href="/v2.6.0-alpha/integrations/mcp">
|
||||
Get Honcho running with a single prompt in Claude Code
|
||||
</Card>
|
||||
<Card title="LangGraph" icon="diagram-project" href="/v2/integrations/langgraph">
|
||||
<Card title="LangGraph" icon="diagram-project" href="/v2.6.0-alpha/integrations/langgraph">
|
||||
Add persistent memory and theory of mind to your LangGraph agents
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
@ -28,10 +28,10 @@ Quick integration guides to get up and running:
|
|||
Ready-to-use integration patterns for popular platforms:
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Discord Bot" icon="discord" href="/v2/guides/discord">
|
||||
<Card title="Discord Bot" icon="discord" href="/v2.6.0-alpha/guides/discord">
|
||||
Build a Discord bot that remembers users across conversations
|
||||
</Card>
|
||||
<Card title="Telegram Bot" icon="telegram" href="/v2/guides/telegram">
|
||||
<Card title="Telegram Bot" icon="telegram" href="/v2.6.0-alpha/guides/telegram">
|
||||
Create a Telegram bot with persistent user understanding
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
|
|
|||
|
|
@ -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](/v2/documentation/core-concepts/configuration)
|
||||
Peer or Session](/v2.6.0-alpha/documentation/core-concepts/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
|
||||
|
|
|
|||
Loading…
Reference in New Issue