Questions
Hi, @Wendong-Fan Eigent-ai team.
I took a deep look and found some potential issues for architecture, UX, backend and infrastructure on Eigent.
- Electron single-instance lock in dev
requestSingleInstanceLock() can cause dev server to exit when a second instance starts.
- Layout visibility race
setWaitingBackend() can briefly show the install screen after content has already rendered.
- Zustand hydration
- Persisted auth may hydrate after the first render, causing temporary redirects or flicker.
- Norate limiting
- Endpoints are not rate-limited, increasing abuse and Dos risk.
- CORS configuration
- Missing or overly permissive CORS can allow unwanted origins
- Backend API keys in env
- API keys and config are set in os.environ per request.
I'm confident that they will be addressed by me.
Please assign it to me, so I can implement the improvements soon.
Thanks
Questions
Hi, @Wendong-Fan Eigent-ai team.
I took a deep look and found some potential issues for architecture, UX, backend and infrastructure on Eigent.
requestSingleInstanceLock()can cause dev server to exit when a second instance starts.setWaitingBackend()can briefly show the install screen after content has already rendered.I'm confident that they will be addressed by me.
Please assign it to me, so I can implement the improvements soon.
Thanks