吴恩达开源的OpenWorker，为什么「不 Work」了？
Ranking
Overall
71
Content
80
Popularity
N/A
No observed public metrics; popularity remains neutral/archived.
Merged summary
TL;DR - OpenWorker is an open-source desktop agent backed by Andrew Ng that packages model routing, tool use, connectors, and approvals into an office automation app. Early testing shows a substantial gap between an extensible agent architecture and a dependable product for nontechnical users.
- Its local agent service can orchestrate OpenAI, Gemini, Ollama, and other models while connecting to tools such as Slack, GitHub, Jira, Notion, and Outlook.
- “Model agnostic” does not mean plug-and-play: users reported failures with OpenAI-compatible endpoints and Ollama model discovery, alongside weak handling of quota and repeated API errors.
- “Local first” still permits data to flow to cloud models, connected services, and potentially official telemetry, making explicit data-path disclosure essential.
- Approval controls may not cover every execution path, including configuration loading and background service startup; mature desktop agents need unified authorization, logging, and restrictions across all paths.
Sources (1)
吴恩达开源的OpenWorker，为什么「不 Work」了？
Public signals
N/A
TL;DR - OpenWorker is an open-source desktop agent backed by Andrew Ng that packages model routing, tool use, connectors, and approvals into an office automation app. Early testing shows a substantial gap between an extensible agent architecture and a dependable product for nontechnical users.
- Its local agent service can orchestrate OpenAI, Gemini, Ollama, and other models while connecting to tools such as Slack, GitHub, Jira, Notion, and Outlook.
- “Model agnostic” does not mean plug-and-play: users reported failures with OpenAI-compatible endpoints and Ollama model discovery, alongside weak handling of quota and repeated API errors.
- “Local first” still permits data to flow to cloud models, connected services, and potentially official telemetry, making explicit data-path disclosure essential.
- Approval controls may not cover every execution path, including configuration loading and background service startup; mature desktop agents need unified authorization, logging, and restrictions across all paths.