migrate-honcho-ts

Migrate Honcho TypeScript SDK code from v1.6.0 to v2.0.0.

6.5k|796|Updated Sep 10, 2023
One-click install
npx skills add https://github.com/plastic-labs/honcho --skill migrate-honcho-ts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-honcho-ts
Source: https://github.com/plastic-labs/honcho/tree/main/.claude/skills/migrate-honcho-ts
Command: npx skills add https://github.com/plastic-labs/honcho --skill migrate-honcho-ts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineers through upgrading Honcho TypeScript SDK code from v1.6.0 to v2.0.0, addressing breaking changes and removed APIs to reduce integration risk.

Core Features & Use Cases

  • Migrate core API names (e.g., getConfig -> getConfiguration, setConfig -> setConfiguration) across client, peer, and session layers.
  • Replace .core usages with .http and adapt to the new HTTP client model.
  • Convert snake_case properties to camelCase (e.g., created_at -> createdAt, token_count -> tokenCount) and update related data structures.
  • Update streaming to chatStream() and remove deprecated features like pollDeriverStatus(), with guidance for queueStatus() usage.
  • Support structured migrations with step-by-step examples and a migration checklist to ensure no breaking changes are missed.

Quick Start

  1. Review the MIGRATION-CHECKLIST.md and align your project with the new API surface.
  2. Update dependencies by removing @honcho-ai/core and installing the v2 SDK.
  3. Refactor code to replace deprecated APIs; for example, call honcho.getConfiguration() and peer.context({ ... }) instead of legacy methods.
  4. Ensure all property names follow camelCase conventions for messages and configurations.

Frequently Asked Questions about migrate-honcho-ts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Honcho TypeScript SDK from v1.6.0 to v2.0.0?

To migrate Honcho TypeScript SDK from v1.6.0 to v2.0.0, remove the @honcho-ai/core dependency, install the v2 SDK, and refactor deprecated APIs to align with the new HTTP client model and camelCase conventions.

What breaking changes were introduced in Honcho SDK v2.0.0?

Breaking changes in Honcho SDK v2.0.0 include replacing .core with .http, renaming getConfig to getConfiguration, converting snake_case properties to camelCase, and removing the Representation class and pollDeriverStatus API.

How do I update streaming APIs when upgrading to Honcho TS SDK v2?

When upgrading to Honcho TS SDK v2, update streaming APIs by adopting the new chatStream() method and replacing deprecated queue polling functions like pollDeriverStatus() with the new queueStatus() API.

Why did my Honcho SDK properties break after upgrading to v2?

Honcho SDK properties broke after upgrading to v2 because v2.0.0 enforces camelCase conventions across all message fields and configurations, requiring updates to legacy snake_case data structures like created_at and token_count.

Do I need to remove @honcho-ai/core to upgrade to Honcho SDK v2?

Yes, you need to remove the @honcho-ai/core package to upgrade to Honcho SDK v2, as v2.0.0 consolidates dependencies into the main SDK and replaces the old .core client model with the new .http client.

What is the best way to handle API renames in the Honcho TypeScript SDK?

The best way to handle API renames in the Honcho TypeScript SDK is to systematically refactor client, peer, and session layers, replacing legacy methods like setConfig with setConfiguration and updating context calls.