OpenAI builds and deploys advanced AI models like GPT-4o for autonomous agents and workflows.
Cogitorium
About Cogitorium
Cogitorium is a modular workbench designed for agentic development, allowing users to define agents, select models per agent, and establish workflows with explicit permissions. The tool operates as a single Go binary with an embedded interface, supporting connections to various model providers including frontier APIs, local models like Ollama, or self-hosted setups without requiring internet access. It emphasizes deterministic workflows where the order of operations is controlled by the engine rather than the model, enabling reproducible pipelines that can be reshaped without rebuilding. The interface uses a graphical canvas where agents are nodes and edges represent permissions such as delegation, tool usage, memory access, and outward communication. Time-based triggers are included by default, with memory layers disabled by default to reduce complexity. The workbench provides visibility into agent interactions, costs, and approvals, including granular controls for approving executable code and managing credentials. Workspaces can be exported and shared, with approvals tied to specific builds to ensure traceability.
Key features
- Agent definition with per-agent model selection
- Graph-based workflow design with permission edges
- Time-based triggers for scheduled operations
- Cost tracking and attribution for each agent
- Approval workflow for executable code and credentials
- Exportable and shareable workspace configurations
- Local and remote model provider support
- Built-in OpenAPI documentation generation
Use cases
- Building reproducible AI pipelines with multiple models
- Designing agent workflows with explicit permission controls
- Running scheduled tasks with time-based triggers
Pros
- Single binary deployment with no external dependencies
- Supports multiple model providers simultaneously
- Explicit permission model for agent interactions
- Cost tracking per agent and workflow
- Open-source license (Apache-2.0) with no usage restrictions
Cons
- No compatibility policy for major versions
- Memory layer disabled by default, requiring manual activation
- No paid tier or commercial edition currently available
Frequently asked questions about Cogitorium
What is Cogitorium and what does it do?
Cogitorium is a modular workbench for agentic development that lets users define agents, select models per agent, and design workflows with explicit permissions. It operates as a single Go binary with an embedded interface and supports connections to various model providers, including frontier APIs, local models like Ollama, or self-hosted setups.
Who is Cogitorium designed for?
Cogitorium is designed for developers, teams, and organizations that need to build, manage, and audit agentic workflows with deterministic behavior and granular control over permissions and costs. It suits those who require visibility into agent interactions, approvals, and resource usage.
How does Cogitorium handle pricing and licensing?
Cogitorium is currently free to use with no paid tier, seat limits, or edition restrictions. The entire product is distributed as a single binary. The license is Apache-2.0, allowing modification, redistribution, and commercial use with attribution requirements.
Can Cogitorium work offline or with local models?
Yes, Cogitorium can operate offline and supports local models like Ollama or self-hosted setups without requiring internet access. It can also connect to frontier APIs or multiple model providers simultaneously.
What kind of workflows can be built with Cogitorium?
Cogitorium enables the creation of deterministic workflows and pipelines where the order of operations is controlled by the engine rather than the model. Workflows can be reshaped without rebuilding, and agents are represented as nodes with permissions defined by edges such as delegation, tool usage, memory access, and outward communication.
How does Cogitorium handle approvals and security?
Cogitorium provides granular controls for approving executable code, managing credentials, and tracking approvals tied to specific builds. Approvals are bound to the SHA256 of the bytes on disk, ensuring traceability and preventing silent retention of outdated approvals.