Coordinate
A 36-role architecture routes work through specialized agent responsibilities instead of treating every request as a single undifferentiated prompt.
The system beneath the surface
ECLIPSE is built around 36 specialized agent roles connected through planning, memory, research and controlled tool execution. The public repository shows the architecture, development progress and engineering behind the system.
Inside the system.
Architecture, memory, tools, training pipeline, checkpoint verification, inference runtime, and evaluation system.
The first ECLIPSE model has completed training.
The architecture is designed for explicit coordination and controlled access to context and tools.
A 36-role architecture routes work through specialized agent responsibilities instead of treating every request as a single undifferentiated prompt.
Scoped memory retrieval supplies relevant context to each workflow.
Planning and reasoning components organize work before execution. The architecture is inspectable in the public repository.
Web research is approval-based. Tool execution is gated, and Python runs in an external sandbox.
Use AI chat and Website Builder in your private ECLIPSE AI workspace. Sign in to create conversations and manage projects.
Start and revisit conversations about code, debugging, architecture, and development.
Open BuilderCreate website projects, continue existing work, and use the project editor to generate and preview sites.
Open Website BuilderThe ECLIPSE token is planned as the utility layer behind the platform. It is intended to give users access to AI compute across ECLIPSE, including agents, website generation, code execution, 3D engineering tools and advanced workflows.
The more AI power available in your account, the more complex workflows ECLIPSE is intended to run.
Planned on Solana. Powered by ECLIPSE.The public repository is the most direct account of the system's implementation.