Greptile Overview
\\r\\n\\r\\n### Greptile Summary\\r\\n\\r\\nThis PR fixes the Python chat example and inmemorydb plugin to work together, adds Python quickstart documentation, and improves Character attribute handling. The changes include:\\r\\n\\r\\n**Key Improvements:**\\r\\n- Adds comprehensive Python quickstart documentation with examples\\r\\n- Fixes inmemorydb plugin to use proper Plugin class instead of dict\\r\\n- Enhances inmemorydb adapter to handle Pydantic models in create_memory/update_memory\\r\\n- Updates character provider to safely access optional attributes with getattr()\\r\\n- Adds dotenv support to chat example for .env file loading\\r\\n- Adds useful helper methods to AgentRuntime (get_available_actions, get_entity alias)\\r\\n- Enhances get_memories() to accept keyword arguments\\r\\n\\r\\n**Critical Issues Found:**\\r\\n1. **Bug in adapter.py line 329**: The update_memory() method references the wrong variable name (`memory` instead of `memory_dict`), which will cause AttributeError when processing Pydantic models\\r\\n2. **Bug in character.py lines 70-73**: Inconsistent attribute access - uses getattr() in function body but direct access in return data dict, causing AttributeError for optional attributes\\r\\n3. **Missing dependency in chat.py**: Imports python-dotenv but it's not in requirements.txt\\r\\n4. **Incomplete documentation**: Quickstart guide doesn't include inmemorydb plugin installation that the chat example now requires\\r\\n\\r\\n**Impact:**\\r\\nThe bugs in adapter.py and character.py are critical and will cause runtime errors. The missing dependencies will prevent users from running the example successfully.\\r\\n\\r\\n### Confidence Score: 1/5\\r\\n\\r\\n- This PR contains critical bugs that will cause runtime failures and prevent the chat example from working\\r\\n- Score reflects two critical logic errors (wrong variable reference in adapter.py:329 and inconsistent attribute access in character.py:70-73) plus missing dependencies that will cause import errors. These issues will break the example for users and cause AttributeErrors at runtime.\\r\\n- Pay close attention to plugins/plugin-inmemorydb/python/elizaos_plugin_inmemorydb/adapter.py (line 329 bug), packages/python/elizaos/bootstrap/providers/character.py (lines 70-73 inconsistency), and examples/chat/python/chat.py (missing python-dotenv dependency)\\r\\n\\r\\nImportant Files Changed
\\r\\n\\r\\n\\r\\n\\r\\nFile Analysis\\r\\n\\r\\n\\r\\n\\r\\n| Filename | Score | Overview |\\r\\n|----------|-------|----------|\\r\\n| docs/python-quickstart.md | 3/5 | New documentation file added. Missing plugin-inmemorydb installation instruction that the chat example now requires. |\\r\\n| examples/chat/python/chat.py | 2/5 | Added dotenv and inmemorydb support. Missing python-dotenv dependency in requirements, which will cause import errors. |\\r\\n| packages/python/elizaos/bootstrap/providers/character.py | 2/5 | Fixed to use getattr for optional character attributes. Critical bug: return data dict directly accesses attributes without getattr, causing AttributeError. |\\r\\n| plugins/plugin-inmemorydb/python/elizaos_plugin_inmemorydb/adapter.py | 1/5 | Enhanced get_memories(), create_memory(), and update_memory() to handle Pydantic models. Critical bug in update_memory line 329: uses wrong variable name. |\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nSequence Diagram
\\r\\n\\r\\n```mermaid\\r\\nsequenceDiagram\\r\\n participant User\\r\\n participant chat.py\\r\\n participant dotenv\\r\\n participant AgentRuntime\\r\\n participant OpenAIPlugin\\r\\n participant InMemoryDBPlugin\\r\\n participant InMemoryAdapter\\r\\n participant CharacterProvider\\r\\n\\r\\n User->>chat.py: Run python chat.py\\r\\n chat.py->>dotenv: load_dotenv(env_path)\\r\\n dotenv-->>chat.py: Load .env from repo root\\r\\n \\r\\n chat.py->>AgentRuntime: Create with character and plugins\\r\\n AgentRuntime->>OpenAIPlugin: Initialize OpenAI plugin\\r\\n AgentRuntime->>InMemoryDBPlugin: Initialize InMemoryDB plugin\\r\\n InMemoryDBPlugin->>InMemoryAdapter: create_database_adapter(agent_id)\\r\\n InMemoryAdapter-->>InMemoryDBPlugin: Return adapter instance\\r\\n InMemoryDBPlugin->>AgentRuntime: register_database_adapter(adapter)\\r\\n \\r\\n AgentRuntime->>CharacterProvider: get_character_context()\\r\\n CharacterProvider->>CharacterProvider: Use getattr() for optional attributes\\r\\n CharacterProvider-->>AgentRuntime: Return character context\\r\\n \\r\\n AgentRuntime-->>chat.py: Runtime initialized\\r\\n \\r\\n User->>chat.py: Type message\\r\\n chat.py->>AgentRuntime: handle_message(runtime, memory)\\r\\n AgentRuntime->>InMemoryAdapter: get_memories(params)\\r\\n InMemoryAdapter-->>AgentRuntime: Return memories\\r\\n AgentRuntime->>OpenAIPlugin: Generate response\\r\\n OpenAIPlugin-->>AgentRuntime: Return response\\r\\n AgentRuntime->>InMemoryAdapter: create_memory(memory_dict)\\r\\n InMemoryAdapter-->>AgentRuntime: Memory stored\\r\\n AgentRuntime-->>chat.py: Return result\\r\\n chat.py-->>User: Display response\\r\\n```\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n* **New Features**\\n * In-memory database plugin for agent memory.\\n * Token-by-token streaming for chat responses and streaming endpoints.\\n * Atropos data-generation, trajectory tooling, and TextWorld agent integrations.\\n * New Tic\u2011Tac\u2011Toe AI/player options and interactive configuration.\\n\\n* **Documentation**\\n * Expanded developer setup, examples, runnable chat walkthroughs, and new Atropos CLI flags.\\n\\n* **Other**\\n * Updated Python packaging/requirements and repository-root .env loading for examples.\\n\\n\u270f\ufe0f Tip: You can customize this high-level summary in your review settings.\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2026-01-13T00:34:32Z\",\n \"mergedAt\": \"2026-01-22T01:20:54Z\",\n \"additions\": 17483,\n \"deletions\": 8280\n },\n {\n \"id\": \"PR_kwDOMT5cIs670Y6I\",\n \"title\": \"fix: plugin-bootstrap (+ sql minor) actions/providers for serverId => messageServerId change\",\n \"author\": \"odilitime\",\n \"number\": 6333,\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\n\\r\\n## Why are we doing this? Any context or related work?\\r\\n\\r\\nUser reports of 1.7.0 not working with plugin-discord 1.3.3\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\nMy changes do not require a change to the project documentation.\\r\\n\\n\\n---\\n\\n> [!NOTE]\\n> **Adds onboarding and role management, refactors providers, and updates schema**\\n> \\n> - New `UPDATE_SETTINGS` action: extracts multiple settings, persists to `world.metadata.settings` with salting/unsalting, generates success/failure/error responses, and completes onboarding when required settings are done\\n> - New/updated `SETTINGS` provider: reads/decrypts settings from world metadata, supports onboarding (DM) vs regular contexts, and outputs concise status with guidance\\n> - New/updated `WORLD` provider: surfaces world/room/channel/participant summaries and structured channel categorization for prompts\\n> - New `UPDATE_ROLE` action: parses XML for role assignments, enforces permission rules, updates `world.metadata.roles`, and persists via `updateWorld`\\n> - Tests: comprehensive event lifecycle and reaction handling, entity join/leave, and platform-agnostic `shouldRespond` mention/reply logic\\n> - SQL: `packages/plugin-sql/src/schema/room.ts` now defines `messageServerId` as `uuid('message_server_id')` (doc/comment cleanup)\\n> \\n> Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 25d98528e8c98217fbaa63a5e430202a575800e6. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).\\n\\n\\n\\n\\nGreptile Summary
\\n\\n\\nCompletes the migration from deprecated `serverId` to `messageServerId` across plugin-bootstrap actions/providers and plugin-sql schema.\\n\\n**Key Changes:**\\n- Updated `packages/plugin-bootstrap/src/actions/roles.ts` validate function to check `room.messageServerId` instead of accessing `message.content.serverId`\\n- Updated logger metadata keys from `serverId` to `messageServerId` in actions/settings.ts, providers/settings.ts, and action return data in roles.ts\\n- Updated provider output in providers/world.ts to use `messageServerId` field name\\n- Updated JSDoc comment in plugin-sql schema to reflect the correct column name\\n- Updated test mocks and fixtures to use `messageServerId`\\n\\nThis PR addresses user-reported compatibility issues between eliza v1.7.0 and plugin-discord v1.3.3 by ensuring consistent use of the new `messageServerId` field name throughout the codebase. The deprecated `serverId` field still exists in the core types for backward compatibility but is no longer referenced in plugin-bootstrap or plugin-sql.\\n\\nConfidence Score: 5/5
\\n\\n\\n- This PR is safe to merge with minimal risk\\n- The changes are straightforward field name updates that align with an existing migration (commit 6d1b928c). All changes are consistent, the deprecated field remains in core types for backward compatibility, and the PR only updates references in plugin-bootstrap and plugin-sql to use the new field name. The changes fix reported compatibility issues without introducing breaking changes.\\n- No files require special attention\\n\\nImportant Files Changed
\\n\\n\\n\\n\\n| Filename | Overview |\\n|----------|----------|\\n| packages/plugin-sql/src/schema/room.ts | Updated JSDoc comment from `serverId` to `messageServerId` to match the column definition |\\n| packages/plugin-bootstrap/src/actions/settings.ts | Updated logger metadata keys from `serverId` to `messageServerId` for consistency |\\n| packages/plugin-bootstrap/src/providers/settings.ts | Updated logger metadata key from `serverId` to `messageServerId` for consistency |\\n| packages/plugin-bootstrap/src/providers/world.ts | Updated provider output to use `messageServerId` instead of deprecated `serverId` field |\\n| packages/plugin-bootstrap/src/actions/roles.ts | Refactored validation to check room.messageServerId and updated logger/return data to use `messageServerId` |\\n\\n\\n\\n\\n\\nSequence Diagram
\\n\\n```mermaid\\nsequenceDiagram\\n participant User\\n participant Action as Action/Provider\\n participant Runtime\\n participant Database\\n \\n Note over User,Database: serverId \u2192 messageServerId Migration Flow\\n \\n User->>Action: Trigger action (e.g., UPDATE_ROLE)\\n Action->>Runtime: getRoom(roomId)\\n Runtime->>Database: Query room table\\n Database-->>Runtime: Return Room with messageServerId\\n Runtime-->>Action: Room object\\n \\n alt Validate messageServerId exists\\n Action->>Action: Check room.messageServerId\\n Action->>Runtime: getWorld(worldId)\\n Runtime->>Database: Query world\\n Database-->>Runtime: Return World with messageServerId\\n Runtime-->>Action: World object\\n end\\n \\n Action->>Action: Process with world.messageServerId\\n Action->>Runtime: updateWorld(world)\\n Runtime->>Database: Update world metadata\\n Database-->>Runtime: Success\\n \\n Action->>Action: Log with messageServerId key\\n Action-->>User: Return result with messageServerId\\n \\n Note over Action,Database: All references to deprecated serverIdupdated to messageServerId\\n```\\n\\n\\n\\n\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n* **Breaking Changes**\\n * Renamed field `serverId` to `messageServerId` across room and world data structures, affecting API responses and database schema. This impacts any code consuming room or world context data.\\n\\n* **Tests**\\n * Updated test utilities and fixtures to reflect the field name change for consistency with production code.\\n\\n\u270f\ufe0f Tip: You can customize this high-level summary in your review settings.\\n\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2026-01-07T01:11:56Z\",\n \"mergedAt\": \"2026-01-07T10:46:02Z\",\n \"additions\": 5363,\n \"deletions\": 23\n },\n {\n \"id\": \"PR_kwDOMT5cIs6-HSpn\",\n \"title\": \"V2.0.0: dynamic execution engine (test if context is going to blown)\",\n \"author\": \"odilitime\",\n \"number\": 6384,\n \"body\": \"Redo #6113 for 2.0.0, first pass\\n\\n\\n---\\n\\n> [!NOTE]\\n> Introduces a validation-aware, schema-driven prompt execution path and applies it across runtimes and message flows.\\n> \\n> - Adds `dynamic_prompt_exec_from_state`/`dynamicPromptExecFromState` (TS/Python/Rust) with per-field/checkpoint UUID validation codes, required-field checks, and retry with backoff; supports XML/JSON\\n> - Refactors message handling (should-respond, single-shot, multi-step decision, final summary) to use structured schemas instead of ad-hoc parsing\\n> - Implements streaming support in TS with `ValidationStreamExtractor`, `MarkableExtractor`, and streaming context helpers; emits rich `StreamEvent`s\\n> - Introduces shared types: `SchemaRow`, `RetryBackoffConfig`, `StreamEvent(Type)` in Python/Rust/TS type modules\\n> - Adds XML parsing utilities (nested-safe) and normalizes structured responses; basic templating in Rust, Handlebars in TS\\n> - Exposes validation level configuration (0\u20133) and model selection; defaults to large text models\\n> \\n> Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 1e447bbc005cbad715eb819aba27eb35b54aa5b8. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).\\n\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n* **New Features**\\n * Added dynamic prompt execution with state injection and schema-driven validation.\\n * Enabled validation-aware streaming with configurable validation levels (0-3).\\n * Introduced built-in retry logic with exponential backoff for improved resilience.\\n * Support for structured output validation across JSON and XML formats.\\n * Per-field and checkpoint-level validation for enhanced data integrity.\\n\\n\u270f\ufe0f Tip: You can customize this high-level summary in your review settings.\\n\\n\\n\\n\\n\\n
Greptile Summary
\\n\\n\\nIntroduces `dynamicPromptExecFromState()` across Python, Rust, and TypeScript runtimes to provide schema-driven prompt execution with context validation via UUID codes. The implementation detects when LLMs truncate output due to limited context windows by injecting validation codes at strategic positions (start/middle/end or per-field). Supports four validation levels (0=trusted to 3=full), exponential backoff retries, and optional validation-aware streaming via `ValidationStreamExtractor`.\\n\\n**Key changes:**\\n- Cross-language API consistency for dynamic prompt execution with state injection\\n- Validation code system to detect context overflow (4 levels: trusted, progressive, checkpoint, full)\\n- Streaming integration with progressive validation and retry support\\n- Schema-based structured output parsing (XML/JSON) with required field validation\\n- Performance metrics tracking per model+schema combination (TypeScript only)\\n- Comprehensive type definitions (`SchemaRow`, `RetryBackoffConfig`, `StreamEvent`)\\n\\n**Critical issues in Python implementation:**\\n- Callable prompt invocation wraps state incorrectly (`{\\\"state\\\": state}` vs direct state access)\\n- Template substitution assumes `state.values` has dynamic attributes accessible via `dir()`, incompatible with protobuf State\\n- XML parsing regex `\\\\w+` won't match validation field names with underscores like `code_text_start`\\n\\n**Minor issues:**\\n- Rust template rendering uses basic string replacement instead of full Handlebars compiler\\n- TypeScript `_smartRetryContext` deletion during retry loop prevents reuse on subsequent attempts\\n- ValidationStreamExtractor abort handling may leave inconsistent state\\n\\nConfidence Score: 3/5
\\n\\n\\n- Python implementation has runtime errors that will break production usage; TypeScript and Rust implementations are safer but need testing\\n- Score reflects critical logical errors in Python (3 bugs that will cause runtime failures), plus architecture differences across languages. TypeScript implementation is most complete with metrics and full Handlebars support. Python bugs must be fixed before merge to avoid breaking callers.\\n- `packages/python/elizaos/runtime.py` requires immediate fixes for callable invocation, state.values access pattern, and XML regex. Test the Python implementation thoroughly before merging.\\n\\nImportant Files Changed
\\n\\n\\n\\n\\n| Filename | Overview |\\n|----------|----------|\\n| packages/python/elizaos/runtime.py | Adds `dynamic_prompt_exec_from_state` with validation codes and retry logic; has critical bugs in callable invocation, state.values access, and XML parsing regex |\\n| packages/rust/src/runtime.rs | Implements `dynamic_prompt_exec_from_state` with validation and retry; template rendering is basic string replacement vs full Handlebars |\\n| packages/typescript/src/runtime.ts | Implements `dynamicPromptExecFromState` with metrics, streaming, and validation; minor issue with `_smartRetryContext` deletion timing |\\n| packages/typescript/src/utils/streaming.ts | Implements validation-aware streaming with multiple extractor types; minor state inconsistency on abort signal |\\n\\n\\n\\n\\n\\nSequence Diagram
\\n\\n```mermaid\\nsequenceDiagram\\n participant Client\\n participant Runtime\\n participant ValidationExtractor\\n participant LLM\\n participant Parser\\n\\n Client->>Runtime: dynamicPromptExecFromState(state, schema, options)\\n \\n Note over Runtime: Generate validation codes(UUID snippets)\\n \\n Runtime->>Runtime: Build extended schema
with validation fields\\n \\n Runtime->>Runtime: Inject codes into prompt
(initial, middle, end)\\n \\n Runtime->>Runtime: Compile template with
Handlebars/state values\\n \\n alt Streaming enabled\\n Runtime->>ValidationExtractor: Create extractor
(level, schema, codes)\\n end\\n \\n loop Retry attempts (0 to maxRetries)\\n Runtime->>LLM: Generate text with prompt\\n \\n alt Streaming\\n loop Stream chunks\\n LLM-->>ValidationExtractor: chunk\\n ValidationExtractor->>ValidationExtractor: Extract field content\\n ValidationExtractor->>ValidationExtractor: Check per-field codes
(level 0-1)\\n ValidationExtractor-->>Client: Stream validated content\\n end\\n else Non-streaming\\n LLM-->>Runtime: Complete response\\n end\\n \\n Runtime->>Runtime: Clean response
(remove
(one_initial, one_middle, etc)\\n end\\n \\n Runtime->>Runtime: Validate required fields
are present and non-empty\\n \\n alt All validations pass\\n alt Streaming (level 2-3)\\n Runtime->>ValidationExtractor: flush()\\n ValidationExtractor-->>Client: Buffered content\\n end\\n Runtime->>Runtime: Remove validation code fields\\n Runtime->>Runtime: Update success metrics\\n Runtime-->>Client: Return parsed response\\n else Validation fails\\n alt Has retries remaining\\n Runtime->>Runtime: Calculate backoff delay\\n Runtime->>Runtime: Wait for backoff\\n Note over Runtime: Loop continues with retry\\n else No retries left\\n Runtime->>Runtime: Update failure metrics\\n Runtime-->>Client: Return null\\n end\\n end\\n end\\n```\\n\\n\\n\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2026-01-20T02:29:59Z\",\n \"mergedAt\": null,\n \"additions\": 4309,\n \"deletions\": 1591\n },\n {\n \"id\": \"PR_kwDOMT5cIs6gRJJ1\",\n \"title\": \"feature/docker starter\",\n \"author\": \"bealers\",\n \"number\": 5670,\n \"body\": \"# Docker Infrastructure for elizaOS - foundation stage\\r\\n\\r\\nAdds Docker support with CLI integration and organized target structure for both starter projects and monorepo development.\\r\\n\\r\\n## New Commands\\r\\n\\r\\n```bash\\r\\n# Development with hot reload\\r\\nelizaos dev --docker\\r\\n\\r\\n# Production deployment \\r\\nelizaos start --docker\\r\\n```\\r\\n\\r\\n## How It Works\\r\\n\\r\\n### Starter Project Context\\r\\nWhen using `elizaos create my-project`, the generated project includes Docker configs:\\r\\n\\r\\n```bash\\r\\nelizaos create my-project\\r\\ncd my-project\\r\\nelizaos dev --docker # Starts containerized dev environment\\r\\nelizaos start --docker # Starts production-ready container\\r\\n```\\r\\n\\r\\n**Benefits:**\\r\\n- **Consistent environments** across team members\\r\\n- **No local dependency conflicts** (Node versions, system packages)\\r\\n- **One-command setup** for new developers\\r\\n- **Production-like testing** locally\\r\\n\\r\\n### Monorepo Context\\r\\nFor ElizaOS core development, use organized Docker targets:\\r\\n\\r\\n```bash\\r\\n# Development\\r\\ncd docker/targets/dev && docker-compose up\\r\\n\\r\\n# Production\\r\\ncd docker/targets/prod && docker-compose up\\r\\n\\r\\n# Documentation\\r\\ncd docker/targets/docs && docker-compose up\\r\\n```\\r\\n## Structure\\r\\n\\r\\n```\\r\\ndocker/targets/\\r\\n\u251c\u2500\u2500 dev/ # Development: hot reload, debug ports, volume mounting\\r\\n\u251c\u2500\u2500 prod/ # Production: optimized builds, health checks, PostgreSQL\\r\\n\u2514\u2500\u2500 docs/ # Documentation: fast nginx serving\\r\\n```\\r\\n\\r\\n## Testing\\r\\n\\r\\n```bash\\r\\ncd docker/tests && bun test\\r\\n\\r\\n# Test CLI integration\\r\\nelizaos create test-project\\r\\ncd test-project\\r\\nelizaos dev --docker\\r\\n```\\r\\n\\r\\n## Compatibility\\r\\n\\r\\n- No breaking changes\\r\\n- TEE functionality preserved (`tee-docker-compose.yaml`)\\r\\n- Project starter templates include Docker configs \\r\\n\\r\\n## Next\\r\\n\\r\\n- reduce prod image size futher, use `docker-slim`\\r\\n- take prod image and apply to docker registry\\r\\n- build out `elizaos deploy`, or similar\\r\\n- document popular providers, Railway, Digital Ocean, Hetzner\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-07-23T13:15:34Z\",\n \"mergedAt\": null,\n \"additions\": 4053,\n \"deletions\": 177\n }\n ],\n \"codeChanges\": {\n \"additions\": 25706,\n \"deletions\": 8753,\n \"files\": 269,\n \"commitCount\": 379\n },\n \"completedItems\": [\n {\n \"title\": \"refactor(default-message-service): optimize provider handling in MultiStep\",\n \"prNumber\": 6263,\n \"type\": \"refactor\",\n \"body\": \"# Risks\\r\\n\\r\\nLow. The change only affects the internal execution order of providers in multi-step mode. All providers still execute and return results - just faster.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nConverts sequential provider \",\n \"files\": [\n \".env.example\",\n \"packages/cli/tests/test-timeouts.ts\",\n \"packages/core/src/__tests__/message-service.test.ts\",\n \"packages/core/src/services/default-message-service.ts\"\n ]\n },\n {\n \"title\": \"feat(core): enhance multi-step workflow with retry logic and parameter extraction\",\n \"prNumber\": 6286,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nEnhances multi-step workflows with retry logic and parameter extraction capabilities.\\n\\n### Changes\\n\\n- **Retry logic for XML parsing**: Multi-step workflows now retry parsing up to 5 times (configurable via `MULTISTEP_PARSE_RETRI\",\n \"files\": [\n \"packages/core/src/prompts.ts\",\n \"packages/core/src/services/default-message-service.ts\",\n \"packages/plugin-bootstrap/src/__tests__/multi-step.test.ts\",\n \"packages/plugin-bootstrap/src/providers/actions.ts\",\n \"packages/core/src/runtime.ts\",\n \".cursor\",\n \"examples/tsconfig.json\",\n \"packages/core/src/__tests__/streaming-context.test.ts\",\n \"packages/core/src/streaming-context.ts\",\n \"packages/core/src/types/streaming.ts\",\n \"packages/core/src/utils/streaming.ts\",\n \"packages/cli/tests/unit/characters/README.md\",\n \"bun.lock\",\n \"lerna.json\",\n \"packages/api-client/package.json\",\n \"packages/app/package.json\",\n \"packages/cli/package.json\",\n \"packages/cli/src/commands/deploy/utils/docker-build.ts\",\n \"packages/client/package.json\",\n \"packages/client/src/components/chat.tsx\",\n \"packages/config/package.json\",\n \"packages/core/package.json\",\n \"packages/core/src/__tests__/runtime.test.ts\",\n \"packages/elizaos/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-bootstrap/src/__tests__/test-utils.ts\",\n \"packages/plugin-bootstrap/src/actions/roles.ts\",\n \"packages/plugin-bootstrap/src/providers/settings.ts\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-quick-starter/package.json\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-sql/src/__tests__/integration/base-adapter-methods.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/entity-crud.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/memory.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/world.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/migration-before-1.6.5.test.ts\",\n \"packages/plugin-sql/src/__tests__/unit/utils.test.ts\",\n \"packages/plugin-sql/src/base.ts\",\n \"packages/plugin-sql/src/neon/adapter.ts\",\n \"packages/plugin-sql/src/pg/adapter.ts\",\n \"packages/plugin-sql/src/pglite/adapter.ts\",\n \"packages/plugin-starter/package.json\",\n \"packages/project-starter/package.json\",\n \"packages/project-starter/src/character.ts\",\n \"packages/project-tee-starter/package.json\",\n \"packages/server/package.json\",\n \"packages/server/src/__tests__/unit/api/agents-runs.test.ts\",\n \"packages/server/src/api/agents/runs.ts\",\n \"packages/server/src/api/index.ts\",\n \"packages/server/src/api/memory/rooms.ts\"\n ]\n },\n {\n \"title\": \"fix: Enable hot reload for backend development\",\n \"prNumber\": 6293,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nImplements comprehensive hot reload functionality for backend development. When TypeScript files in watched packages are modified, the system automatically rebuilds the CLI and restarts the server with health verification.\\n\\nPrev\",\n \"files\": [\n \"scripts/__tests__/dev-watch.test.ts\",\n \"scripts/dev-watch.js\"\n ]\n },\n {\n \"title\": \"feat: unified hooks with multi-transport support (HTTP/SSE/WebSocket)\",\n \"prNumber\": 6300,\n \"type\": \"feature\",\n \"body\": \"This PR introduces unified client hooks with multi-transport support and aligns transport naming between `api-client` and `server` packages.\\r\\n\\r\\n### Key Changes\\r\\n\\r\\n**Client Hooks (packages/client)**\\r\\n- New `useElizaChat` hook - unified inter\",\n \"files\": [\n \"packages/api-client/src/__tests__/services/sessions.test.ts\",\n \"packages/api-client/src/services/sessions.ts\",\n \"packages/api-client/src/types/sessions.ts\",\n \"packages/client/src/components/agent-card.cy.tsx\",\n \"packages/client/src/components/agent-card.tsx\",\n \"packages/client/src/components/agent-log-viewer.tsx\",\n \"packages/client/src/components/agent-sidebar.tsx\",\n \"packages/client/src/components/chat.tsx\",\n \"packages/client/src/components/profile-overlay.tsx\",\n \"packages/client/src/components/server-management.tsx\",\n \"packages/client/src/hooks/__tests__/use-dm-channels.test.ts\",\n \"packages/client/src/hooks/__tests__/use-http-chat.test.ts\",\n \"packages/client/src/hooks/__tests__/use-sse-chat.test.ts\",\n \"packages/client/src/hooks/index.ts\",\n \"packages/client/src/hooks/use-agent-management.ts\",\n \"packages/client/src/hooks/use-elevenlabs-voices.ts\",\n \"packages/client/src/hooks/use-eliza-chat.ts\",\n \"packages/client/src/hooks/use-eliza.ts\",\n \"packages/client/src/hooks/use-http-chat.ts\",\n \"packages/client/src/hooks/use-query-hooks.ts\",\n \"packages/client/src/hooks/use-socket-chat.ts\",\n \"packages/client/src/hooks/use-sse-chat.ts\",\n \"packages/client/src/lib/api-type-mappers.ts\",\n \"packages/client/src/lib/utils.ts\",\n \"packages/client/src/routes/agent-detail.tsx\",\n \"packages/client/src/routes/agent-list.tsx\",\n \"packages/client/src/routes/agent-settings.tsx\",\n \"packages/client/src/routes/chat.tsx\",\n \"packages/client/src/routes/home.tsx\",\n \"packages/client/src/types.ts\",\n \"packages/client/src/types/index.ts\",\n \"packages/server/src/__tests__/fixtures/socketio-client.fixture.ts\",\n \"packages/server/src/__tests__/integration/http-transport.test.ts\",\n \"packages/server/src/__tests__/integration/socketio-infrastructure.test.ts\",\n \"packages/server/src/__tests__/integration/sse-transport.test.ts\",\n \"packages/server/src/__tests__/integration/websocket-transport.test.ts\",\n \"packages/server/src/__tests__/unit/api/channels-mode.test.ts\",\n \"packages/server/src/__tests__/unit/api/response-handlers.test.ts\",\n \"packages/server/src/__tests__/unit/api/sessions.test.ts\",\n \"packages/server/src/__tests__/unit/features/socketio-router.test.ts\",\n \"packages/server/src/api/messaging/channels.ts\",\n \"packages/server/src/api/messaging/sessions.ts\",\n \"packages/server/src/api/shared/constants.ts\",\n \"packages/server/src/api/shared/response-handlers.ts\",\n \"packages/server/src/api/shared/validation.ts\",\n \"packages/server/src/index.ts\",\n \"packages/server/src/socketio/index.ts\"\n ]\n },\n {\n \"title\": \"chore(license): update year to 2026\",\n \"prNumber\": 6301,\n \"type\": \"other\",\n \"body\": \"Annual copyright year update.\\n\\n- Updated year: 2025 -> 2026\\n- Files affected: LICENSE\\n\\n\\n\\n