{ "interval": { "intervalStart": "2025-05-25T00:00:00.000Z", "intervalEnd": "2025-05-26T00:00:00.000Z", "intervalType": "day" }, "repository": "elizaos/eliza", "overview": "From 2025-05-25 to 2025-05-26, elizaos/eliza had 7 new PRs (4 merged), 3 new issues, and 10 active contributors.", "topIssues": [ { "id": "I_kwDOMT5cIs64JzeU", "title": "LOG_LEVEL not working", "author": "standujar", "number": 4772, "repository": "elizaos/eliza", "body": "**Describe the bug**\n\nThe LOG_LEVEL variable is not working anymore. I have the same log level if I se LOG_LEVEL=debug ou DEBUG or INFO or info.", "createdAt": "2025-05-25T21:14:04Z", "closedAt": "2025-05-26T07:53:38Z", "state": "CLOSED", "commentCount": 2 }, { "id": "I_kwDOMT5cIs64JPkJ", "title": "Temporary messages not removed after failed send messages stay in UI even on error", "author": "0x-Tek", "number": 4769, "repository": "elizaos/eliza", "body": "When you send a message, two messages get added to the chat immediately: one from the user and a second from the \"system\" with a loading indicator. \nBut if the API call fails (like due to no internet), both fake messages stay in the chat as if nothing went wrong. There’s no rollback, no error handling on the UI so it looks like the message was sent when it actually wasn’t.\n\nTo Reproduce:\n\n1.Open the chat page (eliza/client/src/components/chat.tsx)\n\n2.Disconnect from the internet or block the request to the send message endpoint.\n\n3.Type a message and hit Enter.\n\n4.You’ll see your message and a “loading” message instantly.\n\n5.Even though the request fails, both messages stay on screen.\n\nExpected behavior\nIf the message fails to send, the temporary messages should be removed automatically. The user should also get feedback (like a toast or error icon) to let them know it didn’t work.\n\nAdditional context\nTo fix it, I added a tempId to identify and clean up fake messages properly. Now if the message fails, those temporary entries get removed from the cache.\n\n\nIn chat.tsx, update the type:\n```\ntype ExtraContentFields = {\n user: string;\n createdAt: number;\n isLoading?: boolean;\n tempId?: string; // ✅ for cleanup\n};\n\n```\nReplace handleSendMessage with:\n```\nconst handleSendMessage = (e: React.FormEvent) => {\n e.preventDefault();\n if (!input) return;\n\n const tempId = `${Date.now()}-${Math.random()}`;\n const attachments: IAttachment[] | undefined = selectedFile\n ? [\n {\n url: URL.createObjectURL(selectedFile),\n contentType: selectedFile.type,\n title: selectedFile.name,\n },\n ]\n : undefined;\n\n const tempMessages: ContentWithUser[] = [\n {\n text: input,\n user: \"user\",\n createdAt: Date.now(),\n attachments,\n isLoading: true,\n tempId,\n },\n {\n text: input,\n user: \"system\",\n createdAt: Date.now(),\n isLoading: true,\n tempId,\n },\n ];\n\n queryClient.setQueryData(\n [\"messages\", agentId],\n (old: ContentWithUser[] = []) => [...old, ...tempMessages]\n );\n\n sendMessageMutation.mutate({\n message: input,\n selectedFile,\n tempId,\n });\n\n setSelectedFile(null);\n setInput(\"\");\n formRef.current?.reset();\n};\n```\n\nAnd update the mutation like this:\n```\nconst sendMessageMutation = useMutation({\n mutationKey: [\"send_message\", agentId],\n mutationFn: ({\n message,\n selectedFile,\n }: {\n message: string;\n selectedFile?: File | null;\n tempId: string;\n }) => apiClient.sendMessage(agentId, message, selectedFile),\n onSuccess: (newMessages: ContentWithUser[], variables) => {\n const { tempId } = variables;\n queryClient.setQueryData(\n [\"messages\", agentId],\n (old: ContentWithUser[] = []) => [\n ...old.filter((msg) => msg.tempId !== tempId),\n ...newMessages.map((msg) => ({\n ...msg,\n createdAt: Date.now(),\n })),\n ]\n );\n },\n onError: (error, variables) => {\n const { tempId } = variables;\n queryClient.setQueryData(\n [\"messages\", agentId],\n (old: ContentWithUser[] = []) =>\n old.filter((msg) => msg.tempId !== tempId)\n );\n\n toast({\n variant: \"destructive\",\n title: \"Unable to send message\",\n description: error.message,\n });\n },\n});\n```\n", "createdAt": "2025-05-25T16:53:00Z", "closedAt": null, "state": "OPEN", "commentCount": 1 }, { "id": "I_kwDOMT5cIs64JQK6", "title": "Failed Fetch-News", "author": "K1mc4n", "number": 4770, "repository": "elizaos/eliza", "body": "fetch-news\n\nThe process '/usr/bin/git' failed with exit\n\ncode 1", "createdAt": "2025-05-25T16:57:08Z", "closedAt": null, "state": "OPEN", "commentCount": 0 } ], "topPRs": [ { "id": "PR_kwDOMT5cIs6Xjeuj", "title": "feat: Add Project TEE Starter Template", "author": "HashWarlock", "number": 4774, "body": "\r\n\r\n# Relates to\r\nAdds TEE Project Starter Template for a quickstart to launch in TEE Cloud provider. For the time being, Phala Cloud is the current available option for a customizable ElizaOS deployment.\r\n\r\n\r\n\r\n\r\n# Risks\r\nLow\r\n\r\n\r\n# Background\r\n\r\n## What does this PR do?\r\nCreates a quick start to generate a TEE Agent project.\r\n## What kind of change is this?\r\nFeature\r\n\r\n\r\n\r\n\r\n\r\n# Documentation changes needed?\r\n\r\n\r\n\r\n\r\n\r\n# Testing\r\n\r\n## Where should a reviewer start?\r\nA reviewer should start with getting a Phala Cloud Account to test the CVM deployment. Get an API Key and Install the Phala Cloud CLI for deployment. Check Docs [here]()\r\n### Detailed testing steps\r\nFirst clone the repo (I have not added the CLI command, yet. This could be easier with elizaos CLI.)\r\n```bash\r\n# Make sure you are in the `project-tee-starter` folder\r\nnpm install -g phala\r\n# Set TEE_MODE=PRODUCTION\r\n# Ensure you are also running docker\r\n\r\n# Step0: Set your API Key from Phala Cloud Dashboard\r\nphala auth login\r\n\r\n# Step1: Build Docker Image\r\nphala docker build\r\n\r\n# Step2: Publish Docker Image to DockerHub\r\nphala docker push\r\n\r\n# Step3: Update docker-compose.yaml file with your published Docker image and deploy CVM\r\nphala cvms create -c docker-compose.yaml -e .env\r\n\r\n# (Optional) Step4: Check attestation\r\nphala cvms attestation\r\n\r\n# (Optional) Step5: Upgrade CVM if updated changes\r\nphala cvms upgrade -c docker-compose.yaml\r\n```\r\n\r\n\r\n\r\n\r\n\r\n\r\n## Screenshots\r\nTest deployment: https://94068a91ffa0d8f97f2fb38941ee0139f533daab-3000.dstack-prod6.phala.network/chat/f1b8ef45-dab5-095e-90a8-87a35b16966e\r\n\r\n![image](https://github.com/user-attachments/assets/f0f09aa4-14f4-4523-b013-0d7af096dd99)\r\n\r\n![image](https://github.com/user-attachments/assets/0e0e8b5d-3e4a-4cb0-a06f-bfd932c3c746)\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n", "repository": "elizaos/eliza", "createdAt": "2025-05-25T21:42:34Z", "mergedAt": "2025-05-27T07:53:37Z", "additions": 4168, "deletions": 0 }, { "id": "PR_kwDOMT5cIs6Xh8oU", "title": "feat: Migrate knowledge tab to plugin-knowledge, add graph view to memories", "author": "lalalune", "number": 4766, "body": "This PR makes some changes to enable the knowledge plugin\r\n\r\n- Some stuff could be moved out of the PR but is probably fine, like the package.json changes, and we should adopt the convention of .beta\" anyways\r\n\r\n- Removes knowledge APIs since they are in plugin-knowledge\r\n\r\n- Adds some PCA stuff to map embeddings to a 2D graph\r\n\r\n- Adds a graph view to memories and lib stuff for other views", "repository": "elizaos/eliza", "createdAt": "2025-05-25T06:57:28Z", "mergedAt": "2025-05-26T08:29:38Z", "additions": 1135, "deletions": 1236 }, { "id": "PR_kwDOMT5cIs6XjL5N", "title": "fixed: Undelegate Action", "author": "Samarthsinghal28", "number": 4771, "body": "\r\n\r\n# Relates to\r\n\r\n\r\n\r\n\r\n\r\n# Risks\r\n\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\n\r\n\r\n\r\n\r\n# Documentation changes needed?\r\n\r\n\r\n\r\n\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\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n", "repository": "elizaos/eliza", "createdAt": "2025-05-25T18:46:25Z", "mergedAt": "2025-05-25T18:58:47Z", "additions": 568, "deletions": 1046 }, { "id": "PR_kwDOMT5cIs6Xjdku", "title": "feat: describe images WIP", "author": "0xbbjoker", "number": 4773, "body": "Draft describing works only for small images. \r\n\r\nNot complete. \r\n\r\nWe would need to do cleanup for the prompt. Right now url is being added in the prompt.\r\n\r\nig we need to test this a bit and see what's best approach for image description from the client side.", "repository": "elizaos/eliza", "createdAt": "2025-05-25T21:31:21Z", "mergedAt": null, "additions": 353, "deletions": 30 }, { "id": "PR_kwDOMT5cIs6XV4vc", "title": "feat: Add graph view for memories and knowledge", "author": "lalalune", "number": 4737, "body": "## Summary\n- expose embeddings via API with `includeEmbedding` flag\n- add PCA implementation and simple force graph\n- integrate graph toggle for memory and knowledge views\n- add unit test for PCA\n\n## Testing\n- `bun test` *(fails: vi.resetAllMocks is not a function)*", "repository": "elizaos/eliza", "createdAt": "2025-05-23T07:43:24Z", "mergedAt": null, "additions": 184, "deletions": 20 } ], "codeChanges": { "additions": 570, "deletions": 1102, "files": 15, "commitCount": 13 }, "completedItems": [ { "title": "corrected path for defaultCharacter.ts", "prNumber": 4775, "type": "other", "body": "\r\n\r\n# Relates to\r\n\r\n\r\nI was just reading the README.md file and path to defaultCharacter.ts" }, { "title": "fixed: Undelegate Action", "prNumber": 4771, "type": "bugfix", "body": "\r\n\r\n# Relates to\r\n\r\n\r\n\r\n\r\n\r\n# Relates to\r\n\r\n\r\n\r\n\r\n\r\n# Relates to\r\n\r\n\r\n\r\n