Hey HN. We built Frequency, AI agent orchestration that autonomously detects, defines, and runs any repeatable workflow in your repo for you, continuously and at scale.
We used it to automate our app development repo, and rapidly ship 30 production apps (and counting) at Cashew Crate (https://cashewcrate.com) from scratch, autonomously. These are real, fully functional apps with working payments, accounts, analytics, and marketing integrations. Now, all we need to do is run Frequency and we see new apps appear everyday, without any prompting or babysitting.
While we needed to intervene to set up payments for the first time due to regulatory verification, the agents handled everything else - ideation, implementation, review, deployment, and bug fixes across 10 parallel pipelines (more pipelines can be added as needed).
Frequency analyses your codebase, generates workflow config as YAML state machines, and runs them with repo-local JSON state (no database, no message queue). Pipelines coordinate through state predicates and shared resource locks. Agent calls run in git worktrees with integration gates. About 40% of our steps are agent calls, the rest are deterministic scripts. Works with any agent or CLI tool. App development was our proving ground but the runtime is workflow-agnostic.
The hardest part was cross-pipeline coordination: marketing needs to know deploy finished, bug fixes need to feed back through build. Getting this to work declaratively rather than with imperative callbacks took several iterations. Our main bottleneck now is token limits rather than the orchestration.
We're opening Frequency to design partners. If you want agents building and running your workflows autonomously, safely and at scale, sign up at http://frequency.sh.
frequencyai•1h ago
We used it to automate our app development repo, and rapidly ship 30 production apps (and counting) at Cashew Crate (https://cashewcrate.com) from scratch, autonomously. These are real, fully functional apps with working payments, accounts, analytics, and marketing integrations. Now, all we need to do is run Frequency and we see new apps appear everyday, without any prompting or babysitting.
While we needed to intervene to set up payments for the first time due to regulatory verification, the agents handled everything else - ideation, implementation, review, deployment, and bug fixes across 10 parallel pipelines (more pipelines can be added as needed).
Frequency analyses your codebase, generates workflow config as YAML state machines, and runs them with repo-local JSON state (no database, no message queue). Pipelines coordinate through state predicates and shared resource locks. Agent calls run in git worktrees with integration gates. About 40% of our steps are agent calls, the rest are deterministic scripts. Works with any agent or CLI tool. App development was our proving ground but the runtime is workflow-agnostic.
The hardest part was cross-pipeline coordination: marketing needs to know deploy finished, bug fixes need to feed back through build. Getting this to work declaratively rather than with imperative callbacks took several iterations. Our main bottleneck now is token limits rather than the orchestration.
Twitter blog post with demo video: https://x.com/FrequencyAI_HQ/status/2031399095848362032
We're opening Frequency to design partners. If you want agents building and running your workflows autonomously, safely and at scale, sign up at http://frequency.sh.
The HN url links to our writeup with architecture details, what broke, and limitations: https://www.frequency.sh/blog/introducing-frequency/
We also plan to periodically release further deep dives into the architecture and technicals as we open up the platform to everyone, so please follow our socials for further updates. Hacker News: https://news.ycombinator.com/submitted?id=frequencyai Twitter (X): https://x.com/FrequencyAI_HQ Bluesky: https://bsky.app/profile/frequency-ai.bsky.social