SYS.ABOUT / FREQUENCY / v2.1

Agent orchestration that runs your workflows without you.

Your repo already has patterns worth automating. Frequency analyses your codebase, generates the workflow config and scripts, and runs them safely across parallel pipelines with quality controls, failure handling, and clear visibility.

We proved the system by shipping 30 production apps at Cashew Crate. Agents autonomously handled ideation, validation, implementation, review, deployment, marketing, and bug fixes across 10 parallel pipelines coordinating with each other. We intervened minimally throughout the entire process.

Generate workflows

Frequency analyses your codebase and generates workflow config as YAML state machines with explicit states, transitions, and dependency checks. Stored in your repo. State backed by repo-local JSON files. Inspect everything with git log.

Run reliably

Automatic retries for transient failures. Permanent failures isolated for manual review. Git worktree isolation prevents merge conflicts. Four levels of concurrency control keep parallel agents from corrupting each other's work.

Coordinate pipelines

Multiple workflows coordinate automatically through state predicates and shared resource locks. Marketing waits for deploy. Bug fixes feed back through build. All configured automatically.

How it works

Frequency analyses your codebase, generates workflow config as YAML state machines, and runs them. Each workflow has states, transitions, and steps. A step can be an agent call, a shell command, a git operation, or a noop. The runtime polls for subjects, advances them through states, handles retries, and dead-letters permanent failures.

  • Auto-generated config: Frequency generates YAML workflows from your codebase, stored in your repo.
  • File-backed state: repo-local JSON, fully portable.
  • Cross-pipeline coordination: state predicates and shared resource locks.
  • Concurrency control: global max workers, per-step limits, WIP limits, named resource locks.
  • Agent-agnostic: works with Claude Code, Codex, Cursor, or any CLI tool.
  • Git worktree isolation: agents work in isolated branches, merge back only on success.

Why we built this

Many teams can get a good single run from an agent. The hard part is keeping quality and reliability across repeated runs without considerable human intervention. Multi-step workflows break on sequencing, dependency control, and recovery paths when execution scales.

We built Frequency to solve that in our own stack first, with Cashew Crate as the proving ground. Most agent tools help you run agents faster or in parallel. Frequency sits one level up: each agent call is a step inside a larger workflow, and multiple workflows coordinate with each other automatically.

Who Frequency is for

Anyone with a codebase that has patterns worth automating. Frequency handles the workflow generation, orchestration, and reliability so you can focus on what matters.

  • Engineering teams who want agents running their workflows autonomously.
  • Founders who want to move from one-off prompting to a repeatable operating model.
  • Teams scaling with agents who need to go from one good run to reliable daily operation at scale.

Get early access

We're opening Frequency to design partners. If you want agents building and running your workflows autonomously, safely and at scale, we'd love to give you early access.

← RETURN TO TERMINAL