No reviews yetBe the first to leave a review for Clor
Maker
📌
Hey Product Hunt!
Jeff here, co-founder of Clor
Clor is a tool for managing your claws, which are async agents that use your Claude or Codex subscription to automate tasks. It lets you create, modify, and start custom automations directly from your agent with the /claw skill, then check on them any time from the macOS menu bar app. Clor also includes a plugin for Claude and Codex with skills (backed by the Clor CLI) that make your agent more capable, deterministic, and token efficient.
We built Clor because we realized we were getting really productive using Claude and Codex interactively, but were missing a huge opportunity to use them as async agents to automate tasks and become way more productive.
Claude and Codex each have their own proprietary scheduling features, but we wanted something that ran across all of our agents using our existing subscriptions. We also wanted things to run remotely on our Mac minis and cloud VMs.
One of the things I've learned is that the most exciting claws are the custom ones people create to solve problems in their own lives. You don't need to know how to code to create one. Claude or Codex can build it with the Clor CLI and test it automatically.
It's as simple as using the /claw skill in Claude or Codex:
/claw automatically update my docs when I push changes to github
/claw every week check pricing changes for my competitors
/claw create a coding loop to debug github issue #381
/claw check my spam folder for legit emails once a day
/claw your idea here!
Happy to chat or answer questions, AMA!
-Jeff
Report
@jeff_clor Congrats on the launch! 🎉 Interesting idea — especially the async agent layer on top of Claude/Codex. How do you handle task coordination when multiple “claws” are running at the same time?
A claw can have its "concurrency" setting configured, which determines whether only one instance of the claw can run at a time or whether multiple instances can run simultaneously.
Your computers, which run your claws, also have a setting that determines how many claws they'll run at the same time. The default is 10.
@jeff_clor Congrats on the launch! 🎉 Interesting idea — especially the async agent layer on top of Claude/Codex. How do you handle task coordination when multiple “claws” are running at the same time?
@jeff_clor @nicole_hynek Hi Nicole. Thanks for the question.
A claw can have its "concurrency" setting configured, which determines whether only one instance of the claw can run at a time or whether multiple instances can run simultaneously.
Your computers, which run your claws, also have a setting that determines how many claws they'll run at the same time. The default is 10.