Skip to main content

Understanding Agents

Agents are the multi-step Companion behavior Harmony is building toward. The long-term vision is for agents to monitor signals, make decisions, and chain actions together on behalf of a workspace. Today, the Agents surface is only partially shipped.

The Marketplace includes an Agents tab where you can browse curated agent prompts, open detail pages, copy the prompt, and download the agent bundle. Harmony does not yet include a per-workspace agent registry, a one-click install flow, or a continuous monitoring runtime.

What is available today

The live part of Agents is the Marketplace experience. In Marketplace -> Agents, you can browse agent prompts published through the CMS. Each agent detail page shows the agent's description, prompt, metadata, and download action.

The standalone Agents sidebar entry is currently disabled and marked Soon. It does not navigate to an active workspace agent area. The Installed tab in the Marketplace also lists integrations only, not installed agents, because workspace-level agent installation is not available yet.

Continuous monitoring and autonomous triggers are not configurable in the UI today. To use an agent now, a workspace member must open it from the Marketplace, copy the prompt, and run it in Companion or save it as a workspace Protocol.

Agents vs Skills

A Skill is a reusable Companion prompt for a specific recurring task. A user activates the Skill, Companion follows the instructions, and the workflow runs in that interaction.

An Agent is intended to be a more autonomous, multi-step assistant. As the product matures, agents are expected to chain actions together and eventually work in the background based on configured signals or triggers.

In practice today, Marketplace Skills and Marketplace Agents are both distributed as Markdown prompts. You can copy either type into a Companion thread, or you can turn the prompt into a workspace Protocol under Settings -> Protocols so the team can reuse it from Companion. The difference will become more meaningful as Harmony ships the workspace agent registry, installation flow, and autonomous runtime.

How to use an agent today

There is no in-app Install agent action today. To use a Marketplace agent, open Marketplace -> Agents, choose an agent, and open its detail page. From there, copy the prompt into a new Companion thread. Companion will follow that prompt for the duration of the thread.

You can also download the agent bundle as a zip for sharing or offline reference. If the agent should become reusable across your workspace, copy the prompt into a new Protocol under Settings -> Protocols. See Creating custom Protocols for details.

Triggers

Automatic activation is planned but not available yet. Examples of future trigger behavior might include running an agent when sentiment drops below a threshold or when a deal stalls. The Marketplace and Protocols UI may refer to triggers as a future capability, but there is no setting today that makes an agent or Protocol run automatically.

Until triggers ship, a person must explicitly start the agent from Companion or use its prompt in a Companion thread.

Marketplace detail pages

An agent detail page at /marketplace/agents/{agentId} presents the information needed to evaluate and reuse the agent. The page includes the hero content, the agent name and description, the Markdown prompt, categories, author metadata, and a download button for the bundle.

The prompt is the most important part of the page because it is the actual text you can use in Companion. If the agent ID is unknown, the detail page shows a not found state.

What changes when Agents fully ship

When the per-workspace Agents product ships in full, the disabled sidebar entry is expected to become navigable. Harmony is also expected to add a workspace registry for active agents, an in-app install action from Marketplace detail pages, configurable triggers for autonomous activation, and Marketplace installed-state support for agents.

Until then, treat Marketplace agents as discovery and distribution. The prompt is real and usable today, while installation, monitoring, and trigger behavior are still future product surfaces.

For Marketplace behavior, see Marketplace overview. For reusable Companion prompts, see Skills overview. To turn an agent prompt into a shared workspace workflow, see Creating custom Protocols.