Making things

Setup tasks

Now

Some steps only a human can do: add an API key, run a migration, set an OAuth redirect URL, configure DNS. Iterel promotes every such step to a first-class task the moment an agent emits it.

Product guide

In a chat tool these scroll away and get lost. Iterel keeps them tracked, findable, and un-loseable.

Auto-detected and typed. When an agent's output implies a human-only step, Iterel spawns a setup task instead of leaving prose.
Impossible to miss. Setup tasks surface as a persistent warning banner in the agenda ("2 setup steps blocking preview") and a status dot on the affected artifact.
One click to resolve. Each carries concrete steps and, where possible, an affordance: open the env-var editor, run the migration, open the connected service, or copy the exact command.
Blocking is explicit. A setup task can hold a dependent task at needs-input and keep a preview un-runnable until satisfied — a visible dependency, not a silent runtime failure.