Welcome to the Honcho changelog! This section documents all notable changes to the Honcho API and SDKs.

​
Honcho API and SDK Changelogs

​
v2.0.4 (Current)

​
Fixed

  • Migration/provision scripts did not have correct database connection arguments, causing timeouts
​
v2.0.3

​
Fixed

  • Bug that causes runtime error when Sentry flags are enabled
​
v2.0.2

​
Fixed

  • Database initialization was misconfigured and led to provision_db script failing: switch to consistent working configuration with transaction pooler
​
v2.0.1

​
Added

  • Ergonomic SDKs for Python and TypeScript (uses Stainless underneath)
  • Deriver Queue Status endpoint
  • Complex arbitrary filters on workspace/session/peer/message
  • Message embedding table for full semantic search

​
Changed

  • Overhauled documentation
  • BasedPyright typing for entire project
  • Resource filtering expanded to include logical operators

​
Fixed

  • Various bugs
  • Use new config arrangement everywhere
  • Remove hardcoded responses
​
v2.0.0

​
Added

  • Ability to get a peer’s working representation
  • Metadata to all data primitives (Workspaces, Peers, Sessions, Messages)
  • Internal metadata to store Honcho’s state no longer exposed in API
  • Batch message operations and enhanced message querying with token and message count limits
  • Search and summary functionalities scoped by workspace, peer, and session
  • Session context retrieval with summaries and token allocatio
  • HNSW Index for Documents Table
  • Centralized Configuration via Environment Variables or config.toml file

​
Changed

  • New architecture centered around the concept of a “peer” replaces the former “app”/“user”/“session” paradigm
  • Workspaces replace “apps” as top-level namespace
  • Peers replace “users”
  • Sessions no longer nested beneath peers and no longer limited to a single user-assistant model. A session exists independently of any one peer and peers can be added to and removed from sessions.
  • Dialectic API is now part of the Peer, not the Session
  • Dialectic API now allows queries to be scoped to a session or “targeted” to a fellow peer
  • Database schema migrated to adopt workspace/peer/session naming and structure
  • Authentication and JWT scopes updated to workspace/peer/session hierarchy
  • Queue processing now works on ‘work units’ instead of sessions
  • Message token counting updated with tiktoken integration and fallback heuristic
  • Queue and message processing updated to handle sender/target and task types for multi-peer scenarios

​
Fixed

  • Improved error handling and validation for batch message operations and metadata
  • Database Sessions to be more atomic to reduce idle in transaction time

​
Removed

  • Metamessages removed in favor of metadata
  • Collections and Documents no longer exposed in the API, solely internal
  • Obsolete tests for apps, users, collections, documents, and metamessages
​
v1.1.0

​
Added

  • Normalize resources to remove joins and increase query performance
  • Query tracing for debugging

​
Changed

  • /list endpoints to not require a request body
  • metamessage_type to label with backwards compatability
  • Database Provisioning to rely on alembic
  • Database Session Manager to explicitly rollback transactions before closing the connection

​
Fixed

  • Alembic Migrations to include initial database migrations
  • Sentry Middleware to not report Honcho Exceptions
​
v1.0.0

​
Added

  • JWT based API authentication
  • Configurable logging
  • Consolidated LLM Inference via ModelClient class
  • Dynamic logging configurable via environment variables

​
Changed

  • Deriver & Dialectic API to use Hybrid Memory Architecture
  • Metamessages are not strictly tied to a message
  • Database provisioning is a separate script instead of happening on startup
  • Consolidated session/chat and session/chat/stream endpoints

​
Previous Releases

For a complete history of all releases, see our GitHub Releases page.

​
Getting Help

If you encounter issues using the Honcho API or its SDKs:

  1. Open an issue on GitHub
  2. Join our Discord community for support

Welcome to the Honcho changelog! This section documents all notable changes to the Honcho API and SDKs.

​
Honcho API and SDK Changelogs

​
v2.0.4 (Current)

​
Fixed

  • Migration/provision scripts did not have correct database connection arguments, causing timeouts
​
v2.0.3

​
Fixed

  • Bug that causes runtime error when Sentry flags are enabled
​
v2.0.2

​
Fixed

  • Database initialization was misconfigured and led to provision_db script failing: switch to consistent working configuration with transaction pooler
​
v2.0.1

​
Added

  • Ergonomic SDKs for Python and TypeScript (uses Stainless underneath)
  • Deriver Queue Status endpoint
  • Complex arbitrary filters on workspace/session/peer/message
  • Message embedding table for full semantic search

​
Changed

  • Overhauled documentation
  • BasedPyright typing for entire project
  • Resource filtering expanded to include logical operators

​
Fixed

  • Various bugs
  • Use new config arrangement everywhere
  • Remove hardcoded responses
​
v2.0.0

​
Added

  • Ability to get a peer’s working representation
  • Metadata to all data primitives (Workspaces, Peers, Sessions, Messages)
  • Internal metadata to store Honcho’s state no longer exposed in API
  • Batch message operations and enhanced message querying with token and message count limits
  • Search and summary functionalities scoped by workspace, peer, and session
  • Session context retrieval with summaries and token allocatio
  • HNSW Index for Documents Table
  • Centralized Configuration via Environment Variables or config.toml file

​
Changed

  • New architecture centered around the concept of a “peer” replaces the former “app”/“user”/“session” paradigm
  • Workspaces replace “apps” as top-level namespace
  • Peers replace “users”
  • Sessions no longer nested beneath peers and no longer limited to a single user-assistant model. A session exists independently of any one peer and peers can be added to and removed from sessions.
  • Dialectic API is now part of the Peer, not the Session
  • Dialectic API now allows queries to be scoped to a session or “targeted” to a fellow peer
  • Database schema migrated to adopt workspace/peer/session naming and structure
  • Authentication and JWT scopes updated to workspace/peer/session hierarchy
  • Queue processing now works on ‘work units’ instead of sessions
  • Message token counting updated with tiktoken integration and fallback heuristic
  • Queue and message processing updated to handle sender/target and task types for multi-peer scenarios

​
Fixed

  • Improved error handling and validation for batch message operations and metadata
  • Database Sessions to be more atomic to reduce idle in transaction time

​
Removed

  • Metamessages removed in favor of metadata
  • Collections and Documents no longer exposed in the API, solely internal
  • Obsolete tests for apps, users, collections, documents, and metamessages
​
v1.1.0

​
Added

  • Normalize resources to remove joins and increase query performance
  • Query tracing for debugging

​
Changed

  • /list endpoints to not require a request body
  • metamessage_type to label with backwards compatability
  • Database Provisioning to rely on alembic
  • Database Session Manager to explicitly rollback transactions before closing the connection

​
Fixed

  • Alembic Migrations to include initial database migrations
  • Sentry Middleware to not report Honcho Exceptions
​
v1.0.0

​
Added

  • JWT based API authentication
  • Configurable logging
  • Consolidated LLM Inference via ModelClient class
  • Dynamic logging configurable via environment variables

​
Changed

  • Deriver & Dialectic API to use Hybrid Memory Architecture
  • Metamessages are not strictly tied to a message
  • Database provisioning is a separate script instead of happening on startup
  • Consolidated session/chat and session/chat/stream endpoints

​
Previous Releases

For a complete history of all releases, see our GitHub Releases page.

​
Getting Help

If you encounter issues using the Honcho API or its SDKs:

  1. Open an issue on GitHub
  2. Join our Discord community for support