Your tools.
A little help getting started.

Prepare the human step in your automation with Claude Code or Codex. Or bring the process to us and we’ll work through it together.

Start with the tools your business already uses: Asana, Notion, Monday, Slack or something else. The kit helps you describe the work, decide who checks it and rehearse a handoff with fictional data.

Available now: a setup guide, workflow brief and local rehearsal. Live connections and staffing are agreed separately. There is no public hitl.ph task API available through this kit.

Choose your way in.

Open your coding assistant in the project you want to work on, then paste the setup prompt. It will read the guide, help prepare your brief and run the sample rehearsal if Node.js is available. Nothing is installed just by clicking a button here.

Set up with
Codex.

Give Codex a practical brief for the human step in your automation.

Read or select the prompt

Paste into Codex in the project you want to work on.

Help me prepare a human-in-the-loop workflow with hitl.ph using Codex. Read https://www.hitl.ph/setup/hitl-setup/SKILL.md first. Download that guide, workflow-brief.md and rehearse.mjs from the same folder, inspect them, and save them in .agents/skills/hitl-setup/ in this project without overwriting existing work. Follow the guide to prepare a workflow brief using my existing task tools and run the local sample-data rehearsal if Node.js is available. Ask for the missing business details you need. This is a planning kit, not a live hitl.ph connection: do not send messages, submit work, connect accounts or claim staff are assigned. Report what was actually tested and what still needs agreement.

Prefer to add it yourself? Save the setup guide, brief template and sample rehearsal together in .agents/skills/hitl-setup/.

Set up with
Claude Code.

Help Claude Code prepare the handoff in the tools your business uses.

Read or select the prompt

Paste into Claude Code in the project you want to work on.

Help me prepare a human-in-the-loop workflow with hitl.ph using Claude Code. Read https://www.hitl.ph/setup/hitl-setup/SKILL.md first. Download that guide, workflow-brief.md and rehearse.mjs from the same folder, inspect them, and save them in .claude/skills/hitl-setup/ in this project without overwriting existing work. Follow the guide to prepare a workflow brief using my existing task tools and run the local sample-data rehearsal if Node.js is available. Ask for the missing business details you need. This is a planning kit, not a live hitl.ph connection: do not send messages, submit work, connect accounts or claim staff are assigned. Report what was actually tested and what still needs agreement.

Prefer to add it yourself? Save the setup guide, brief template and sample rehearsal together in .claude/skills/hitl-setup/.

Let’s set it up together.

You bring the process. We’ll work through the people, the tools and the next step with you.

A project skill uses the existing skill features in Codex or Claude Code. The kit does not include a live connector or automatically grant access to any account.

A clear brief before a connection.

Pick one recurring job: an invoice mismatch, a customer record that needs checking, or a request outside the usual rules. The kit helps turn it into instructions a person can follow.

What triggers the handoff and what information comes with it.
Who checks it, their decision limits and who handles exceptions.
Where the answer is recorded and how the automation finds it.
What happens when information is missing, nobody replies or a message arrives twice.

You finish with a workflow brief to discuss with your IT provider and our team.

Keep the work where your team can find it.

An Asana task, Notion record or Monday item could hold the work and its decision. Slack could be where someone hears about it. We first agree which tool holds the final answer, rather than treating a notification as approval.

These are possible workflows to explore. Connections depend on your accounts, permissions and the process we agree. See the business examples for a useful first job.

Try the idea with sample data.

The included rehearsal runs on your computer with Node.js. It checks four fictional invoice events: a simulated approval, missing information, an amount requiring a manager and a repeated event.

node rehearse.mjs

No accounts are connected, no messages are sent and no staff are contacted. The report makes the difference clear: this is a local demonstration of the rules, not a test of your business software. Its duplicate tracking lasts for one run only.

Download the sample rehearsal and inspect it before running. Or ask your coding assistant to walk you through the cases.

Access follows the agreed process.

The kit needs no hitl.ph API key. For an actual connection, we agree the destination workspace, the people involved and the permissions they need. Account owners authorise access through their own tools.

Keep passwords and access tokens out of your workflow brief. A setup prompt does not sign you up for a service or authorise changes to business accounts.

Build the connection when the process is clear.

Your tool’s own automation may be enough. If custom code is needed, your IT provider can work with us on the handoff and return path. A webhook is one way systems notify each other that something has changed.

Before live work, test the actual connection with sample records: the right person sees the job, only an authorised decision resumes it, repeated events do not repeat actions, and failed deliveries can be recovered.

Earlier API and CLI examples on this site described prototypes and proposed behaviour. They are not supported setup instructions. The API availability record now publishes no callable operations.

Know what is ready.

Stage	What it means
Planning	The brief identifies the process, people and unanswered questions.
Local rehearsal	Sample rules have been exercised on your computer. No external connection is proven.
External test	An authorised connection has been tested with sample records in the agreed tools.
Live by agreement	Staffing, access, instructions, cover and the working connection have been agreed and checked.

Bring us your first workflow.

A rough brief is enough to start. Tell us where work needs a person, the tools you use and the volume you expect.

You can email us directly at ai@yoonet.io.