{
  "interval": {
    "intervalStart": "2025-06-18T00:00:00.000Z",
    "intervalEnd": "2025-06-19T00:00:00.000Z",
    "intervalType": "day"
  },
  "repository": "elizaos/eliza",
  "overview": "From 2025-06-18 to 2025-06-19, elizaos/eliza had 16 new PRs (12 merged), 6 new issues, and 17 active contributors.",
  "topIssues": [
    {
      "id": "I_kwDOMT5cIs67ev9-",
      "title": "bedrock",
      "author": "furkannabisumji",
      "number": 5117,
      "repository": "elizaos/eliza",
      "body": "how I can integrate bedrock as a llm there is no option in the cli",
      "createdAt": "2025-06-14T04:22:22Z",
      "closedAt": "2025-06-18T13:18:22Z",
      "state": "CLOSED",
      "commentCount": 3
    },
    {
      "id": "I_kwDOMT5cIs66Hl5D",
      "title": "Creating room via REST API first works but then returns empty rooms array",
      "author": "exitsimulation",
      "number": 4955,
      "repository": "elizaos/eliza",
      "body": "**Describe the bug**\n\nI am creating a room for an existing agent via the Rest API which returns a success response\n\nPOST `/api/agents/b850bc30-45f8-0041-a00a-83df46d8555d/rooms` with \n```\n{\n  \"name\": \"TestRoom\",\n  \"worldId\": \"00000000-0000-0000-0000-000000000000\",\n  \"roomId\": \"c06bb360-e84f-49ff-b43a-75a9eb6df8f3\",\n  \"enitityId\": \"b850bc30-45f8-0041-a00a-83df46d8555d\"\n}\n```\n\nResponse:\n```\n{\n    \"success\": true,\n    \"data\": {\n        \"id\": \"143da10d-b1e5-00cb-b315-a64f6062d9de\",\n        \"name\": \"TestRoom\",\n        \"agentId\": \"b850bc30-45f8-0041-a00a-83df46d8555d\",\n        \"createdAt\": 1749153906448,\n        \"source\": \"client\",\n        \"type\": \"dm\",\n        \"worldId\": \"00000000-0000-0000-0000-000000000000\",\n        \"serverId\": \"server-1749153906404\"\n    }\n}\n```\n\nNow, the strange thing is then when I call the rooms endpoint via GET\n`api/agents/b850bc30-45f8-0041-a00a-83df46d8555d/rooms`\n\nI am getting an empty array\n\n```\n{\n    \"success\": true,\n    \"data\": {\n        \"rooms\": []\n    }\n}\n```\n\nAlso the ID in the success response is not the one that I supplied in the request.\n\nIt seems like internally the room has not been created despite the success response?\n\nIs this a bug in the current version? I am on 1.0.4. Any help would be appreciated!",
      "createdAt": "2025-06-05T20:24:03Z",
      "closedAt": "2025-06-18T21:24:30Z",
      "state": "CLOSED",
      "commentCount": 2
    },
    {
      "id": "I_kwDOMT5cIs65--J8",
      "title": "Successive replies on target users",
      "author": "imanngabriel",
      "number": 4940,
      "repository": "elizaos/eliza",
      "body": "**Describe the bug**\n The replies on the target users behavior has successive replies, it provides 2 response in a row. I saw related issues with here as well. \n\n**To Reproduce**\n\nSet a target users on env and provide a post interval min and max. The reply of the agent behavior is inconsistent sometimes provide one reply per target users but there are scenario where it successive replies in a row (2 replies in a row)\n\n**Expected behavior**\n\nThere should be one reply per target users post or tweet and will not have successive replies. \n\n**Screenshots**\n\n<img width=\"589\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/dba6c082-3df1-45b6-9a71-d9f6e37ba8a0\" />\n\n<img width=\"612\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/126bc8bd-882b-426b-8465-7de2440e32d8\" />\n\n**Additional context**\n\n<!-- Add any other context about the problem here. -->\n",
      "createdAt": "2025-06-05T08:19:57Z",
      "closedAt": "2025-06-18T21:22:48Z",
      "state": "CLOSED",
      "commentCount": 1
    },
    {
      "id": "I_kwDOMT5cIs67_woD",
      "title": "feat: Add Ollama as AI provider option in create command",
      "author": "wtfsayo",
      "number": 5159,
      "repository": "elizaos/eliza",
      "body": "**Is your feature request related to a problem? Please describe.**\n\nCurrently, the `elizaos create` command only offers three AI provider options during project setup: Local AI, OpenAI, and Anthropic. However, the Ollama plugin (`@elizaos/plugin-ollama`) already exists in the registry and Ollama environment variables are included in the template, but users cannot select Ollama as an AI provider during the interactive create flow. This forces users to manually configure Ollama after project creation, which is inconsistent with the streamlined setup experience provided for other providers.\n\n**Describe the solution you'd like**\n\nAdd Ollama as a fourth AI provider option in the `elizaos create` command, alongside the existing Local AI, OpenAI, and Anthropic options. When users select Ollama, the system should:\n\n1. Guide users through Ollama-specific configuration (API endpoint, model selection)\n2. Set up the appropriate environment variables in the `.env` file\n3. Provide helpful setup guidance similar to other providers\n\n**Technical Implementation Details**\n\nThe following changes are needed in the CLI package (`packages/cli/src/commands/create/`):\n\n1. **Update AI Model Selection** (`utils/selection.ts`):\n   - Add Ollama option to `getAvailableAIModels()` function:\n   ```typescript\n   {\n     title: 'Ollama (self-hosted, free to use)',\n     value: 'ollama',\n     description: 'Use self-hosted Ollama models for complete privacy and control'\n   }\n   ```\n\n2. **Add Setup Logic** (`actions/setup.ts`):\n   - Add case for `'ollama'` in `setupAIModelConfig()` function\n   - Create `promptAndStoreOllamaConfig()` function to handle:\n     - OLLAMA_API_ENDPOINT (default: http://localhost:11434)\n     - OLLAMA_MODEL selection\n     - Optional embedding model configuration\n\n3. **Environment Variables** (already exist in `utils/get-config.ts`):\n   - `OLLAMA_API_ENDPOINT`\n   - `OLLAMA_MODEL`\n   - `USE_OLLAMA_TEXT_MODELS`\n   - `USE_OLLAMA_EMBEDDING`\n   - `OLLAMA_EMBEDDING_MODEL`\n   - `OLLAMA_SMALL_MODEL`\n   - `OLLAMA_MEDIUM_MODEL`\n   - `OLLAMA_LARGE_MODEL`\n\n**Acceptance Criteria**\n\n- [ ] Ollama appears as the fourth option in the AI provider selection menu\n- [ ] Selecting Ollama prompts for necessary configuration (API endpoint, models)\n- [ ] Environment variables are properly written to `.env` file\n- [ ] Setup provides helpful guidance about Ollama installation/setup\n- [ ] Follows the same interaction patterns as existing providers\n- [ ] Works in both interactive and non-interactive modes\n- [ ] Includes appropriate validation for Ollama endpoints\n- [ ] Tests are added/updated to cover the new functionality\n\n**Describe alternatives you've considered**\n\n1. **Manual Configuration**: Current approach requires users to manually add Ollama configuration after project creation, which is inconsistent with other providers\n2. **Documentation Only**: Simply documenting how to configure Ollama manually, but this doesn't match the user experience expectations set by other providers\n3. **Plugin-based Setup**: Handling Ollama setup through a separate plugin command, but this breaks the unified create experience\n\n**Additional context**\n\n- **Ollama Plugin Repository**: https://github.com/elizaos-plugins/plugin-ollama\n- **NPM Package**: https://www.npmjs.com/package/@elizaos/plugin-ollama\n- **Plugin Registry**: https://github.com/elizaos-plugins/registry\n- **Ollama Plugin Entry**: Already exists in `DEFAULT_REGISTRY` at line 209 in `/packages/cli/src/utils/registry/index.ts`\n\nThis enhancement would complete the AI provider ecosystem by making all officially supported providers accessible through the consistent create command interface, improving user experience and reducing setup friction for Ollama users.",
      "createdAt": "2025-06-17T16:13:06Z",
      "closedAt": "2025-06-18T17:41:53Z",
      "state": "CLOSED",
      "commentCount": 0
    },
    {
      "id": "I_kwDOMT5cIs68QEwg",
      "title": "Standardize Testing Framework: Migrate from vitest to bun:test",
      "author": "wtfsayo",
      "number": 5185,
      "repository": "elizaos/eliza",
      "body": "# Standardize Testing Framework: Migrate from vitest to bun:test\n\n## Problem Statement\n\nThe ElizaOS monorepo currently uses a mixed testing setup with both `vitest` and `bun:test`, creating inconsistency and potential maintenance overhead. Since the project already uses bun as the package manager and runtime, standardizing on `bun:test` would provide better integration and consistency across the codebase.\n\n## Current State Analysis\n\n**vitest Usage (extensive):**\n- 21+ `vitest.config.ts` files across packages\n- vitest listed as devDependency in root `package.json` and multiple package-specific `package.json` files\n- Used in: `@elizaos/core`, `@elizaos/cli`, `@elizaos/plugin-sql`, `@elizaos/server`, `@elizaos/client`, and others\n- Documentation specifically mentions \"Component tests use **Vitest**\"\n- Test scripts in packages use `vitest run`, `vitest watch`, etc.\n\n**bun:test Usage (minimal):**\n- Only 1 `bunfig.toml` file found in `packages/cli`\n- Limited configuration: just test preload setup\n- No evidence of extensive bun:test usage in test files\n\n## Proposed Solution\n\nMigrate the entire monorepo to use `bun:test` exclusively, removing vitest dependencies and configurations while maintaining all existing test functionality.\n\n## Benefits of bun:test\n\n1. **Consistency**: Single testing framework aligned with bun package manager usage\n2. **Performance**: Native bun testing typically faster than vitest\n3. **Simplicity**: Reduced dependency count and configuration complexity\n4. **Maintenance**: One less external dependency to maintain and update\n5. **Integration**: Better integration with bun's built-in development tools\n\n## Implementation Plan\n\n### Phase 1: Preparation\n- [ ] Audit all test files to identify vitest-specific APIs that need migration\n- [ ] Create bun:test configuration templates for different package types\n- [ ] Update test utilities in `@elizaos/plugin-bootstrap/__tests__/test-utils` for bun:test compatibility\n\n### Phase 2: Core Packages Migration\n- [ ] Migrate `@elizaos/core` package\n  - [ ] Replace `vitest.config.ts` with appropriate `bunfig.toml`\n  - [ ] Update test imports (`describe`, `it`, `expect`, etc.)\n  - [ ] Update package.json test scripts\n  - [ ] Verify all 9 test files work with bun:test\n- [ ] Migrate `@elizaos/plugin-bootstrap` (contains test utilities used by other packages)\n\n### Phase 3: Application Packages Migration\n- [ ] Migrate `@elizaos/cli` package\n  - [ ] Update existing `bunfig.toml` configuration\n  - [ ] Replace vitest scripts with bun:test equivalents\n  - [ ] Update `run-all-tests.sh` script\n  - [ ] Ensure compatibility with BATS tests (keep separate)\n- [ ] Migrate `@elizaos/server` package\n  - [ ] Handle both `vitest.config.ts` and `vitest.config.integration.ts`\n  - [ ] Update integration test setup\n- [ ] Migrate `@elizaos/client` package\n\n### Phase 4: Plugin Packages Migration\n- [ ] Migrate `@elizaos/plugin-sql` (complex test suite)\n- [ ] Migrate remaining plugin packages\n- [ ] Update plugin templates to use bun:test\n\n### Phase 5: Documentation & Templates\n- [ ] Update `/packages/docs/docs/core/testing.md` \n- [ ] Update plugin and project starter templates\n- [ ] Update CLI template generation to use bun:test configuration\n\n### Phase 6: Cleanup\n- [ ] Remove vitest dependencies from all package.json files\n- [ ] Remove all vitest.config.ts files\n- [ ] Update root-level test scripts and turbo.json configuration\n- [ ] Update CI/CD workflows if needed\n\n## Acceptance Criteria\n\n- [ ] All existing tests pass with bun:test\n- [ ] No vitest dependencies remain in any package.json\n- [ ] No vitest configuration files remain\n- [ ] Test coverage functionality maintained (if used)\n- [ ] CI/CD pipeline works with bun:test\n- [ ] Documentation updated to reflect bun:test usage\n- [ ] New project templates use bun:test by default\n- [ ] All test scripts use bun:test commands\n- [ ] Performance benchmarks show no regression (preferably improvement)\n\n## Migration Considerations\n\n**Potential Challenges:**\n1. **API Differences**: Some vitest-specific APIs may not have direct bun:test equivalents\n2. **Coverage Reports**: Ensure test coverage functionality is maintained\n3. **IDE Integration**: Verify IDE/editor test runners work with bun:test\n4. **CI Performance**: Monitor CI build times during transition\n5. **Complex Test Configurations**: Some packages have sophisticated vitest configurations that need careful translation\n\n**Risk Mitigation:**\n- Migrate packages incrementally to catch issues early\n- Maintain comprehensive test suite throughout migration\n- Keep detailed documentation of configuration changes\n- Test in CI environment before merging changes\n\n## Related Files\n\n**High-priority migration targets:**\n- `packages/core/vitest.config.ts` (9 test files)\n- `packages/cli/vitest.config.ts` (extensive test suite)\n- `packages/plugin-sql/vitest.config.ts` (complex integration tests)\n- `packages/server/vitest.config.ts` & `vitest.config.integration.ts`\n- `packages/docs/docs/core/testing.md` (documentation)\n\n**Configuration files to update:**\n- Root `package.json` (remove vitest devDependency)\n- Individual package `package.json` files\n- `turbo.json` (if test pipeline configuration needs updates)\n\n---\n\nThis migration will significantly simplify the testing infrastructure while maintaining all existing functionality and improving consistency across the ElizaOS monorepo.",
      "createdAt": "2025-06-18T22:23:56Z",
      "closedAt": null,
      "state": "OPEN",
      "commentCount": 0
    }
  ],
  "topPRs": [
    {
      "id": "PR_kwDOMT5cIs6akL6T",
      "title": "DRAFT feat: quickswap plugin ",
      "author": "monilpat",
      "number": 5123,
      "body": "<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\r\n\r\n# Relates to\r\n\r\n<!-- LINK TO ISSUE OR TICKET -->\r\n\r\n<!-- This risks section must be filled out before the final review and merge. -->\r\n\r\n# Risks\r\n\r\n<!--\r\nLow, medium, large. List what kind of risks and what could be affected.\r\n-->\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\n<!--\r\nBug fixes (non-breaking change which fixes an issue)\r\nImprovements (misc. changes to existing features)\r\nFeatures (non-breaking change which adds functionality)\r\nUpdates (new versions of included code)\r\n-->\r\n\r\n<!-- This \"Why\" section is most relevant if there are no linked issues explaining why. If there is a related issue, it might make sense to skip this why section. -->\r\n<!--\r\n## Why are we doing this? Any context or related work?\r\n-->\r\n\r\n# Documentation changes needed?\r\n\r\n<!--\r\nMy changes do not require a change to the project documentation.\r\nMy changes require a change to the project documentation.\r\nIf documentation change is needed: I have updated the documentation accordingly.\r\n-->\r\n\r\n<!-- Please show how you tested the PR. This will really help if the PR needs to be retested and probably help the PR get merged quicker. -->\r\n\r\n# Testing\r\n\r\n## Where should a reviewer start?\r\n\r\n## Detailed testing steps\r\n\r\n<!--\r\nNone: Automated tests are acceptable.\r\n-->\r\n\r\n<!--\r\n- As [anon/admin], go to [link]\r\n  - [do action]\r\n  - verify [result]\r\n-->\r\n\r\n<!-- If there is a UI change, please include before and after screenshots or videos. This will speed up PRs being merged. It is extra nice to annotate screenshots with arrows or boxes pointing out the differences. -->\r\n<!--\r\n## Screenshots\r\n### Before\r\n### After\r\n-->\r\n\r\n<!-- If there is anything about the deployment, please make a note. -->\r\n<!--\r\n# Deploy Notes\r\n-->\r\n\r\n<!--  Copy and paste command line output. -->\r\n<!--\r\n## Database changes\r\n-->\r\n\r\n<!--  Please specify deploy instructions if there is something more than the automated steps. -->\r\n<!--\r\n## Deployment instructions\r\n-->\r\n\r\n<!-- If you are on Discord, please join https://discord.gg/ai16z and state your Discord username here for the contributor role and join us in #development-feed -->\r\n<!--\r\n## Discord username\r\n\r\n-->\r\n",
      "repository": "elizaos/eliza",
      "createdAt": "2025-06-15T02:29:25Z",
      "mergedAt": null,
      "additions": 57824,
      "deletions": 75
    },
    {
      "id": "PR_kwDOMT5cIs6bGryt",
      "title": "Fix/summarized tweet interval issue",
      "author": "crypto-cooker",
      "number": 5177,
      "body": "This PR fixed Milli bot issue that is not posting summarized tweet in time interval that is set in .env.\r\n\r\nhttps://github.com/orgs/abstractoperators/projects/4/views/1?pane=issue&itemId=115868311&issue=abstractoperators%7Caiden%7C166",
      "repository": "elizaos/eliza",
      "createdAt": "2025-06-18T15:55:17Z",
      "mergedAt": null,
      "additions": 16855,
      "deletions": 80117
    },
    {
      "id": "PR_kwDOMT5cIs6bGi9_",
      "title": "Phase 2: Environment Variable Centralization",
      "author": "wtfsayo",
      "number": 5176,
      "body": "# Phase 2: Environment Variable Centralization\n\n## 🎯 Overview\n\nThis PR implements **Phase 2** of the project loading refactor, focusing on environment variable centralization to address scattered `dotenv.config()` calls and provide consistent environment variable access across the CLI.\n\n## 📋 **Week 1 Completed** ✅\n\n### Core Implementation\n- **EnvironmentLoader**: Centralized environment variable management in `src/utils/environment-loader.ts`\n- **Singleton Pattern**: Single instance with lazy loading\n- **Zod Validation**: Type-safe validation for 25+ environment variables\n- **Character-Scoped Variables**: Support for `CHARACTER.{id}.{key}` pattern\n- **Security Filtering**: Redacts sensitive variables in debugging output\n\n### Type-Safe API\n```typescript\nimport { env } from './utils/environment-loader';\n\nawait env.load();\nconst apiKey = env.getRequired('OPENAI_API_KEY');\nconst isDryRun = env.getBoolean('TWITTER_DRY_RUN');\nconst aliceConfig = env.getCharacterScoped('alice');\n```\n\n### Testing & Quality\n- **Unit Tests**: 8/8 passing with comprehensive coverage\n- **Integration Tests**: Real .env file scenarios\n- **Build Success**: CLI builds without errors\n- **Documentation**: Complete API docs and migration guide\n\n## 🚀 **Week 2 Plan** (Coming Next)\n\n### Incremental Migration Strategy\n1. **Server Loader Migration**: Update server/src/loader.ts environment access\n2. **CLI Project Migration**: Update src/project.ts environment variables\n3. **Deprecation Warnings**: Add warnings for direct process.env usage\n4. **Cleanup**: Remove scattered dotenv.config() calls\n5. **Testing**: End-to-end validation\n\n## 🎯 **Benefits Achieved**\n\n### Immediate Wins\n- ✅ **Centralized Environment Loading**: Single point of truth\n- ✅ **Type-Safe Access**: Prevents runtime configuration errors\n- ✅ **Character-Scoped Configuration**: Multi-agent support\n- ✅ **Security**: Sensitive variable filtering\n- ✅ **Backward Compatibility**: Falls back to process.env\n\n### Performance\n- **Faster Startup**: Single dotenv.config() call vs 12+ scattered calls\n- **Memory Efficient**: Singleton pattern prevents duplicate loading\n- **Validation Caching**: Environment validation happens once\n\n## 🛡️ **Safety Measures**\n\n### Risk Mitigation\n- **100% Backward Compatibility**: No breaking changes\n- **Incremental Adoption**: Can migrate consumers one by one\n- **Graceful Fallback**: Uses process.env when not loaded\n- **Clear Rollback Path**: Each step can be reverted independently\n\n### Quality Assurance\n- **Comprehensive Testing**: Unit, integration, and platform tests\n- **Build Verification**: CLI builds successfully\n- **Documentation**: Complete migration guide with examples\n\n## 📁 **Files Changed**\n\n### Core Implementation\n- `src/utils/environment-loader.ts` - Main EnvironmentLoader class\n- `src/utils/index.ts` - Export EnvironmentLoader\n- `docs/environment-loader.md` - Complete API documentation\n\n### Testing\n- `tests/unit/utils/environment-loader-simple.test.ts` - Unit tests\n- `tests/integration/environment-loader.integration.test.ts` - Integration tests\n\n## 🔄 **Migration Status**\n\n- [x] **Week 1**: Core EnvironmentLoader Implementation\n- [ ] **Week 2**: Incremental Migration (Next Phase)\n- [ ] **Week 3**: Cleanup & Performance Optimization\n\n## 📊 **Testing Results**\n\n```bash\n✓ EnvironmentLoader Simple Test > should import without errors\n✓ EnvironmentLoader Simple Test > should create singleton instance  \n✓ EnvironmentLoader Simple Test > should handle environment variables without loading\n✓ EnvironmentLoader Simple Test > should handle boolean conversion\n✓ EnvironmentLoader Simple Test > should handle number conversion\n✓ EnvironmentLoader Simple Test > should handle required variables\n✓ EnvironmentLoader Simple Test > should handle character-scoped variables\n✓ EnvironmentLoader Simple Test > should filter sensitive variables\n\n8 pass, 0 fail, 25 expect() calls\n```\n\n## 🎯 **Ready for Review**\n\nThis PR represents a **safe, incremental approach** to environment variable centralization that:\n\n1. **Solves the immediate problem** of scattered dotenv.config() calls\n2. **Provides immediate value** with type-safe environment access\n3. **Maintains stability** with 100% backward compatibility\n4. **Sets foundation** for future configuration management improvements\n\n**Status**: Ready for Week 2 incremental migration phase.",
      "repository": "elizaos/eliza",
      "createdAt": "2025-06-18T15:42:34Z",
      "mergedAt": null,
      "additions": 13043,
      "deletions": 0
    },
    {
      "id": "PR_kwDOMT5cIs6ZR5cO",
      "title": "Feature/polymarket plugin enhancements",
      "author": "HarshModi2005",
      "number": 4959,
      "body": "",
      "repository": "elizaos/eliza",
      "createdAt": "2025-06-05T21:14:45Z",
      "mergedAt": null,
      "additions": 10099,
      "deletions": 2942
    },
    {
      "id": "PR_kwDOMT5cIs6a-K0o",
      "title": "chore: update faq, quickstart, core docs",
      "author": "0xbbjoker",
      "number": 5164,
      "body": "## Summary\n\nUpdates core documentation files including FAQ, quickstart guide, and core documentation to improve clarity and accuracy.\n\n## Changes\n- Updated FAQ documentation with latest information  \n- Refreshed quickstart guide with current setup instructions\n- Enhanced core documentation for better developer experience\n\n## Impact\n- Improved onboarding experience for new users\n- More accurate and up-to-date documentation\n- Better alignment with current codebase and features\n\n**Files changed:** +2,503 additions, -974 deletions across documentation files",
      "repository": "elizaos/eliza",
      "createdAt": "2025-06-17T21:39:00Z",
      "mergedAt": "2025-06-18T17:19:11Z",
      "additions": 2503,
      "deletions": 974
    }
  ],
  "codeChanges": {
    "additions": 4350,
    "deletions": 1691,
    "files": 47,
    "commitCount": 57
  },
  "completedItems": [
    {
      "title": "chore: update faq, quickstart, core docs",
      "prNumber": 5164,
      "type": "other",
      "body": "## Summary\n\nUpdates core documentation files including FAQ, quickstart guide, and core documentation to improve clarity and accuracy.\n\n## Changes\n- Updated FAQ documentation with latest information  \n- Refreshed quickstart guide with curren"
    },
    {
      "title": "fix(docs): update ElizaOS documentation link to new official URL",
      "prNumber": 5162,
      "type": "bugfix",
      "body": "Replaced the outdated ElizaOS documentation link (https://elizaos.github.io/docs) with the current official documentation URL (https://eliza.how/docs/intro) in the Eliza partner page. This ensures users are directed to the latest and most a"
    },
    {
      "title": "feat: Add Ollama as AI provider option in create command",
      "prNumber": 5160,
      "type": "feature",
      "body": "## Summary\n\nAdds Ollama as the fourth AI provider option in the `elizaos create` command, alongside existing Local AI, OpenAI, and Anthropic options.\n\n## Changes Made\n\n### Core Implementation\n- **Added Ollama to AI model selection** (`packa"
    },
    {
      "title": "Minor Text Corrections and Consistency Improvements in Community Docs",
      "prNumber": 5154,
      "type": "other",
      "body": "\r\n\r\nDescription:  \r\nThis pull request updates the community documentation to correct minor typos and improve consistency in phrasing. Changes include fixing the spelling of \"successful\" and standardizing the formatting of \"uploaded\" for cla"
    },
    {
      "title": "feat: gui chat title",
      "prNumber": 5179,
      "type": "feature",
      "body": ""
    },
    {
      "title": "feat: (cli) consolidate stop command into agent stop --all",
      "prNumber": 5175,
      "type": "feature",
      "body": "## Problem\r\n\r\nThe ElizaOS CLI had two separate ways to stop agents:\r\n\r\n- `elizaos stop` - standalone command to stop all agents\r\n- `elizaos agent stop --name <name>` - stop individual agents\r\n\r\nThis created inconsistent UX where users had t"
    },
    {
      "title": "fix: global env load",
      "prNumber": 5174,
      "type": "bugfix",
      "body": "## What does this PR do?\n\nFixes global environment variable loading issue.\n\n## What kind of change is this?\n\nBug fixes (non-breaking change which fixes an issue)\n\n## Documentation changes needed?\n\nMy changes do not require a change to the p"
    },
    {
      "title": "fix: (cli) resolve plugin template dependencies and publish command issues",
      "prNumber": 5173,
      "type": "bugfix",
      "body": "# Fix Plugin Template Dependencies and Publish Command Issues\r\n\r\n## Problem\r\n\r\nUsers were encountering build failures when creating and publishing ElizaOS plugins using `elizaos create --type plugin` and `elizaos publish`. The errors manife"
    },
    {
      "title": "feat: cascade delete agent",
      "prNumber": 5171,
      "type": "feature",
      "body": "# Relates to\n\n<!-- LINK TO ISSUE OR TICKET -->\nDatabase relationship management and agent cleanup functionality\n\n# Risks\n\n**Medium** - Changes database deletion behavior which could affect data integrity and related records\n\n# Background\n\n#"
    },
    {
      "title": "refactor(into-5167): consolidate character loading logic and eliminate duplication (Phase 1)",
      "prNumber": 5169,
      "type": "refactor",
      "body": "$(cat <<'EOF'\n## Summary\n\nThis PR implements **Phase 1** of the project loading refactor outlined in issue #5168. The primary focus is eliminating the massive code duplication between CLI and server character loading logic by consolidating "
    },
    {
      "title": "feat(after-5169): implement Zod-based character validation with safe JSON parsing",
      "prNumber": 5167,
      "type": "feature",
      "body": "## Summary\n\nThis PR implements comprehensive Zod-based character validation with safe JSON parsing to address the issues outlined in #5166.\n\n## Changes Made\n\n### 🔧 Core Schema Implementation\n- **New File**: `packages/core/src/schemas/chara"
    },
    {
      "title": "fix: tweak media content",
      "prNumber": 5165,
      "type": "bugfix",
      "body": "Fix media content color contrast, text truncation, and padding adjustments"
    }
  ],
  "topContributors": [
    {
      "username": "wtfsayo",
      "avatarUrl": "https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4",
      "totalScore": 189.7859516558949,
      "prScore": 174.9459516558949,
      "issueScore": 10,
      "reviewScore": 4.5,
      "commentScore": 0.33999999999999997,
      "summary": null
    },
    {
      "username": "yungalgo",
      "avatarUrl": "https://avatars.githubusercontent.com/u/113615973?u=92e0f29f7e2fbb8ce46ed13c51f692ca803de02d&v=4",
      "totalScore": 130.93696444260246,
      "prScore": 130.59696444260246,
      "issueScore": 0,
      "reviewScore": 0,
      "commentScore": 0.33999999999999997,
      "summary": null
    },
    {
      "username": "0xbbjoker",
      "avatarUrl": "https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4",
      "totalScore": 124.9683436215014,
      "prScore": 115.6283436215014,
      "issueScore": 0,
      "reviewScore": 9,
      "commentScore": 0.33999999999999997,
      "summary": null
    },
    {
      "username": "ChristopherTrimboli",
      "avatarUrl": "https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4",
      "totalScore": 104.9817738965761,
      "prScore": 33.5437738965761,
      "issueScore": 0,
      "reviewScore": 71,
      "commentScore": 0.43799999999999994,
      "summary": null
    },
    {
      "username": "tcm390",
      "avatarUrl": "https://avatars.githubusercontent.com/u/60634884?u=c6c41679b8322eaa0c81f72e0b4ed95e80f0ac16&v=4",
      "totalScore": 62.21337828370962,
      "prScore": 57.01337828370962,
      "issueScore": 0,
      "reviewScore": 5,
      "commentScore": 0.2,
      "summary": null
    },
    {
      "username": "cursor-com",
      "avatarUrl": "https://avatars.githubusercontent.com/in/1210556?v=4",
      "totalScore": 39.6007738965761,
      "prScore": 39.6007738965761,
      "issueScore": 0,
      "reviewScore": 0,
      "commentScore": 0,
      "summary": null
    },
    {
      "username": "madjin",
      "avatarUrl": "https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4",
      "totalScore": 37.5217738965761,
      "prScore": 37.5217738965761,
      "issueScore": 0,
      "reviewScore": 0,
      "commentScore": 0,
      "summary": null
    },
    {
      "username": "crypto-cooker",
      "avatarUrl": "https://avatars.githubusercontent.com/u/16945788?u=819d567b766cb43113f89fb60ba0fac4c5137cf5&v=4",
      "totalScore": 34.2457738965761,
      "prScore": 34.2457738965761,
      "issueScore": 0,
      "reviewScore": 0,
      "commentScore": 0,
      "summary": null
    },
    {
      "username": "odilitime",
      "avatarUrl": "https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4",
      "totalScore": 4.7,
      "prScore": 0,
      "issueScore": 0,
      "reviewScore": 4.5,
      "commentScore": 0.2,
      "summary": null
    },
    {
      "username": "sicco-moonbeam",
      "avatarUrl": "https://avatars.githubusercontent.com/u/92480254?u=d0a396ee2f37b5bb3944aa58a7e75ee3a7e4cda3&v=4",
      "totalScore": 4,
      "prScore": 0,
      "issueScore": 4,
      "reviewScore": 0,
      "commentScore": 0,
      "summary": null
    },
    {
      "username": "yasir23",
      "avatarUrl": "https://avatars.githubusercontent.com/u/46179498?u=89dcf261b397bb2930cbedce61e09b8df01998e6&v=4",
      "totalScore": 2,
      "prScore": 0,
      "issueScore": 2,
      "reviewScore": 0,
      "commentScore": 0,
      "summary": null
    }
  ],
  "newPRs": 16,
  "mergedPRs": 12,
  "newIssues": 6,
  "closedIssues": 6,
  "activeContributors": 17
}