Architecture
ChemAgent uses a layered architecture so model choice, project context, durable knowledge, executable capabilities, and user interfaces can evolve without collapsing into one uncontrolled prompt.
System layers
Configured providers supply reasoning, generation, vision, and tool-calling capability.
Planning, context management, mode rules, cancellation, and execution state shape each task.
Memory, project knowledge, files, and source retrieval provide durable and inspectable context.
Tools, Skills, MCP integrations, optimization modules, and simulator access perform bounded work.
Interfaces and channels
- ✓Web and desktop
Provide conversation, configuration, knowledge, memory, tasks, logs, and operational controls.
- ✓Messaging channels
Carry the same agent into approved enterprise and collaboration surfaces.
- ✓CLI
Provides system lifecycle and session-level commands without duplicating the agent core.
Control model
A mode defines the intended capability family, a workspace defines the project boundary, and deployment policy defines which integrations can operate.