Capabilities

Capabilities are the approved skills and tools your organization makes available to agents — for example a code-quality helper, a documentation assistant, or a connection to an internal knowledge source. They give agents more power within what your organization has vetted.

Built-in capability packs

Chronos ships three capability packs by default:

• Kairos — governed method skills: proven working methods the agent retrieves on demand.
• Tempo — an output and token optimizer (pack id tempo).
• Pulse — a reuse-first code-minimalism guardrail (pack id pulse).

Like every other capability, they are governed from your organization’s panel and can be enabled or disabled per session.

The Capabilities tab

Select a session and open Capabilities in the right pane. Each capability shows what it is, what it does, and whether you can turn it on or off for this session.

• Optional capabilities have a switch — turn them on or off per session as you like.
• Required capabilities show a lock — your organization mandates them, so they are always on.

Installing a capability

Some capabilities need to be installed into a session before they take effect. When you turn one on, Chronos asks you to confirm — approval is required to install, with the reason shown — before completing the install.

This is the same “no silent side effects” principle used everywhere in Chronos. Once approved, the capability is ready to use.

Why capabilities are governed

Capabilities change what an agent can do, so they are treated with care:

• Approved only — every capability comes from your organization’s vetted catalog; an agent cannot reach anything that has not been approved.
• Scoped — your organization can make a capability available everywhere, to specific teams, or to specific projects.
• Recorded — turning a capability on or off, and installing it, are all recorded.

This keeps the benefit of powerful, extensible agents while staying firmly within your organization’s rules.