Skip to main content
Helix plugs into the tools around your agents in three ways: it reads traces from wherever your agent runs, it writes approved fixes back to your agent’s source, and it connects to general-purpose services like GitHub and Slack. Cloud deployment targets are on the way.
Helix reads traces — it doesn’t store them. Your traces stay in the source you already use.

Trace Sources

Where your agent’s runs come from — local transcripts, JSONL exports, or an OpenTelemetry observability backend.

Apply Targets

Where approved fixes land — harness markdown agents or agent code, via GitHub.

General-purpose

GitHub — connect a repo, read agent code, ship fixes as PRs. Slack — drive Helix.

Cloud Deployment

Managed-agent deployment platforms — Paperclip, Mastra Cloud, Vercel EVE.

​
Local vs cloud

  • Local integrations run on your machine, no cloud account: transcripts, JSONL, and GitHub PRs against a repo you own.
  • Cloud integrations use credentials on a hosted platform: an observability backend (Langfuse, OpenObserve, SigNoz) for traces, and managed-agent deployment platforms for shipping the agent.