Overview
A runtime represents an agent environment such as Hermes, Codex, or another installed tool. Multica can show which runtime is active and which computer it is running on. Workspaces separate major domains such as business and personal operations. Projects group related outcomes. Issues track individual units of work and their movement across statuses.
The key mechanism is the hook. A hook is an automatic trigger that fires when a defined event occurs. Unlike a natural-language reminder that the model may or may not follow, a hook is configured to run deterministically.
Two hook patterns are especially important:
- A memory hook loads or processes Honcho context when Hermes receives and completes a message.
- A project-management hook creates or updates a Multica issue whenever Hermes starts, updates, or
completes meaningful work.
With the second hook in place, Hermes acts as its own project manager. A new request can create a project or issue, progress can move the issue across the board, and completion can close it. The user can inspect the board instead of searching through multiple chat threads.