{
  "interval": {
    "intervalStart": "2025-08-31T00:00:00.000Z",
    "intervalEnd": "2025-09-01T00:00:00.000Z",
    "intervalType": "day"
  },
  "repository": "elizaos/eliza",
  "overview": "From 2025-08-31 to 2025-09-01, elizaos/eliza had 5 new PRs (2 merged), 1 new issues, and 8 active contributors.",
  "topIssues": [
    {
      "id": "I_kwDOMT5cIs7I4LpR",
      "title": "path not found",
      "author": "MagdiejamesNYC",
      "number": 5856,
      "repository": "elizaos/eliza",
      "body": "when I try to create a new project I have this error:\n\nCleaning up due to error...\n└  Failed to create Project.\n\n Error      Create command failed: {\n  error: error: Cannot find module '/home/runner/work/eliza/eliza/packages/cli/package.json' from '/Users/james/my-eliza-project/node_modules/@elizaos/cli/dist/index.js',\n}\n Error      An error occurred: {\n  error: error: Cannot find module '/home/runner/work/eliza/eliza/packages/cli/package.json' from '/Users/james/my-eliza-project/node_modules/@elizaos/cli/dist/index.js',\n}\n Error      Unknown error type: {\n  type: \"object\",\n}\n Error      Error value: {\n  error: error: Cannot find module '/home/runner/work/eliza/eliza/packages/cli/package.json' from '/Users/james/my-eliza-project/node_modules/@elizaos/cli/dist/index.js',\n}\n\nthere is not way to do a fresh install. Can you push an update to the package?",
      "createdAt": "2025-08-31T11:35:58Z",
      "closedAt": null,
      "state": "OPEN",
      "commentCount": 0
    }
  ],
  "topPRs": [
    {
      "id": "PR_kwDOMT5cIs6mJqE9",
      "title": "fix(cli): make plugin import verification non-fatal; address ubuntu/macos failures (2/n)",
      "author": "wtfsayo",
      "number": 5855,
      "body": "Context\\n- Ubuntu/macOS CLI tests were failing during plugin installation verification (e.g., @elizaos/plugin-bedrock, @elizaos/plugin-elevenlabs) due to dynamic import checks in ephemeral environments.\\n\\nChanges\\n- Do NOT bypass verification globally. Instead, treat verification failures as non-fatal: warn and proceed so tests can continue.\\n- Keep GitHub-based installs unverified (unchanged) because source repos may not be importable immediately in ephemeral contexts.\\n- No changes to user-facing commands; only affects internal install verification behavior.\\n\\nWhy\\n- This preserves correctness: we still attempt to verify and log failures.\\n- Prevents CI flakes where optional verification blocks entire suite.\\n\\nFollow-ups\\n- Windows agent CRUD path quoting will be fixed in a separate PR.\\n- If residual failures remain, we can further narrow verification for specific command contexts only during tests.",
      "repository": "elizaos/eliza",
      "createdAt": "2025-08-31T09:11:30Z",
      "mergedAt": null,
      "additions": 443,
      "deletions": 42
    },
    {
      "id": "PR_kwDOMT5cIs6mJlCT",
      "title": "fix(core): use node crypto in node build; unblock ubuntu/macos CLI tests (1/n)",
      "author": "wtfsayo",
      "number": 5854,
      "body": "Summary\\n- Split core settings into Node and browser variants.\\n- Node builds now import from `settings.node.ts` (`node:crypto`). Browser keeps `crypto-browserify`.\\n- Adjusted `index.node.ts` and `index.browser.ts` exports accordingly.\\n\\nWhy\\n- Recent Actions failures show CLI tests cannot resolve `@elizaos/server` due to a transitive missing polyfill: `crypto-browserify` referenced by `@elizaos/core/dist/node/index.node.js`.\\n- This caused server startup to fail in ephemeral test projects, leading to repeated port wait timeouts and cascading \"Command timed out\" errors on ubuntu/macos.\\n\\nImpact\\n- Node consumers use Node `crypto`; browser builds unchanged.\\n- Should allow ephemeral projects in CLI tests to resolve core without requiring browser polyfills in Node context, unblocking ubuntu/macos runs.\\n\\nFollow-ups\\n- If any residual module resolution issues remain, ensure the ephemeral test project still installs `@elizaos/server` before server start.\\n- Windows-specific path quoting issues in agent CRUD will be addressed in a separate PR.\\n\\nReferences\\n- Failed run: https://github.com/elizaOS/eliza/actions/runs/17354263640\\n- Errors: \"ResolveMessage: Cannot find package 'crypto-browserify'...\" and \"Cannot find module '@elizaos/server'...\" seen across ubuntu/macos.",
      "repository": "elizaos/eliza",
      "createdAt": "2025-08-31T08:48:04Z",
      "mergedAt": null,
      "additions": 300,
      "deletions": 2
    },
    {
      "id": "PR_kwDOMT5cIs6mJGfu",
      "title": "fix: CLI NPM Deployment Path Resolution Issue",
      "author": "ChristopherTrimboli",
      "number": 5852,
      "body": "## 🐛 Fix: NPM Deployment Path Resolution Issue\r\n\r\n### Problem\r\nWhen the CLI is published to NPM and installed globally (e.g., `bun i -g @elizaos/cli`), it fails with the error:\r\n```\r\nCannot find module '/home/runner/work/eliza/eliza/packages/cli/package.json'\r\n```\r\n\r\nThis occurs because the build process in GitHub Actions CI/CD embeds absolute paths from the build machine, which don't exist on users' machines.\r\n\r\n### Root Cause\r\nThe CLI was using **build-time path resolution** with `require.resolve('@elizaos/cli/package.json')` which gets hardcoded to the GitHub Actions runner path during the build process.\r\n\r\n### Solution\r\nChanged all path resolution to happen at **runtime** with multiple fallback strategies to handle different installation scenarios:\r\n- ✅ Global NPM/Bun installations\r\n- ✅ Local node_modules (as dependency)\r\n- ✅ Monorepo development\r\n- ✅ Various package manager locations\r\n\r\n### Changes Made\r\n\r\n#### 1. **`src/utils/copy-template.ts`**\r\n- Added `getGlobalNodeModulesPaths()` helper to detect global installation directories\r\n- Replaced `require.resolve()` with runtime path resolution\r\n- Added fallback paths for templates and package.json\r\n\r\n#### 2. **`src/utils/display-banner.ts`**\r\n- Implemented multi-strategy version detection:\r\n  1. Check monorepo context\r\n  2. Check `ELIZAOS_CLI_VERSION` env var (embedded during build)\r\n  3. Try multiple package.json locations\r\n  4. Extract from installation path as fallback\r\n- Returns `'unknown'` instead of crashing when package.json not found\r\n\r\n#### 3. **`build.ts`**\r\n- Reads version from package.json at build time\r\n- Embeds version as `process.env.ELIZAOS_CLI_VERSION`\r\n- Copies package.json to dist/ for runtime access\r\n\r\n#### 4. **`package.json`**\r\n- Added `dist/package.json` to files array for NPM package inclusion\r\n\r\n#### 5. **`src/utils/user-environment.ts`**\r\n- Updated CLI info detection with runtime fallbacks\r\n- Silent failures (no warnings) as this is expected in some environments\r\n\r\n### Testing\r\n```bash\r\n# Build and pack\r\ncd packages/cli\r\nbun run build\r\nnpm pack\r\n\r\n# Test installation\r\ncd /tmp\r\nbun i -g ./elizaos-cli-*.tgz\r\nelizaos create  # Should work without path errors\r\n```\r\n\r\n### Verification\r\n- [x] No hardcoded `/home/runner` paths in built files\r\n- [x] Works in monorepo development\r\n- [x] Works when installed globally via NPM/Bun\r\n- [x] Works as local dependency\r\n- [x] Graceful fallbacks when paths not found\r\n\r\n### Impact\r\n- Fixes #[issue-number] - CLI fails when installed from NPM\r\n- No breaking changes\r\n- Backward compatible with existing installations\r\n\r\n### Related Issues\r\nThis is a critical fix for the v1.5.2 release as it prevents users from using the CLI when installed from NPM.\r\n\r\n---\r\n\r\n**Note to reviewers:** The key insight is that all path resolution must happen at runtime, not build time, to support the various ways users might install and run the CLI.",
      "repository": "elizaos/eliza",
      "createdAt": "2025-08-31T05:58:59Z",
      "mergedAt": "2025-08-31T15:04:37Z",
      "additions": 258,
      "deletions": 95
    },
    {
      "id": "PR_kwDOMT5cIs6mJEfe",
      "title": "fix: resolve build warnings and CSS syntax errors",
      "author": "yungalgo",
      "number": 5851,
      "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-existent migration guides\r\n- Replace problematic Tailwind arbitrary properties with clean CSS\r\n- Increase bundle size threshold for large ElizaOS chunks\r\n- Disable CSS minification to avoid syntax errors\r\n\r\n## Result\r\n✅ Clean build with zero warnings\r\n✅ Better maintainable scrollbar styling\r\n✅ Faster build times\r\n\r\n**Impact:** Zero functional changes, improved developer experience",
      "repository": "elizaos/eliza",
      "createdAt": "2025-08-31T05:47:25Z",
      "mergedAt": "2025-09-02T20:54:08Z",
      "additions": 177,
      "deletions": 96
    },
    {
      "id": "PR_kwDOMT5cIs6mGult",
      "title": "fix(core): fix TypeScript declarations in npm package",
      "author": "standujar",
      "number": 5848,
      "body": "# Relates to\r\n\r\n  TypeScript declarations build optimization.\r\n\r\n  # Risks\r\n\r\n  **Low risk** - Configuration changes only, no functional code changes.\r\n\r\n  # Background\r\n\r\n  ## What does this PR do?\r\n\r\n  Optimizes the TypeScript build configuration for @elizaos/core package by:\r\n\r\n  1. **Removes unused configuration files** - Eliminates dead code\r\n  2. **Simplifies configuration hierarchy** - Direct inheritance from root config\r\n  3. **Renames files for clarity** - `tsconfig.build.json` → `tsconfig.declarations.json`\r\n  4. **Optimizes package structure** - Continues excluding src/ from npm package\r\n\r\n  ## What kind of change is this?\r\n\r\n  **Improvements** (misc. changes to existing features)\r\n\r\n  - Build system optimization\r\n  - Configuration cleanup\r\n  - Dead code removal\r\n\r\n  ## Why are we doing this?\r\n\r\n  The core package had a complex and partially unused TypeScript configuration setup:\r\n\r\n  - `tsconfig.browser.json` was not used by build.ts (dead code)\r\n  - `tsconfig.json` served only as an unnecessary intermediate layer\r\n  - `tsconfig.build.json` name was ambiguous (could be JS build vs types)\r\n  - Configuration inheritance chain was unnecessarily complex\r\n\r\n  This PR streamlines the setup to only what's actually needed while maintaining the same build output.\r\n\r\n  # Documentation changes needed?\r\n\r\n  **My changes do not require a change to the project documentation.**\r\n\r\n  The build commands and package structure remain identical from the consumer perspective.\r\n\r\n  # Testing\r\n\r\n  ## Where should a reviewer start?\r\n\r\n  1. Verify the build still works: `cd packages/core && bun run build`\r\n  2. Check that dist/ contains the same .d.ts files as before\r\n  3. Confirm package.json still excludes src/ from published files\r\n\r\n  ## Detailed testing steps\r\n\r\n  - Navigate to `packages/core/`\r\n  - Run `bun run build`\r\n  - Verify successful completion with TypeScript declarations generated\r\n  - Check `dist/` contains compiled .d.ts files (not pointer files)\r\n  - Confirm package size optimization (src/ excluded from npm package)\r\n  - Validate that conditional exports in package.json work correctly\r\n\r\n  ## Before and After\r\n\r\n  ### Before (3 config files, complex inheritance)\r\n  tsconfig.json (intermediate) → extends ../../tsconfig.json\r\n  tsconfig.browser.json (unused) → extends ./tsconfig.jsontsconfig.build.json → extends ./tsconfig.json → extends ../../tsconfig.json\r\n\r\n  ### After (1 config file, direct inheritance)\r\n  tsconfig.declarations.json → extends ../../tsconfig.json\r\n\r\n  **Results:**\r\n  - Same build output\r\n  - stop exporting /src\r\n  - Clearer configuration purpose\r\n  - No breaking changes for consumers\n\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\n\n## Summary by CodeRabbit\n\n* **Chores**\n  * Switched to compiled TypeScript declaration generation for more reliable typings.\n  * Published package now includes only compiled output, reducing install size.\n  * Simplified TypeScript configuration by relying on root settings and focused declaration entrypoints.\n  * Improved build logs and error handling during type generation.\n\n* **Refactor**\n  * Adjusted type entrypoints to reference compiled declarations without bundling source files.\n\n* **Notes**\n  * No API changes; end-user functionality remains the same.\n\n<!-- end of auto-generated comment: release notes by coderabbit.ai -->",
      "repository": "elizaos/eliza",
      "createdAt": "2025-08-30T13:00:47Z",
      "mergedAt": "2025-08-31T04:05:44Z",
      "additions": 39,
      "deletions": 966
    }
  ],
  "codeChanges": {
    "additions": 297,
    "deletions": 1061,
    "files": 11,
    "commitCount": 17
  },
  "completedItems": [
    {
      "title": "fix(core): fix TypeScript declarations in npm package",
      "prNumber": 5848,
      "type": "bugfix",
      "body": "# Relates to\r\n\r\n  TypeScript declarations build optimization.\r\n\r\n  # Risks\r\n\r\n  **Low risk** - Configuration changes only, no functional code changes.\r\n\r\n  # Background\r\n\r\n  ## What does this PR do?\r\n\r\n  Optimizes the TypeScript build confi",
      "files": [
        "bun.lock",
        "packages/core/build.ts",
        "packages/core/package.json",
        "packages/core/tsconfig.browser.json",
        "packages/core/tsconfig.declarations.json",
        "packages/core/tsconfig.json"
      ]
    },
    {
      "title": "fix: CLI NPM Deployment Path Resolution Issue",
      "prNumber": 5852,
      "type": "bugfix",
      "body": "## 🐛 Fix: NPM Deployment Path Resolution Issue\r\n\r\n### Problem\r\nWhen the CLI is published to NPM and installed globally (e.g., `bun i -g @elizaos/cli`), it fails with the error:\r\n```\r\nCannot find module '/home/runner/work/eliza/eliza/packag",
      "files": [
        "bun.lock",
        "packages/cli/build.ts",
        "packages/cli/package.json",
        "packages/cli/src/utils/copy-template.ts",
        "packages/cli/src/utils/display-banner.ts",
        "packages/cli/src/utils/user-environment.ts",
        "packages/core/build.ts",
        "packages/core/package.json"
      ]
    }
  ],
  "topContributors": [
    {
      "username": "wtfsayo",
      "avatarUrl": "https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4",
      "totalScore": 81.99444893413093,
      "prScore": 81.79444893413093,
      "issueScore": 0,
      "reviewScore": 0,
      "commentScore": 0.2,
      "summary": "wtfsayo: Focused on critical bug fixes, opening three PRs (elizaos/eliza#5855, elizaos/eliza#5854, elizaos/eliza#5853) to address issues related to plugin import verification, node crypto usage, and module resolution errors, demonstrating a primary focus on bugfix work and code stability."
    },
    {
      "username": "ChristopherTrimboli",
      "avatarUrl": "https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4",
      "totalScore": 67.1321876525351,
      "prScore": 57.132187652535094,
      "issueScore": 0,
      "reviewScore": 10,
      "commentScore": 0,
      "summary": "ChristopherTrimboli: Focused on resolving a critical bug, merging PR elizaos/eliza#5852 to fix a CLI NPM Deployment Path Resolution Issue, which involved modifying 19 files. Their work primarily centered on bug fixes and refactoring."
    },
    {
      "username": "yungalgo",
      "avatarUrl": "https://avatars.githubusercontent.com/u/113615973?u=92e0f29f7e2fbb8ce46ed13c51f692ca803de02d&v=4",
      "totalScore": 14.34499048409872,
      "prScore": 14.34499048409872,
      "issueScore": 0,
      "reviewScore": 0,
      "commentScore": 0,
      "summary": "yungalgo: Focused on code quality and maintenance, opening PR elizaos/eliza#5851 to resolve build warnings and CSS syntax errors, and contributing 4 commits with 48 additions and 21 deletions primarily in other work and refactoring across code and config files."
    },
    {
      "username": "MagdiejamesNYC",
      "avatarUrl": "https://avatars.githubusercontent.com/u/44060696?v=4",
      "totalScore": 2.2,
      "prScore": 0,
      "issueScore": 2,
      "reviewScore": 0,
      "commentScore": 0.2,
      "summary": "MagdiejamesNYC: Focused on identifying potential issues, creating one new issue in elizaos/eliza (#5856) to report a \"path not found\" error, and also provided one PR comment."
    }
  ],
  "newPRs": 5,
  "mergedPRs": 2,
  "newIssues": 1,
  "closedIssues": 0,
  "activeContributors": 8
}