{ "interval": { "intervalStart": "2025-09-02T00:00:00.000Z", "intervalEnd": "2025-09-03T00:00:00.000Z", "intervalType": "day" }, "repository": "elizaos/eliza", "overview": "From 2025-09-02 to 2025-09-03, elizaos/eliza had 6 new PRs (8 merged), 2 new issues, and 10 active contributors.", "topIssues": [ { "id": "I_kwDOMT5cIs7JUUNl", "title": "Observability GUI for event runs", "author": "borisudovicic", "number": 5868, "repository": "elizaos/eliza", "body": "Need this level of visibility/ui for event runs [https://content.trigger.dev/agent-parallelization.mp4](https://content.trigger.dev/agent-parallelization.mp4)", "createdAt": "2025-09-02T21:30:19Z", "closedAt": null, "state": "OPEN", "commentCount": 0 }, { "id": "I_kwDOMT5cIs7JNL6H", "title": "Matrix Platform Integration", "author": "objp2", "number": 5862, "repository": "elizaos/eliza", "body": "**Is your feature request related to a problem? Please describe.**\n\nWould be nice to have matrix (matrix.org) platform integration\n\n**Describe the solution you'd like**\n\nBasically just the Discord/Telegram plugin but using https://www.npmjs.com/package/matrix-bot-sdk with a Matrix bot account. Would need to be able to set up homeserver and bot token (there are instructions to get the bot token [here](https://turt2live.github.io/matrix-bot-sdk/tutorial-bot.html)) \n\n**Describe alternatives you've considered**\n\nI've looked at using Discord and the Discord to Matrix bridge, but I use Matrix for privacy, and would like everything to stay completely local. Matrix bot would support end to end encryption too.\n", "createdAt": "2025-09-02T11:47:20Z", "closedAt": null, "state": "OPEN", "commentCount": 0 } ], "topPRs": [ { "id": "PR_kwDOMT5cIs6meEtU", "title": "refactor: centralize business logic in server package", "author": "standujar", "number": 5864, "body": "# Relates to\r\n\r\n #5860 Refactor Eliza CLI\r\n \r\n # Risks \r\n \r\n **Low to Medium** \r\n - **Low**: All existing functionality maintained with backward compatibility \r\n - **Medium**: Large architectural change affecting core components, thoroughly tested \r\n \r\n # Background \r\n \r\n ## What does this PR do? \r\n \r\n This PR refactors the ElizaOS architecture by moving all business logic from the CLI package to the server package. The CLI becomes a thin orchestration layer that delegates to the server package, eliminating code duplication and creating a cleaner separation of concerns. \r\n \r\n **Key changes:** \r\n - Moved 870+ lines of business logic from CLI to server package \r\n - Created new `ElizaOS` orchestration class and managers (Agent, Plugin, Config) in server package \r\n - Simplified CLI to ~170 lines of pure delegation code \r\n - Removed 1,612 lines of redundant code while adding 1,211 lines of well-organized managers \r\n - Maintained 100% backward compatibility for all existing use cases \r\n \r\n **Files deleted from CLI:** \r\n - `commands/start/actions/agent-start.ts` (134 lines) \r\n - `commands/start/actions/server-start.ts` (118 lines) \r\n - `commands/start/utils/config-utils.ts` (73 lines) \r\n - `commands/start/utils/dependency-resolver.ts` (56 lines) \r\n - `commands/start/utils/loader.ts` (120 lines) \r\n - `commands/start/utils/plugin-utils.ts` (99 lines) \r\n \r\n **New files in server:** \r\n - `orchestration/ElizaOS.ts` - Main orchestration (166 lines) \r\n - `managers/AgentManager.ts` - Agent lifecycle (171 lines) \r\n - `managers/PluginLoader.ts` - Plugin management (140 lines) \r\n - `managers/ConfigManager.ts` - Config handling (123 lines) \r\n - `characters/default.ts` - Default Eliza character (271 lines) \r\n \r\n ## What kind of change is this? \r\n \r\n **Improvements** (misc. changes to existing features) - Major architectural refactoring without breaking changes \r\n \r\n # Documentation changes needed? \r\n \r\n My changes do not require a change to the project documentation. \r\n - The public API remains the same \r\n - All commands work identically \r\n - Internal architecture changes only \r\n \r\n # Testing \r\n \r\n ## Where should a reviewer start? \r\n \r\n 1. Review the new architecture in `packages/server/src/`: \r\n - `orchestration/ElizaOS.ts` - Main orchestration class \r\n - `managers/AgentManager.ts` - Agent lifecycle management \r\n - `managers/PluginLoader.ts` - Plugin loading and dependency resolution \r\n - `managers/ConfigManager.ts` - Configuration management \r\n \r\n 2. Check the simplified CLI in `packages/cli/src/commands/start/index.ts` \r\n \r\n ## Detailed testing steps \r\n \r\n ```bash \r\n # Test 1: CLI with character files (standalone mode) \r\n cd eliza \r\n bun run build \r\n bunx elizaos start --character characters/cartman.json \r\n # Verify: Agent starts successfully \r\n \r\n # Test 2: CLI within a project \r\n bunx elizaos create test-project --yes \r\n cd test-project \r\n bunx elizaos start \r\n # Verify: Project agents load and start \r\n \r\n # Test 3: Test command still works \r\n bunx elizaos test \r\n # Verify: Tests run successfully \r\n \r\n # Test 5: Build and test \r\n bun run build \r\n bun test \r\n # Verify: All tests passing test still passing \r\n ``` \r\n \r\n **Results:** \r\n - ✅ Created and tested a new project outside monorepo \r\n - ✅ Verified CLI works with --character flag \r\n - ✅ Confirmed projects created with `elizaos create` work correctly \r\n - ✅ All test and scenario commands functioning \r\n - ✅ Added comprehensive unit tests for new managers\"\n\n\n\n## Summary by CodeRabbit\n\n- New Features\n - Introduced unified server orchestration via ElizaOS, enabling simpler startup and agent management.\n - Added a server-provided default character with environment-aware plugin loading.\n - Ensured Ollama is always available as a fallback plugin.\n - Added dotenv support for loading .env at startup.\n- Refactor\n - CLI start flow now delegates to the server for bootstrap, agent lifecycle, and character loading.\n - Plugin parsing updated to functional APIs; centralized plugin loading and dependency resolution.\n- Chores\n - Updated CLI dependencies, including adding the OpenAI plugin.\n- Tests\n - Significant test suite updates aligning with the new orchestration and loaders.\n\n", "repository": "elizaos/eliza", "createdAt": "2025-09-02T14:28:47Z", "mergedAt": null, "additions": 2199, "deletions": 1811 }, { "id": "PR_kwDOMT5cIs6mf7xp", "title": "feat: Show action called and result in chat UI", "author": "tcm390", "number": 5865, "body": "related: https://github.com/elizaOS/eliza/issues/5831\r\n\r\nresult:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/632831d2-819d-4ba6-96e1-57206c08b6fc\r\n\r\n\r\n\r\n# Real-time Action Execution UI with Enhanced Tool Visualization\r\n\r\n## 🎯 Overview\r\n\r\nThis PR introduces a comprehensive **Real-time Action Execution UI System** that provides transparency and visibility into agent action execution. Users can now see actions as they happen, with detailed input/output data, status tracking, and error handling - all updated in real-time.\r\n\r\n## ✨ Features\r\n\r\n### 🔧 Interactive Tool Component\r\n- **Collapsible Tool Cards**: Each action is displayed as an expandable card showing execution details\r\n- **Real-time Status Updates**: Visual indicators for Processing → Ready → Completed → Error states\r\n- **Input/Output Display**: Formatted view of action parameters and results\r\n- **Error Handling**: Clear error messages and stack traces when actions fail\r\n\r\n### 📡 Live Action Tracking\r\n- **WebSocket Integration**: Real-time updates as actions progress through their lifecycle\r\n- **Event-Driven Architecture**: Comprehensive event system for action start/completion\r\n- **Status Broadcasting**: All connected clients receive live action status updates\r\n\r\n### 💾 Enhanced Data Persistence\r\n- **Action Message Storage**: Dedicated storage for action execution data\r\n- **Message Updates**: Ability to update existing messages with new action results\r\n- **Lifecycle Tracking**: Complete audit trail of action execution from start to finish\r\n\r\n## 🏗️ Technical Implementation\r\n\r\n### Frontend Changes\r\n\r\n#### New Components\r\n- **`actionTool.tsx`**: Core tool visualization component with:\r\n - Collapsible interface with state-based styling\r\n - Input/output data formatting and display\r\n - Error handling and status indicators\r\n - Accessibility features and keyboard navigation\r\n\r\n#### Enhanced Chat Interface\r\n- **Action Message Detection**: Automatically identifies action messages and renders them with tool UI\r\n- **Data Transformation**: Converts action messages to tool format with proper state mapping\r\n- **Seamless Integration**: Tool cards integrate naturally into the chat flow\r\n\r\n### Backend Changes\r\n\r\n#### Runtime Enhancements\r\n- **Action Lifecycle Events**: Enhanced `ACTION_STARTED` and `ACTION_COMPLETED` events with detailed payloads\r\n- **Callback System**: Added storage callback mechanism to capture action responses\r\n- **Event Emission**: Comprehensive event emission at action start and completion\r\n\r\n#### Database Layer\r\n- **New Methods**: \r\n - `getMessageById()`: Retrieve specific messages by ID\r\n - `updateMessage()`: Update existing messages with new data\r\n- **Message ID Handling**: Support for pre-defined message IDs in action tracking\r\n\r\n#### API Endpoints\r\n- **`POST /api/messaging/action`**: Create new action messages\r\n- **`PATCH /api/messaging/action/:id`**: Update existing action messages\r\n- **Enhanced Validation**: Comprehensive input validation and error handling\r\n\r\n#### Message Bus Service\r\n- **`notifyActionStart()`**: Broadcasts action initiation to clients\r\n- **`notifyActionUpdate()`**: Broadcasts action completion/updates to clients\r\n- **Real-time Sync**: Ensures all clients stay synchronized with action states\r\n\r\n## 🔄 User Flow\r\n\r\n```mermaid\r\nsequenceDiagram\r\n participant U as User\r\n participant C as Client UI\r\n participant S as Server\r\n participant R as Runtime\r\n participant A as Agent Action\r\n \r\n U->>C: Sends message\r\n C->>S: HTTP request\r\n S->>R: Process message\r\n R->>A: Execute action\r\n R->>S: ACTION_STARTED event\r\n S->>C: WebSocket: action started\r\n C->>C: Show \"Processing\" tool card\r\n A->>R: Action completes\r\n R->>S: ACTION_COMPLETED event\r\n S->>C: WebSocket: action completed\r\n C->>C: Update tool card to \"Completed\"\r\n C->>U: Show final results\r\n```\r\n\r\n## 📋 Code Changes Summary\r\n\r\n### Files Modified\r\n- `packages/client/src/components/chat.tsx` - Enhanced chat interface with action detection\r\n- `packages/client/src/hooks/use-socket-chat.ts` - Added rawMessage handling\r\n- `packages/client/src/lib/api-type-mappers.ts` - Enhanced message mapping with action data\r\n- `packages/core/src/runtime.ts` - Enhanced action lifecycle with event emission\r\n- `packages/core/src/types/events.ts` - Updated action event payload structure\r\n- `packages/plugin-bootstrap/src/index.ts` - Enhanced event handlers for action tracking\r\n- `packages/plugin-sql/src/base.ts` - Added message CRUD operations\r\n- `packages/server/src/index.ts` - Added message update method\r\n- `packages/server/src/api/messaging/core.ts` - New action endpoints\r\n- `packages/server/src/services/message.ts` - Enhanced message bus with action notifications\r\n\r\n### Files Added\r\n- `packages/client/src/components/actionTool.tsx` - New tool visualization component\r\n\r\n## 🧪 Testing\r\n\r\n### Manual Testing Scenarios\r\n1. **Action Execution**: Send a message that triggers an action and verify:\r\n - Tool card appears with \"Processing\" state\r\n - Updates to \"Completed\" when action finishes\r\n - Shows correct input/output data\r\n \r\n2. **Error Handling**: Trigger an action that fails and verify:\r\n - Tool card shows \"Error\" state\r\n - Error message is displayed clearly\r\n - No UI crashes or broken states\r\n\r\n3. **Multiple Actions**: Test scenarios with multiple actions and verify:\r\n - Each action gets its own tool card\r\n - States update independently\r\n - No race conditions or state conflicts\r\n\r\n### Integration Testing\r\n- WebSocket connection stability during action execution\r\n- Database consistency for action message storage\r\n- Event system reliability under load\r\n\r\n## 🔍 Screenshots\r\n\r\n### Action Processing State\r\n```\r\n┌─────────────────────────────────────┐\r\n│ 🔄 SEND_MESSAGE Processing │\r\n│ ▼ Show Details │\r\n└─────────────────────────────────────┘\r\n```\r\n\r\n### Action Completed State\r\n```\r\n┌─────────────────────────────────────┐\r\n│ ✅ SEND_MESSAGE Completed │\r\n│ ▼ Input: │\r\n│ action: \"SEND_MESSAGE\" │\r\n│ text: \"Hello world\" │\r\n│ │\r\n│ ▼ Output: │\r\n│ result: \"Message sent successfully\" │\r\n│ messageId: \"msg_123\" │\r\n└─────────────────────────────────────┘\r\n```\r\n\r\n## 🚨 Breaking Changes\r\n\r\n**None** - This is a purely additive feature that enhances existing functionality without breaking current behavior.\r\n\r\n## 🎯 Benefits\r\n\r\n### For Users\r\n- **Transparency**: Clear visibility into what the agent is doing\r\n- **Feedback**: Immediate indication of action progress and completion\r\n- **Debugging**: Easy access to action inputs, outputs, and errors\r\n\r\n### For Developers\r\n- **Debugging**: Comprehensive action execution logging and visualization\r\n- **Monitoring**: Real-time insight into agent behavior and performance\r\n- **Development**: Enhanced development experience with detailed action tracking\r\n\r\n### For the Platform\r\n- **User Experience**: Significantly improved UX with real-time feedback\r\n- **Reliability**: Better error handling and user communication\r\n- **Extensibility**: Foundation for future action-related features\r\n\r\n## 🔮 Future Enhancements\r\n\r\nThis foundation enables future features like:\r\n- Action execution analytics and metrics\r\n- Custom action UI components for specific tools\r\n- Action replay and debugging tools\r\n- Performance monitoring and optimization insights\r\n\r\n## ✅ Checklist\r\n\r\n- [x] Frontend tool visualization component implemented\r\n- [x] Backend action lifecycle tracking added\r\n- [x] Database layer enhanced with message CRUD operations\r\n- [x] API endpoints for action management created\r\n- [x] WebSocket integration for real-time updates\r\n- [x] Event system enhanced for action tracking\r\n- [x] Error handling implemented throughout the stack\r\n- [x] Manual testing completed\r\n- [x] Code follows ElizaOS architectural patterns\r\n- [x] No breaking changes introduced\r\n\r\n## 🚀 Ready for Review\r\n\r\nThis PR is ready for review and testing. The implementation follows ElizaOS architectural principles, maintains backward compatibility, and provides a solid foundation for enhanced agent interaction visibility.", "repository": "elizaos/eliza", "createdAt": "2025-09-02T17:02:38Z", "mergedAt": "2025-09-02T21:07:19Z", "additions": 796, "deletions": 68 }, { "id": "PR_kwDOMT5cIs6mg2y3", "title": "feat: Add Sentry Node telemetry support", "author": "jonathanprozzi", "number": 5867, "body": "# Overview\r\n\r\nThis adds a Sentry Node implementation to support using Sentry with AI SDK's `experimental_telemetry` option. This also adds a guard when Sentry is being imported in the `client` package. A future PR can include a full client/browser split as well as the Node. We've used this modification in our agent to receive traces from both the `plugin-openai` and the `plugin-anthropic` in Sentry.\r\n\r\n# Risks\r\n\r\nLow. This improves the existing broken Sentry implementation with a full Node.js integration to support `experimentalTelemetry` options in the AI SDK. Changes are contained to the core package's Sentry module, and adds in instrumental that was previously limited to a Sentry browser package used within the server's node context.\r\n\r\n# Background\r\n\r\n## What does this PR do?\r\n\r\nThis PR replaces the Sentry implementation with a production-ready Node.js integration featuring AI telemetry support. This has been tested and used on our fork to provide Sentry traces from AI SDK interactions (with the OpenAI and Anthropic plugins).\r\n\r\n**Key improvements:**\r\n - Fixes incomplete implementation: Replaces `@sentry/browser` with\r\n `@sentry/node` SDK to support telemetry and full tracing\r\n - Adds AI telemetry: Integrates Vercel AI SDK telemetry for monitoring LLM\r\n interactions\r\n - Enables plugin ecosystem: Provides telemetry infrastructure needed by\r\n `plugin-openai` and `plugin-anthropic`\r\n - Smart configuration: Configurable trace filtering (AI-only vs all traces)\r\n - Production ready: Comprehensive error handling, logging, and documentation\r\n\r\n **Technical features:**\r\n - Automatic AI SDK call tracing (generateText, streamText, etc.)\r\n - Input/output recording for debugging AI interactions\r\n - Performance monitoring for AI calls (duration, success rates)\r\n - Environment-aware conditional loading (prevents browser bundling issues)\r\n - Comprehensive environment variable configuration\r\n\r\n## What kind of change is this?\r\n\r\nFeatures (non-breaking change which adds functionality)\r\n\r\n# Documentation changes needed?\r\n\r\nMy changes require a change to the project documentation.\r\n ✅ I have updated the documentation accordingly.\r\n\r\n**Documentation updates made:**\r\n - `README.md`: Added comprehensive \"Sentry Monitoring & AI Telemetry\" section\r\n with usage examples\r\n - .env.example: Added all Sentry environment variables with descriptions\r\n - Code comments: Extensive inline documentation explaining implementation\r\n decisions\r\n\r\n# Testing\r\n\r\n- Tested by building locally and creating a new Eliza test project: https://github.com/jonathanprozzi/eliza-sentry-example that is ready for testing once the configuration (`SENTRY_DSN` specifically) is provided and is set up to use a local path for the `core` package for testing.\r\n- Tested all configuration options and ensured that traces came through in Sentry\r\n- Ran in both this project and in a branch of our fully functioning agent and received Sentry traces for AI SDK interactions\r\n- Builds locally when using `bun run build`\r\n\r\n## Where should a reviewer start?\r\n\r\n 1. Review the main implementation: `packages/core/src/sentry/instrument.ts` -\r\n Core Sentry integration with AI telemetry\r\n 2. Check dependency change: `packages/core/package.json` - Verify `@sentry/node`\r\n replaces browser SDK\r\n 3. Verify exports: `packages/core/src/index.ts` - Sentry utilities properly\r\n exported\r\n 4. Review documentation: `README.md` and `.env.example` - Contains usage configuration\r\n documentation\r\n\r\n## Detailed testing steps\r\n\r\n**Build verification:**\r\n- Run `bun run build` from project root - should complete without errors\r\n- Verify client package builds without Node.js dependency issues\r\n- Check TypeScript compilation succeeds\r\n\r\n**Runtime verification:**\r\n- Set `SENTRY_DSN=test_dsn` and run `elizaos start`\r\n- Verify initialization logs appear:\r\n```\r\n [SENTRY] Initializing with DSN: test_dsn...\r\n [SENTRY] Trace filtering: AI-only traces + all errors\r\n [SENTRY] Node.js initialized successfully\r\n```\r\n\r\n **AI telemetry testing:**\r\n - Set `SENTRY_DSN=real_dsn` with actual Sentry project\r\n - Set `OPENAI_EXPERIMENTAL_TELEMETRY=true` (if using OpenAI)\r\n - Start agent and have conversation\r\n - Check Sentry Performance/traces tab for `ai.generateText traces`\r\n\r\n **Configuration testing:**\r\n - Test `SENTRY_TRACE_FILTER=false` for all traces vs default AI-only\r\n - Verify `SENTRY_LOGGING=false` disables Sentry entirely\r\n - Confirm environment variables work as documented\r\n\r\n **Error capture verification:**\r\n - Existing error capture via `logger.ts` should continue working\r\n - Verify exceptions appear in Sentry Issues tab\r\n\r\n## Discord username\r\n\r\n`jpbuilds`\r\n", "repository": "elizaos/eliza", "createdAt": "2025-09-02T18:39:59Z", "mergedAt": null, "additions": 386, "deletions": 25 }, { "id": "PR_kwDOMT5cIs6mOLva", "title": "fix: add docker files to project-starter", "author": "yungalgo", "number": 5858, "body": "this is a pr to add dockerization to project-starter. so now users can do local project development , create a docker image, and then deploy it to the cloud provider of their choice. \r\n\r\nfor example with phala, users can do it all from the cli:\r\n\r\nelizaos create --type project asdasd\r\nbuild docker image: phala docker build --image my-agents-production --tag v1.0.0\r\npush image to docker hub: phala docker push\r\nadd value for DOCKER_IMAGE to env: DOCKER_IMAGE=yourdockerhubusername/my-agents-production:v1.0.0\r\nthen deploy to cloud: phala cvms create --name my-agents-production --compose ./docker-compose.yaml --env-file ./.env\r\n\r\nthis should work also for any other cloud platform seamlessly.\r\n\r\nused DOCKERFILE and DOCKERIGNORE as provided by @wtfsayo and added own docker-compose to match the one in project-tee-starter.", "repository": "elizaos/eliza", "createdAt": "2025-09-01T06:59:26Z", "mergedAt": "2025-09-02T08:29:37Z", "additions": 356, "deletions": 14 }, { "id": "PR_kwDOMT5cIs6miijk", "title": "feat: Embeds CLI version into build output", "author": "ChristopherTrimboli", "number": 5869, "body": "## 🐛 Fix: NPM CLI Package Runtime Path Resolution Issue\n\n### Problem\nThe published NPM package `@elizaos/cli@1.4.3-alpha.0` was failing with the following error when users tried to run `elizaos create` or `elizaos start`:\n\n```\nError: Cannot find module '/home/runner/work/eliza/eliza/packages/cli/package.json' \nfrom '/home/cjft/.bun/install/global/node_modules/@elizaos/cli/dist/index.js'\n```\n\nThis occurred because the CLI was attempting to read its own `package.json` at runtime using `import.meta.url` path resolution, which embedded the GitHub Actions build machine's absolute paths during the bundling process.\n\n### Root Cause\nThree files were attempting to read `package.json` at runtime:\n- `src/utils/user-environment.ts` - Used `import.meta.url` to resolve package.json path\n- `src/utils/display-banner.ts` - Read package.json to display version\n- `src/utils/copy-template.ts` - Used `require.resolve()` to find package.json\n\nWhen Bun bundled the code on GitHub Actions, these dynamic path resolutions were evaluated and hardcoded to `/home/runner/work/eliza/eliza/...`, making the package unusable on users' machines.\n\n### Solution: Build-Time Version Embedding\nImplemented **Option 1: Embed Version at Build Time** to eliminate runtime package.json reads entirely.\n\n### Changes Made\n\n#### 1. **Created Version Generation Script** (`src/scripts/generate-version.ts`)\n- Reads package.json at build time\n- Generates a TypeScript module (`src/version.ts`) with embedded version info\n- Exports constants: `CLI_VERSION`, `CLI_NAME`, `CLI_DESCRIPTION`\n\n#### 2. **Updated Build Process** (`build.ts`)\n- Now runs version generation before building\n- Ensures version information is compiled into the JavaScript bundle\n\n#### 3. **Refactored Runtime Code**\n- **`user-environment.ts`**: Now imports from generated version file instead of reading package.json\n- **`display-banner.ts`**: Uses embedded `CLI_VERSION` constant\n- **`copy-template.ts`**: Falls back to 'latest' if version file is unavailable\n\n#### 4. **Updated `.gitignore`**\n- Added `src/version.ts` and `src/version.js` to prevent committing generated files\n\n### Testing\n- Created `test-build.sh` script to verify the build process\n- Documented the solution in `BUILD-TIME-VERSION.md` and `BUILD-TIME-VERSION-SOLUTION.md`\n- The solution ensures the CLI works correctly regardless of where it's installed\n\n### Impact\n- ✅ Fixes the critical runtime error preventing users from using the published NPM package\n- ✅ Eliminates dependency on runtime file system operations for version info\n- ✅ Makes the package truly portable and installable via NPM/Bun\n- ✅ No breaking changes to the public API\n\n### Verification Steps\n1. Build the package locally: `cd packages/cli && bun run build`\n2. Check that `src/version.ts` is generated with correct version info\n3. Install and test the package globally\n4. Verify `elizaos create` and `elizaos start` work without path errors\n\nThis fix ensures that the CLI package published to NPM will work correctly on all users' machines, regardless of their file system structure.\nThis change also updates template creation to rely on this build-time constant, instead of resolving the package.json at runtime.\n", "repository": "elizaos/eliza", "createdAt": "2025-09-02T22:09:59Z", "mergedAt": "2025-09-02T22:43:31Z", "additions": 207, "deletions": 128 } ], "codeChanges": { "additions": 1665, "deletions": 325, "files": 38, "commitCount": 70 }, "completedItems": [ { "title": "fix: resolve build warnings and CSS syntax errors", "prNumber": 5851, "type": "bugfix", "body": "## Problem\r\nBuild was generating warnings:\r\n- CSS syntax errors from empty `:is()` selectors in webkit scrollbar styles\r\n- Missing asset reference in CLI build \r\n- Bundle size warnings\r\n\r\n## Solution\r\n- Remove dead reference to non-existen", "files": [ "packages/cli/build.ts", "packages/client/src/components/secret-panel.tsx", "packages/client/src/index.css", "packages/client/vite.config.ts", "bun.lock", "packages/client/cypress.config.cjs", "packages/client/cypress/e2e/03-spa-routing.cy.ts", "packages/client/cypress/support/component.ts", "packages/client/cypress/support/e2e.ts", "packages/client/package.json", "packages/client/scripts/test-e2e-with-server.sh", "packages/client/vite.config.cypress.ts" ] }, { "title": "fix(discord): Enable image generation in Discord channels", "prNumber": 5861, "type": "bugfix", "body": "related: https://github.com/elizaOS/eliza/issues/5809\r\n\r\nresult:\r\n\r\n\r\n\"Screenshot\r\n\r\n\r\n# F", "files": [ "packages/plugin-bootstrap/src/actions/imageGeneration.ts", "packages/plugin-bootstrap/src/index.ts" ] }, { "title": "fix: minor docker improvements project-tee-starter", "prNumber": 5859, "type": "bugfix", "body": "these are just some minor improvements to the docker-related stuff in project-tee-starter to match what's in project-starter. specifically:\r\n\r\n1. add DOCKER_IMAGE to .env.example -- it should be there as its req for docker deployments\r\n2. h", "files": [ "packages/project-tee-starter/.env.example", "packages/project-tee-starter/docker-compose.yaml" ] }, { "title": "fix: add docker files to project-starter", "prNumber": 5858, "type": "bugfix", "body": "this is a pr to add dockerization to project-starter. so now users can do local project development , create a docker image, and then deploy it to the cloud provider of their choice. \r\n\r\nfor example with phala, users can do it all from the ", "files": [ "packages/project-starter/.dockerignore", "packages/project-starter/.env.example", "packages/project-starter/Dockerfile", "packages/project-starter/docker-compose.yaml", "packages/project-tee-starter/.env.example", "packages/project-tee-starter/docker-compose.yaml" ] }, { "title": "feat: Embeds CLI version into build output", "prNumber": 5869, "type": "feature", "body": "## 🐛 Fix: NPM CLI Package Runtime Path Resolution Issue\n\n### Problem\nThe published NPM package `@elizaos/cli@1.4.3-alpha.0` was failing with the following error when users tried to run `elizaos create` or `elizaos start`:\n\n```\nError: Canno", "files": [ "bun.lock", "packages/cli/.gitignore", "packages/cli/build.ts", "packages/cli/src/scripts/generate-version.ts", "packages/cli/src/utils/copy-template.ts", "packages/cli/src/utils/display-banner.ts", "packages/cli/src/utils/user-environment.ts" ] }, { "title": "docs: fix broken path", "prNumber": 5866, "type": "bugfix", "body": "fixed broken path in readme", "files": [ "packages/project-tee-starter/README.md" ] }, { "title": "feat: Show action called and result in chat UI", "prNumber": 5865, "type": "feature", "body": "related: https://github.com/elizaOS/eliza/issues/5831\r\n\r\nresult:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/632831d2-819d-4ba6-96e1-57206c08b6fc\r\n\r\n\r\n\r\n# Real-time Action Execution UI with Enhanced Tool Visualization\r\n\r\n## 🎯 Overview\r", "files": [ "packages/client/src/components/actionTool.tsx", "packages/client/src/components/chat.tsx", "packages/client/src/hooks/use-socket-chat.ts", "packages/client/src/lib/api-type-mappers.ts", "packages/core/src/runtime.ts", "packages/core/src/types/events.ts", "packages/plugin-bootstrap/src/index.ts", "packages/plugin-sql/src/base.ts", "packages/server/src/api/messaging/core.ts", "packages/server/src/index.ts", "packages/server/src/services/message.ts" ] }, { "title": "feat: Adds alpha NPM release workflow", "prNumber": 5863, "type": "feature", "body": "# 🚀 NPM Alpha Release Workflow - Updated Configuration\r\n\r\n## Summary\r\n\r\nThis PR updates the NPM alpha release workflow to improve deployment reliability, enforce better quality control, and ensure consistent tooling throughout the CI/CD pi", "files": [ ".github/workflows/npm-alpha.yml", "package.json" ] } ], "topContributors": [ { "username": "ChristopherTrimboli", "avatarUrl": "https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4", "totalScore": 89.24823362209331, "prScore": 89.0482336220933, "issueScore": 0, "reviewScore": 0, "commentScore": 0.2, "summary": null }, { "username": "tcm390", "avatarUrl": "https://avatars.githubusercontent.com/u/60634884?u=c6c41679b8322eaa0c81f72e0b4ed95e80f0ac16&v=4", "totalScore": 63.813647534659395, "prScore": 63.813647534659395, "issueScore": 0, "reviewScore": 0, "commentScore": 0, "summary": null }, { "username": "standujar", "avatarUrl": "https://avatars.githubusercontent.com/u/16385918?u=718bdcd1585be8447bdfffb8c11ce249baa7532d&v=4", "totalScore": 52.9817738965761, "prScore": 43.5437738965761, "issueScore": 0, "reviewScore": 9, "commentScore": 0.43799999999999994, "summary": null }, { "username": "jonathanprozzi", "avatarUrl": "https://avatars.githubusercontent.com/u/9438776?u=25b5a5b22cfe26724ee1ebd869c378fc65196987&v=4", "totalScore": 37.40307004804858, "prScore": 37.06307004804858, "issueScore": 0, "reviewScore": 0, "commentScore": 0.33999999999999997, "summary": null }, { "username": "MozirDmitriy", "avatarUrl": "https://avatars.githubusercontent.com/u/193700874?v=4", "totalScore": 20.630306144334053, "prScore": 20.630306144334053, "issueScore": 0, "reviewScore": 0, "commentScore": 0, "summary": null }, { "username": "monilpat", "avatarUrl": "https://avatars.githubusercontent.com/u/15067321?v=4", "totalScore": 18.438, "prScore": 0, "issueScore": 0, "reviewScore": 18, "commentScore": 0.43799999999999994, "summary": null }, { "username": "0xbbjoker", "avatarUrl": "https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4", "totalScore": 13.971147180559946, "prScore": 13.631147180559946, "issueScore": 0, "reviewScore": 0, "commentScore": 0.33999999999999997, "summary": null }, { "username": "yungalgo", "avatarUrl": "https://avatars.githubusercontent.com/u/113615973?u=92e0f29f7e2fbb8ce46ed13c51f692ca803de02d&v=4", "totalScore": 4.5, "prScore": 0, "issueScore": 0, "reviewScore": 4.5, "commentScore": 0, "summary": null }, { "username": "objp2", "avatarUrl": "https://avatars.githubusercontent.com/u/189950592?v=4", "totalScore": 2, "prScore": 0, "issueScore": 2, "reviewScore": 0, "commentScore": 0, "summary": null }, { "username": "borisudovicic", "avatarUrl": "https://avatars.githubusercontent.com/u/31806472?u=27713fbe603baae91ef519990facbacd6c23e93d&v=4", "totalScore": 2, "prScore": 0, "issueScore": 2, "reviewScore": 0, "commentScore": 0, "summary": null }, { "username": "wtfsayo", "avatarUrl": "https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4", "totalScore": 0.2, "prScore": 0, "issueScore": 0, "reviewScore": 0, "commentScore": 0.2, "summary": null } ], "newPRs": 6, "mergedPRs": 8, "newIssues": 2, "closedIssues": 0, "activeContributors": 10 }