INTELLISYS / AGENT RUNTIMES
The Harness family
Compare DSH, Codex CLI, Claude CLI and pi, with Hermes Agent planned as a new runtime adapter.
THE AGENT RUNTIME LAYER
Choose the interface
and the tool that does the work.
A Harness is the agent runtime inside an employee environment. The platform manages its surroundings while retaining the official package.
Choose how people interact with AI
HARNESS EXPLORER
The differences are practical.
Compare how a runtime interacts, where its models come from and which shared capabilities it receives.
A web workspace inside your environment.
Use the original DeepSeek Harness interface through CroLink. CroGate prepares the environment and can deliver shared model connections and skills.
Explore model service paths ↗- Models
- Shared connections + personal APIs
- Skills
- Managed DSH delivery
- Network
- Depends on model and dependencies
The Harness provides the interaction; its model and tools determine the work it can perform.
Your CLI, in a managed team environment.
CroGate manages the installed version, employee container and terminal entry. The employee signs in using their own vendor account.
Explore model service paths ↗- Models
- Vendor service
- Skills
- Shared delivery not yet supported
- Network
- Vendor connectivity required
Platform access and vendor authorization are separate. Vendor login state stays in the employee’s private directories.
The Claude Code command-line tool.
Use the original Claude Code CLI through a gateway-held terminal session. CroGate manages its surroundings, while the vendor manages the employee’s model authorization.
Explore model service paths ↗- Models
- Vendor service
- Skills
- Shared delivery not yet supported
- Network
- Vendor connectivity required
“Claude CLI” is the name used in the architecture overview for the Claude Code command-line tool.
Shared model settings in a terminal workflow.
CroGate writes assigned model connections into pi’s own configuration. Employees can also add personal settings and providers.
Explore model service paths ↗- Models
- Shared connections + personal settings
- Skills
- Shared delivery not yet supported
- Network
- Depends on model and dependencies
Available client and gateway combinations depend on the delivered version and its acceptance checks.
A new runtime in the product architecture.
Hermes Agent is planned as an additional employee Harness. Its adapter will define the image, terminal entry, model connections and skill integration.
Explore the roadmap ↗- Models
- Delivery method to be defined
- Skills
- Integration to be defined
- Availability
- Planned; not in the current preview
A place in the architecture is a development direction. Runtime availability follows the delivered adapter.
CURRENT SCOPE AND PLANNED EXTENSION
One family, different integrations.
Hermes Agent joins the product architecture as a planned adapter. Claude CLI refers to the Claude Code command-line tool.
| Harness | Interaction | Shared model settings | Shared skills |
|---|---|---|---|
| DSH | Web workspace | Delivered by CroGate; personal APIs available | Managed environments supported |
| Codex CLI | Terminal | Employee vendor account; no shared settings delivered | Not yet supported |
| Claude CLI | Terminal | Employee vendor account; no shared settings delivered | Not yet supported |
| pi | Terminal | Gateway model file; personal settings available | Not yet supported |
| Hermes | Planned terminal | Adapter and delivery method to be defined | To be defined |
VERSION AND ENVIRONMENT LIFECYCLE
Select at creation.
Maintain by environment.
A shared runtime registry organizes images, launch parameters and readiness checks. Deliveries should identify the exact package and image versions.
Prepare once. Operate with a clear lifecycle.
KEEP EXPLORING
