From 69f823aed1926d7623385a0708e44302136bf28b Mon Sep 17 00:00:00 2001 From: vintro Date: Wed, 10 Dec 2025 17:18:32 -0500 Subject: [PATCH] fix: links --- .../api-reference/endpoint/keys/create-key.mdx | 2 +- .../messages/create-messages-for-session.mdx | 2 +- .../endpoint/messages/create-messages-with-file.mdx | 2 +- .../api-reference/endpoint/messages/get-message.mdx | 2 +- .../api-reference/endpoint/messages/get-messages.mdx | 2 +- .../endpoint/messages/update-message.mdx | 2 +- .../endpoint/observations/create-observations.mdx | 2 +- .../endpoint/observations/delete-observation.mdx | 2 +- .../endpoint/observations/list-observations.mdx | 2 +- .../endpoint/observations/query-observations.mdx | 2 +- .../api-reference/endpoint/peers/chat.mdx | 2 +- .../endpoint/peers/get-or-create-peer.mdx | 2 +- .../api-reference/endpoint/peers/get-peer-card.mdx | 2 +- .../endpoint/peers/get-peer-context.mdx | 2 +- .../api-reference/endpoint/peers/get-peers.mdx | 2 +- .../endpoint/peers/get-sessions-for-peer.mdx | 2 +- .../endpoint/peers/get-working-representation.mdx | 2 +- .../api-reference/endpoint/peers/search-peer.mdx | 2 +- .../api-reference/endpoint/peers/set-peer-card.mdx | 2 +- .../api-reference/endpoint/peers/update-peer.mdx | 2 +- .../endpoint/sessions/add-peers-to-session.mdx | 2 +- .../endpoint/sessions/clone-session.mdx | 2 +- .../endpoint/sessions/delete-session.mdx | 2 +- .../endpoint/sessions/get-or-create-session.mdx | 2 +- .../endpoint/sessions/get-peer-config.mdx | 2 +- .../endpoint/sessions/get-session-context.mdx | 2 +- .../endpoint/sessions/get-session-peers.mdx | 2 +- .../endpoint/sessions/get-session-summaries.mdx | 2 +- .../api-reference/endpoint/sessions/get-sessions.mdx | 2 +- .../endpoint/sessions/remove-peers-from-session.mdx | 2 +- .../endpoint/sessions/search-session.mdx | 2 +- .../endpoint/sessions/set-peer-config.mdx | 2 +- .../endpoint/sessions/set-session-peers.mdx | 2 +- .../endpoint/sessions/update-session.mdx | 2 +- .../endpoint/webhooks/delete-webhook-endpoint.mdx | 2 +- .../webhooks/get-or-create-webhook-endpoint.mdx | 2 +- .../endpoint/webhooks/list-webhook-endpoints.mdx | 2 +- .../api-reference/endpoint/webhooks/test-emit.mdx | 2 +- .../endpoint/workspaces/delete-workspace.mdx | 2 +- .../endpoint/workspaces/get-all-workspaces.mdx | 2 +- .../endpoint/workspaces/get-deriver-status.mdx | 2 +- .../endpoint/workspaces/get-or-create-workspace.mdx | 2 +- .../endpoint/workspaces/search-workspace.mdx | 2 +- .../endpoint/workspaces/trigger-dream.mdx | 2 +- .../endpoint/workspaces/update-workspace.mdx | 2 +- docs/v2.6.0-alpha/api-reference/introduction.mdx | 2 +- docs/v2.6.0-alpha/contributing/self-hosting.mdx | 4 ++-- .../documentation/core-concepts/architecture.mdx | 10 +++++----- .../documentation/core-concepts/reasoning.mdx | 6 +++--- .../documentation/core-concepts/representation.mdx | 10 +++++----- .../documentation/features/advanced/overview.mdx | 12 ++++++------ .../documentation/features/advanced/queue-status.mdx | 2 +- .../features/advanced/toggle-reasoning.mdx | 2 +- docs/v2.6.0-alpha/documentation/features/chat.mdx | 4 ++-- .../documentation/features/get-context.mdx | 2 +- .../documentation/introduction/overview.mdx | 10 +++++----- .../documentation/introduction/quickstart.mdx | 10 +++++----- .../documentation/introduction/vibecoding.mdx | 6 +++--- .../documentation/reference/platform.mdx | 12 ++++++------ docs/v2.6.0-alpha/documentation/reference/sdk.mdx | 4 ++-- .../honcho-memory/advanced-retrieval/get-context.mdx | 6 +++--- .../scratch/honcho-memory/quickstart.mdx | 6 +++--- .../documentation/scratch/local-vs-global.mdx | 2 +- docs/v2.6.0-alpha/guides/integrations/crewai.mdx | 12 ++++++------ docs/v2.6.0-alpha/guides/integrations/langgraph.mdx | 10 +++++----- docs/v2.6.0-alpha/guides/overview.mdx | 10 +++++----- docs/v2.6.0-alpha/guides/storing-data.mdx | 2 +- 67 files changed, 117 insertions(+), 117 deletions(-) diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/keys/create-key.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/keys/create-key.mdx index 41b759f7..eb133652 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/keys/create-key.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/keys/create-key.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/keys +openapi: post /v2.6.0-alpha/keys --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/messages/create-messages-for-session.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/messages/create-messages-for-session.mdx index 19e9c9cb..59f2a1ad 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/messages/create-messages-for-session.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/messages/create-messages-for-session.mdx @@ -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/ --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/messages/create-messages-with-file.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/messages/create-messages-with-file.mdx index 55ca55a8..f87b8243 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/messages/create-messages-with-file.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/messages/create-messages-with-file.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/messages/get-message.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/messages/get-message.mdx index 53765daa..db9c62ef 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/messages/get-message.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/messages/get-message.mdx @@ -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} --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/messages/get-messages.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/messages/get-messages.mdx index 612c7aab..eb5b5097 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/messages/get-messages.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/messages/get-messages.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/messages/update-message.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/messages/update-message.mdx index 77a296b2..3cb2db81 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/messages/update-message.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/messages/update-message.mdx @@ -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} --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/observations/create-observations.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/observations/create-observations.mdx index 1aafec44..569e7190 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/observations/create-observations.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/observations/create-observations.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/observations +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/observations --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/observations/delete-observation.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/observations/delete-observation.mdx index 172ef679..69c9ddd3 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/observations/delete-observation.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/observations/delete-observation.mdx @@ -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} --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/observations/list-observations.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/observations/list-observations.mdx index 3063a96e..1c4bef72 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/observations/list-observations.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/observations/list-observations.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/observations/list +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/observations/list --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/observations/query-observations.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/observations/query-observations.mdx index d5d15a14..00c5c6f8 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/observations/query-observations.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/observations/query-observations.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/observations/query +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/observations/query --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/chat.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/chat.mdx index 8fe3cd18..b7f8047e 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/chat.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/chat.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-or-create-peer.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-or-create-peer.mdx index 724d8100..9964c2aa 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-or-create-peer.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-or-create-peer.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/peers +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/peers --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peer-card.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peer-card.mdx index ef12d719..5ced4d68 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peer-card.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peer-card.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peer-context.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peer-context.mdx index ed6563c2..3e2c9508 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peer-context.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peer-context.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peers.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peers.mdx index 954e89b2..7b885554 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peers.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-peers.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/peers/list +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/peers/list --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-sessions-for-peer.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-sessions-for-peer.mdx index 8b33a832..93ff788d 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-sessions-for-peer.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-sessions-for-peer.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-working-representation.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-working-representation.mdx index b712a032..b77e17de 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-working-representation.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/get-working-representation.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/search-peer.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/search-peer.mdx index c8c25451..0053845c 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/search-peer.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/search-peer.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/set-peer-card.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/set-peer-card.mdx index c209ca8c..ab484cf3 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/set-peer-card.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/set-peer-card.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/peers/update-peer.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/peers/update-peer.mdx index 91b6da61..7bc1b2a5 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/peers/update-peer.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/peers/update-peer.mdx @@ -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} --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/add-peers-to-session.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/add-peers-to-session.mdx index e73ece96..e04fe792 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/add-peers-to-session.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/add-peers-to-session.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/clone-session.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/clone-session.mdx index e06f19a1..016cb1de 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/clone-session.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/clone-session.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/delete-session.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/delete-session.mdx index 2d1252fb..c4348148 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/delete-session.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/delete-session.mdx @@ -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} --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-or-create-session.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-or-create-session.mdx index c013803e..b3aab9d8 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-or-create-session.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-or-create-session.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/sessions +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-peer-config.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-peer-config.mdx index e84f5cea..33438219 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-peer-config.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-peer-config.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-context.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-context.mdx index c8c1bdd1..4e0444f5 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-context.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-context.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-peers.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-peers.mdx index 18beb221..fa85d340 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-peers.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-peers.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-summaries.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-summaries.mdx index 9ae150bc..77208467 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-summaries.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-session-summaries.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-sessions.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-sessions.mdx index 75dc7eba..671f02b3 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-sessions.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/get-sessions.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/sessions/list +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/sessions/list --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/remove-peers-from-session.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/remove-peers-from-session.mdx index 31acf6bf..c08aa744 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/remove-peers-from-session.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/remove-peers-from-session.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/search-session.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/search-session.mdx index 308138d5..b246354d 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/search-session.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/search-session.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/set-peer-config.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/set-peer-config.mdx index 6e6ee462..39b6199b 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/set-peer-config.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/set-peer-config.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/set-session-peers.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/set-session-peers.mdx index 475db5b9..aa8b3f8d 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/set-session-peers.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/set-session-peers.mdx @@ -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 --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/update-session.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/update-session.mdx index 94d14d1b..d2f51dd3 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/sessions/update-session.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/sessions/update-session.mdx @@ -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} --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/delete-webhook-endpoint.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/delete-webhook-endpoint.mdx index 03663d39..44a48097 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/delete-webhook-endpoint.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/delete-webhook-endpoint.mdx @@ -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} --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/get-or-create-webhook-endpoint.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/get-or-create-webhook-endpoint.mdx index 3eca8afb..3303c4dd 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/get-or-create-webhook-endpoint.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/get-or-create-webhook-endpoint.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/webhooks +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/webhooks --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/list-webhook-endpoints.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/list-webhook-endpoints.mdx index a205df80..4f0288c2 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/list-webhook-endpoints.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/list-webhook-endpoints.mdx @@ -1,3 +1,3 @@ --- -openapi: get /v2/workspaces/{workspace_id}/webhooks +openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/webhooks --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/test-emit.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/test-emit.mdx index 8c2cbddd..e12c94f3 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/test-emit.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/webhooks/test-emit.mdx @@ -1,3 +1,3 @@ --- -openapi: get /v2/workspaces/{workspace_id}/webhooks/test +openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/webhooks/test --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/delete-workspace.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/delete-workspace.mdx index f8eb6168..01d7774f 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/delete-workspace.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/delete-workspace.mdx @@ -1,3 +1,3 @@ --- -openapi: delete /v2/workspaces/{workspace_id} +openapi: delete /v2.6.0-alpha/workspaces/{workspace_id} --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-all-workspaces.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-all-workspaces.mdx index 12e3d931..dbfa1d98 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-all-workspaces.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-all-workspaces.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/list +openapi: post /v2.6.0-alpha/workspaces/list --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-deriver-status.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-deriver-status.mdx index 0b7a32b9..b5460068 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-deriver-status.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-deriver-status.mdx @@ -1,3 +1,3 @@ --- -openapi: get /v2/workspaces/{workspace_id}/deriver/status +openapi: get /v2.6.0-alpha/workspaces/{workspace_id}/deriver/status --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-or-create-workspace.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-or-create-workspace.mdx index 513f4fbb..85246932 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-or-create-workspace.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/get-or-create-workspace.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces +openapi: post /v2.6.0-alpha/workspaces --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/search-workspace.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/search-workspace.mdx index f17e4e52..9fa73978 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/search-workspace.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/search-workspace.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/search +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/search --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/trigger-dream.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/trigger-dream.mdx index 138c58be..d238dc7f 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/trigger-dream.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/trigger-dream.mdx @@ -1,3 +1,3 @@ --- -openapi: post /v2/workspaces/{workspace_id}/trigger_dream +openapi: post /v2.6.0-alpha/workspaces/{workspace_id}/trigger_dream --- diff --git a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/update-workspace.mdx b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/update-workspace.mdx index 07d3b75e..0ab685e7 100644 --- a/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/update-workspace.mdx +++ b/docs/v2.6.0-alpha/api-reference/endpoint/workspaces/update-workspace.mdx @@ -1,3 +1,3 @@ --- -openapi: put /v2/workspaces/{workspace_id} +openapi: put /v2.6.0-alpha/workspaces/{workspace_id} --- diff --git a/docs/v2.6.0-alpha/api-reference/introduction.mdx b/docs/v2.6.0-alpha/api-reference/introduction.mdx index 6765e7a3..5234167e 100644 --- a/docs/v2.6.0-alpha/api-reference/introduction.mdx +++ b/docs/v2.6.0-alpha/api-reference/introduction.mdx @@ -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). We strongly recommend using our official SDKs instead of calling these APIs directly. The SDKs provide better error handling, type safety, and developer experience. diff --git a/docs/v2.6.0-alpha/contributing/self-hosting.mdx b/docs/v2.6.0-alpha/contributing/self-hosting.mdx index 3e5e1e42..88fca48e 100644 --- a/docs/v2.6.0-alpha/contributing/self-hosting.mdx +++ b/docs/v2.6.0-alpha/contributing/self-hosting.mdx @@ -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) diff --git a/docs/v2.6.0-alpha/documentation/core-concepts/architecture.mdx b/docs/v2.6.0-alpha/documentation/core-concepts/architecture.mdx index b0eb7dc3..35ec932a 100644 --- a/docs/v2.6.0-alpha/documentation/core-concepts/architecture.mdx +++ b/docs/v2.6.0-alpha/documentation/core-concepts/architecture.mdx @@ -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 ### 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 Sign up for the Honcho platform and start building - + Get started with your first integration - + Learn how Honcho reasons about messages to build memory - + Understand what peer representations are and how they work diff --git a/docs/v2.6.0-alpha/documentation/core-concepts/reasoning.mdx b/docs/v2.6.0-alpha/documentation/core-concepts/reasoning.mdx index 143abfba..38aec7b5 100644 --- a/docs/v2.6.0-alpha/documentation/core-concepts/reasoning.mdx +++ b/docs/v2.6.0-alpha/documentation/core-concepts/reasoning.mdx @@ -84,13 +84,13 @@ Without exhaustive reasoning, you're stuck with surface-level retrieval or someo Sign up for the Honcho platform and start building - + Get started with your first integration - + See how reasoning fits into Honcho's overall architecture - + Learn how reasoning produces peer representations diff --git a/docs/v2.6.0-alpha/documentation/core-concepts/representation.mdx b/docs/v2.6.0-alpha/documentation/core-concepts/representation.mdx index a9bd2325..5d9efb83 100644 --- a/docs/v2.6.0-alpha/documentation/core-concepts/representation.mdx +++ b/docs/v2.6.0-alpha/documentation/core-concepts/representation.mdx @@ -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 Sign up for the Honcho platform and start building - + See representations in action with a working example - + Understand how representations fit into Honcho's architecture - + Learn how to query representations with natural language diff --git a/docs/v2.6.0-alpha/documentation/features/advanced/overview.mdx b/docs/v2.6.0-alpha/documentation/features/advanced/overview.mdx index 9891a34f..916334a6 100644 --- a/docs/v2.6.0-alpha/documentation/features/advanced/overview.mdx +++ b/docs/v2.6.0-alpha/documentation/features/advanced/overview.mdx @@ -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 diff --git a/docs/v2.6.0-alpha/documentation/features/advanced/queue-status.mdx b/docs/v2.6.0-alpha/documentation/features/advanced/queue-status.mdx index 9b00eb01..5b3d8dfa 100644 --- a/docs/v2.6.0-alpha/documentation/features/advanced/queue-status.mdx +++ b/docs/v2.6.0-alpha/documentation/features/advanced/queue-status.mdx @@ -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 diff --git a/docs/v2.6.0-alpha/documentation/features/advanced/toggle-reasoning.mdx b/docs/v2.6.0-alpha/documentation/features/advanced/toggle-reasoning.mdx index 2966c321..c37e1661 100644 --- a/docs/v2.6.0-alpha/documentation/features/advanced/toggle-reasoning.mdx +++ b/docs/v2.6.0-alpha/documentation/features/advanced/toggle-reasoning.mdx @@ -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. -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). diff --git a/docs/v2.6.0-alpha/documentation/features/chat.mdx b/docs/v2.6.0-alpha/documentation/features/chat.mdx index 97296f83..b983846d 100644 --- a/docs/v2.6.0-alpha/documentation/features/chat.mdx +++ b/docs/v2.6.0-alpha/documentation/features/chat.mdx @@ -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). diff --git a/docs/v2.6.0-alpha/documentation/features/get-context.mdx b/docs/v2.6.0-alpha/documentation/features/get-context.mdx index a564e9d9..ce6546c1 100644 --- a/docs/v2.6.0-alpha/documentation/features/get-context.mdx +++ b/docs/v2.6.0-alpha/documentation/features/get-context.mdx @@ -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. ```python Python diff --git a/docs/v2.6.0-alpha/documentation/introduction/overview.mdx b/docs/v2.6.0-alpha/documentation/introduction/overview.mdx index 3d9624f9..871c0c4e 100644 --- a/docs/v2.6.0-alpha/documentation/introduction/overview.mdx +++ b/docs/v2.6.0-alpha/documentation/introduction/overview.mdx @@ -10,7 +10,7 @@ Honcho is an open source memory library with a managed service for building stat Sign up and start building with Honcho - + Build your first stateful agent in minutes @@ -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. ![Honcho Architecture](/images/architecture.png) @@ -87,13 +87,13 @@ Welcome to Honcho. We're excited to have you at the frontier of AI with us 🫡. Sign up for the Honcho platform and get your API key - + Build your first stateful agent in minutes - + Deep dive into how Honcho's primitives fit together - + Learn how Honcho reasons about data to build memory diff --git a/docs/v2.6.0-alpha/documentation/introduction/quickstart.mdx b/docs/v2.6.0-alpha/documentation/introduction/quickstart.mdx index 927e0ba1..21feff6a 100644 --- a/docs/v2.6.0-alpha/documentation/introduction/quickstart.mdx +++ b/docs/v2.6.0-alpha/documentation/introduction/quickstart.mdx @@ -230,7 +230,7 @@ user.chat("What should I know about this user? 3 sentences max").then((response) -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. 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: - + Learn how to fetch the right context for your agent's next response - + Deep dive into how Honcho's primitives fit together - + Query representations with natural language - + Integration patterns and advanced use cases diff --git a/docs/v2.6.0-alpha/documentation/introduction/vibecoding.mdx b/docs/v2.6.0-alpha/documentation/introduction/vibecoding.mdx index 1c0ae6ec..0e44dc04 100644 --- a/docs/v2.6.0-alpha/documentation/introduction/vibecoding.mdx +++ b/docs/v2.6.0-alpha/documentation/introduction/vibecoding.mdx @@ -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 diff --git a/docs/v2.6.0-alpha/documentation/reference/platform.mdx b/docs/v2.6.0-alpha/documentation/reference/platform.mdx index 426af86f..479ffcb2 100644 --- a/docs/v2.6.0-alpha/documentation/reference/platform.mdx +++ b/docs/v2.6.0-alpha/documentation/reference/platform.mdx @@ -93,7 +93,7 @@ Expand the `Peers` list from the `Workspace` dashboard to see a detailed view of Peer Dashboard -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`. Peer Management Dashboard @@ -108,7 +108,7 @@ Utilities include: - **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) Peer Management Dashboard @@ -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 Connect with 1000+ developers building with Honcho - + View our guidelines and explore the codebase - + See Honcho in action with real examples diff --git a/docs/v2.6.0-alpha/documentation/reference/sdk.mdx b/docs/v2.6.0-alpha/documentation/reference/sdk.mdx index 038e3cbc..7e4f7f80 100644 --- a/docs/v2.6.0-alpha/documentation/reference/sdk.mdx +++ b/docs/v2.6.0-alpha/documentation/reference/sdk.mdx @@ -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. ```python Python diff --git a/docs/v2.6.0-alpha/documentation/scratch/honcho-memory/advanced-retrieval/get-context.mdx b/docs/v2.6.0-alpha/documentation/scratch/honcho-memory/advanced-retrieval/get-context.mdx index 520fb362..c30dcf51 100644 --- a/docs/v2.6.0-alpha/documentation/scratch/honcho-memory/advanced-retrieval/get-context.mdx +++ b/docs/v2.6.0-alpha/documentation/scratch/honcho-memory/advanced-retrieval/get-context.mdx @@ -150,13 +150,13 @@ for query in user_queries: ## Related Features - + Learn about basic context retrieval - + Understand session summarization - + Chat with Honcho for insights diff --git a/docs/v2.6.0-alpha/documentation/scratch/honcho-memory/quickstart.mdx b/docs/v2.6.0-alpha/documentation/scratch/honcho-memory/quickstart.mdx index 812bfb95..228d0861 100644 --- a/docs/v2.6.0-alpha/documentation/scratch/honcho-memory/quickstart.mdx +++ b/docs/v2.6.0-alpha/documentation/scratch/honcho-memory/quickstart.mdx @@ -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 + href="/v2.6.0-alpha/documentation/core-concepts/architecture"> Learn about the data primitives in Honcho and how they work together Sign up for Managed Honcho and get started building agents now. - + Check out spellbooks to see different examples apps built with Honcho diff --git a/docs/v2.6.0-alpha/documentation/scratch/local-vs-global.mdx b/docs/v2.6.0-alpha/documentation/scratch/local-vs-global.mdx index e5670229..c9036cdd 100644 --- a/docs/v2.6.0-alpha/documentation/scratch/local-vs-global.mdx +++ b/docs/v2.6.0-alpha/documentation/scratch/local-vs-global.mdx @@ -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. diff --git a/docs/v2.6.0-alpha/guides/integrations/crewai.mdx b/docs/v2.6.0-alpha/guides/integrations/crewai.mdx index 6d39d983..d6cb34a2 100644 --- a/docs/v2.6.0-alpha/guides/integrations/crewai.mdx +++ b/docs/v2.6.0-alpha/guides/integrations/crewai.mdx @@ -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. -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. `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. 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 - + Understand Honcho's peer-based model and core primitives - + Learn about retrieving and formatting conversation context - + Query `peer` representations for deeper understanding - + Build stateful agents with LangGraph and Honcho diff --git a/docs/v2.6.0-alpha/guides/integrations/langgraph.mdx b/docs/v2.6.0-alpha/guides/integrations/langgraph.mdx index 26af8c17..3eba2565 100644 --- a/docs/v2.6.0-alpha/guides/integrations/langgraph.mdx +++ b/docs/v2.6.0-alpha/guides/integrations/langgraph.mdx @@ -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. -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. @@ -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 -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) ## Chat Loop @@ -354,10 +354,10 @@ Now that you have a working LangGraph integration with Honcho, you can: ## Related Resources - + Learn more about retrieving and formatting conversation context - + Use Honcho in Claude Desktop with MCP diff --git a/docs/v2.6.0-alpha/guides/overview.mdx b/docs/v2.6.0-alpha/guides/overview.mdx index bfd96981..1944c7d6 100644 --- a/docs/v2.6.0-alpha/guides/overview.mdx +++ b/docs/v2.6.0-alpha/guides/overview.mdx @@ -5,7 +5,7 @@ description: 'Helpful guides and design patterns for building with Honcho' icon: 'hat-wizard' --- - Before you start a guide, follow [Quickstart](/v2/documentation/introduction/quickstart) to get up and running with Honcho in your language of choice. + 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. 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: - + Get Honcho running with a single prompt in Claude Code - + Add persistent memory and theory of mind to your LangGraph agents @@ -28,10 +28,10 @@ Quick integration guides to get up and running: Ready-to-use integration patterns for popular platforms: - + Build a Discord bot that remembers users across conversations - + Create a Telegram bot with persistent user understanding diff --git a/docs/v2.6.0-alpha/guides/storing-data.mdx b/docs/v2.6.0-alpha/guides/storing-data.mdx index 7f280473..4d49e744 100644 --- a/docs/v2.6.0-alpha/guides/storing-data.mdx +++ b/docs/v2.6.0-alpha/guides/storing-data.mdx @@ -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