No server to keep alive
Triggers, scheduling and run history are managed.
Most agents that run on a server are doing the same job on a schedule: check something, decide a little, write somewhere. Hosting that agent means a server to patch, a process to keep alive and a model call every run. Whenever hosts the job instead, as a workflow your coding agent writes and deploys.
Three steps, and no server at the end of them.
What it watches, what it decides, where it writes.
It follows whenever.dev/skill.md and saves a draft over MCP.
Credentials in Setup, one manual run, then publish.
And what you still own.
The pieces an agent needs to run unattended: triggers, credentials, integrations, a runtime and a record of each run. Whenever provides those for workflows.
Not if the job can be a workflow: Whenever triggers it on a schedule or webhook without a server of yours.
Yes, in steps that ask for a model; those vary and use AI-spend allowance.
Sources reviewed October 16, 2026.
Ask your coding agent to deploy it as a workflow.