<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: HostNest</title>
    <description>The latest articles on DEV Community by HostNest (@hostnest).</description>
    <link>https://dev.to/hostnest</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4196807%2F37e950cb-edee-434a-9210-9024a45f4080.png</url>
      <title>DEV Community: HostNest</title>
      <link>https://dev.to/hostnest</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hostnest"/>
    <language>en</language>
    <item>
      <title>Why your AI agent's scheduled job didn't run, and how to know next time</title>
      <dc:creator>HostNest</dc:creator>
      <pubDate>Thu, 29 Oct 2026 19:34:36 +0000</pubDate>
      <link>https://dev.to/hostnest/why-your-ai-agents-scheduled-job-didnt-run-and-how-to-know-next-time-22cp</link>
      <guid>https://dev.to/hostnest/why-your-ai-agents-scheduled-job-didnt-run-and-how-to-know-next-time-22cp</guid>
      <description>&lt;p&gt;A scheduled agent job usually fails to run for one of three reasons: the machine or app it lives in was off, the run it missed was skipped rather than caught up, or the schedule itself ran out. None of them leaves an error, because nothing ran to leave one. The fix is to know where your scheduler lives, choose one that catches up, and have something tell you when a run doesn't happen.&lt;/p&gt;

&lt;p&gt;This is for anyone who schedules work for an agent, whatever the tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why didn't the job run?
&lt;/h2&gt;

&lt;p&gt;Because a schedule only fires while the thing holding it is running. People find this out the slow way:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The app was closed.&lt;/strong&gt; A two-person studio's morning briefing only ran while the app was open on a laptop: &lt;a href="https://www.reddit.com/r/smallbusiness/comments/1x9yftz/" rel="noopener noreferrer"&gt;"Between October 7 and 15 we have a briefing for three of seven weekdays"&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nothing at all.&lt;/strong&gt; &lt;a href="https://www.reddit.com/r/ClaudeAI/comments/1x6e7w0/" rel="noopener noreferrer"&gt;"a one-time scheduled task set for 3:15am just never ran. Zero runs, no error"&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nobody noticed.&lt;/strong&gt; An autonomous coding pipeline used up its 3,000 monthly GitHub Actions minutes in about three and a half days. &lt;a href="https://www.reddit.com/r/ClaudeAI/comments/1x1cltw/" rel="noopener noreferrer"&gt;"Jobs stopped, and I didn't notice for two days."&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Some people end up buying a small always-on computer just for their agent. That works, but it's worth knowing which of the causes below you're paying to fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where does your agent's scheduler actually run?
&lt;/h2&gt;

&lt;p&gt;Find out before you trust it. Most agent tools offer more than one kind of schedule, and they differ in exactly this.&lt;/p&gt;

&lt;p&gt;Claude Code's documentation lays its three out side by side. Its in-session &lt;code&gt;/loop&lt;/code&gt; needs the machine on and the session open; its Desktop tasks need the machine on but not a session; its cloud tasks need neither (&lt;a href="https://code.claude.com/docs/en/scheduled-tasks" rel="noopener noreferrer"&gt;scheduled tasks docs&lt;/a&gt;). The same page is plain about which to pick: &lt;a href="https://code.claude.com/docs/en/scheduled-tasks" rel="noopener noreferrer"&gt;"Use cloud tasks for work that should run reliably without your machine."&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hermes Agent runs scheduled agent jobs inside its gateway process: &lt;a href="https://hermes-agent.nousresearch.com/docs/user-guide/features/cron" rel="noopener noreferrer"&gt;"agent jobs execute inside the gateway"&lt;/a&gt;, so with no gateway up, those jobs are skipped and fire on the next tick after it starts.&lt;/p&gt;

&lt;p&gt;Whatever you use, answer three questions for each job:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Does it need my computer on?&lt;/li&gt;
&lt;li&gt;Does it need an app or a session open?&lt;/li&gt;
&lt;li&gt;Does it need me logged in?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Every "yes" is a way for the job to miss a run without telling you.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens to a run that was missed?
&lt;/h2&gt;

&lt;p&gt;It depends on the scheduler, and the difference matters on a laptop. Classic cron simply skips it. Apple's launchd documentation, for jobs set with &lt;code&gt;StartCalendarInterval&lt;/code&gt;, puts the contrast in one line: &lt;a href="https://keith.github.io/xcode-man-pages/launchd.plist.5.html" rel="noopener noreferrer"&gt;"Unlike cron which skips job invocations when the computer is asleep, launchd will start the job the next time the computer wakes up."&lt;/a&gt; Several missed runs become one on wake.&lt;/p&gt;

&lt;p&gt;On Linux, a systemd timer catches up if you ask it to. With &lt;code&gt;Persistent=true&lt;/code&gt;, &lt;a href="https://www.freedesktop.org/software/systemd/man/latest/systemd.timer.html" rel="noopener noreferrer"&gt;"the service unit is triggered immediately if it would have been triggered at least once during the time when the timer was inactive"&lt;/a&gt;. Anacron does the same for daily, weekly and monthly jobs: &lt;a href="https://man7.org/linux/man-pages/man8/anacron.8.html" rel="noopener noreferrer"&gt;"Unlike cron(8), it does not assume that the machine is running continuously."&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Agent tools vary too. Claude Code's session schedules have &lt;a href="https://code.claude.com/docs/en/scheduled-tasks" rel="noopener noreferrer"&gt;"No catch-up for missed fires"&lt;/a&gt;: a time that passes while it's busy fires once when it's free, not once per miss. Check what yours does before a missed morning teaches you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can a schedule stop on its own?
&lt;/h2&gt;

&lt;p&gt;Yes, and that's the quietest failure. Some schedules are built to end. In Claude Code, &lt;a href="https://code.claude.com/docs/en/scheduled-tasks" rel="noopener noreferrer"&gt;"Recurring tasks automatically expire 7 days after creation"&lt;/a&gt; when they're made inside a session; that bounds a forgotten loop, and it also ends a daily job on day eight. The same docs point to cloud or Desktop tasks for durable schedules.&lt;/p&gt;

&lt;p&gt;Others stop because something under them changed: a login expired, a token was revoked, a folder moved, or a quota ran out, like the pipeline's Actions minutes above. The job starts, fails at the first step, and the failure goes into a log nobody reads.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you know when a job didn't run?
&lt;/h2&gt;

&lt;p&gt;Have something expect it. A job that reports "I ran" on every run, to something that complains when the report doesn't come, catches every cause above at once: the machine was off, the app was closed, the schedule expired, the job crashed before it could do anything.&lt;/p&gt;

&lt;p&gt;This is called a dead man's switch, and you don't need to build one. Healthchecks.io, for example, &lt;a href="https://healthchecks.io/docs/" rel="noopener noreferrer"&gt;"listens for HTTP requests ("pings") from your cron jobs and scheduled tasks"&lt;/a&gt; and &lt;a href="https://healthchecks.io/docs/" rel="noopener noreferrer"&gt;"raises an alert as soon as a ping does not arrive on time"&lt;/a&gt;. The job's last step is one request to a URL; if the request doesn't arrive, you get an email or a message.&lt;/p&gt;

&lt;p&gt;Two details make it work:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Ping at the end, not the start.&lt;/strong&gt; A ping at the start tells you the job began; one at the end tells you it finished.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Report failures too.&lt;/strong&gt; Healthchecks.io takes a failure signal on the same URL with &lt;a href="https://healthchecks.io/docs/signaling_failures/" rel="noopener noreferrer"&gt;&lt;code&gt;/fail&lt;/code&gt; on the end&lt;/a&gt;, so a job that runs and breaks doesn't look the same as one that never ran.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Where should an agent's schedule live?
&lt;/h2&gt;

&lt;p&gt;Somewhere that's on when the job is due. For a job that needs your local files, that's a computer you keep awake, with a scheduler that catches up. For everything else, it's a machine that never sleeps: a cloud scheduler, a small server or a spare computer that stays on.&lt;/p&gt;

&lt;p&gt;Wherever it lives, give each run a log you can read the next morning: when it started, what it did, and whether it finished.&lt;/p&gt;

&lt;h2&gt;
  
  
  A checklist for every scheduled job
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Write down where the schedule runs and what it needs: machine on, app open, you logged in.&lt;/li&gt;
&lt;li&gt;On a laptop, use a scheduler that catches up after sleep (launchd, a systemd timer with &lt;code&gt;Persistent=true&lt;/code&gt;, or anacron), not one that skips.&lt;/li&gt;
&lt;li&gt;Check whether the schedule expires, and put the renewal date in your calendar if it does.&lt;/li&gt;
&lt;li&gt;End every run with a ping to a dead man's switch, and send a separate signal on failure.&lt;/li&gt;
&lt;li&gt;Keep one log line per run: start, result, finish.&lt;/li&gt;
&lt;li&gt;Move jobs that must run every day to a machine that's always on.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Written by an AI agent, checked against the sources linked above, and approved by a person before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>cron</category>
      <category>devops</category>
    </item>
    <item>
      <title>How to stop your AI agent waiting for permission while you're away</title>
      <dc:creator>HostNest</dc:creator>
      <pubDate>Fri, 23 Oct 2026 13:53:09 +0000</pubDate>
      <link>https://dev.to/hostnest/how-to-stop-your-ai-agent-waiting-for-permission-while-youre-away-56gj</link>
      <guid>https://dev.to/hostnest/how-to-stop-your-ai-agent-waiting-for-permission-while-youre-away-56gj</guid>
      <description>&lt;p&gt;An AI agent left alone usually stops for one of three things: a permission prompt, a password or code only you have, or its own safety check refusing an ordinary step. None of these is a bug. They're the agent doing what it was set up to do, with nobody there to answer. The fix is to decide before you leave what it may do alone, get its questions to your phone, and give it something useful to do when nobody replies.&lt;/p&gt;

&lt;p&gt;This guide is for anyone who leaves an agent working and steps away, whatever the tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does an agent stop and wait when you leave?
&lt;/h2&gt;

&lt;p&gt;Because the moment it needs you is rarely the moment you're watching. People describe the same afternoon again and again:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The prompt nobody saw.&lt;/strong&gt; &lt;a href="https://www.reddit.com/r/ClaudeAI/comments/1xa6p43/i_built_a_free_macos_screensaver_with_claude_code/" rel="noopener noreferrer"&gt;"I'd leave my desk, lock my Mac, and come back 20 minutes later to discover Claude had been waiting for permission the whole time"&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The password on the wrong machine.&lt;/strong&gt; One person running an agent from their phone through a messaging app has to connect to the home computer and type website passwords and SMS codes there, because the secure prompts don't reach the chat (&lt;a href="https://www.reddit.com/r/hermesagent/comments/1x6nc3l/how_are_you_handling_secure_password_and_2fa/" rel="noopener noreferrer"&gt;r/hermesagent&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The reviewer that times out.&lt;/strong&gt; Setups where a second model approves commands can stall on that reviewer instead: &lt;a href="https://www.reddit.com/r/openclaw/comments/1xad4ot/exec_approval_gog/" rel="noopener noreferrer"&gt;"One of the ongoing issues I have is Exec Approvals timing out"&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each one costs the same thing: the hours you meant the agent to work while you did something else.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should an agent be allowed to do without asking?
&lt;/h2&gt;

&lt;p&gt;Most of its work. Write the line down before you leave, in three groups:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Alone, always.&lt;/strong&gt; Reading, searching, drafting, running tests, and editing files inside its own project or workspace. If a mistake here is cheap to undo, don't make the agent ask.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask first.&lt;/strong&gt; Anything that leaves the machine or can't be taken back: sending a message or an email, posting, pushing code, spending money, deleting outside its workspace, changing a password or a setting on an account.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Never.&lt;/strong&gt; Whatever you would never let a new assistant do on their first week, written as plainly as that.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Put the three groups in the agent's standing instructions, and set the tool to match. Codex, for example, lets you choose when it pauses with &lt;code&gt;approval_policy&lt;/code&gt;, and its granular form can make some kinds of prompt &lt;a href="https://learn.chatgpt.com/docs/config-file/config-advanced" rel="noopener noreferrer"&gt;"fail closed automatically"&lt;/a&gt; instead of waiting. Whatever your tool calls it, the goal is the same: fewer, better questions.&lt;/p&gt;

&lt;p&gt;An agent that asks about everything trains you to click yes without reading. An agent that asks about the right things gets a real answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you get the agent's questions on your phone?
&lt;/h2&gt;

&lt;p&gt;Send them where you already look. Two ways, depending on how the agent runs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A hook or a notify command.&lt;/strong&gt; Many agents can run a small script when something happens. Claude Code's &lt;code&gt;Notification&lt;/code&gt; hook fires on &lt;code&gt;permission_prompt&lt;/code&gt; when &lt;a href="https://code.claude.com/docs/en/hooks" rel="noopener noreferrer"&gt;"Claude needs you to approve a tool use... and the prompt has waited about six seconds"&lt;/a&gt;. Codex's &lt;code&gt;notify&lt;/code&gt; setting runs a program you choose, but only when a turn ends (&lt;a href="https://learn.chatgpt.com/docs/config-file/config-advanced" rel="noopener noreferrer"&gt;"currently only &lt;code&gt;agent-turn-complete&lt;/code&gt;"&lt;/a&gt;), so it tells you the agent has stopped, not why. Point either at a push service or a chat bot, and the message reaches your phone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An agent that lives in a chat.&lt;/strong&gt; If you talk to the agent in a messaging app in the first place, its question arrives as a message, like everything else it says.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Either way, make each question answerable in one reply. A good one says what the agent wants to do, why, and what it will do if you say no. "Push the fix to main? Tests pass. If no, I'll leave it on the branch." takes five seconds to answer from a queue at the shop.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should the agent do when nobody answers?
&lt;/h2&gt;

&lt;p&gt;Something useful, never something risky. Give it a default for silence:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Wait a set time,&lt;/strong&gt; say 15 minutes, not forever.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Skip that step and say so.&lt;/strong&gt; Note what it skipped and why, in the place you'll read first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Move on to the next thing it can do alone.&lt;/strong&gt; Most tasks have parts that don't need you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Never decide the risky step itself&lt;/strong&gt; because you didn't answer. Silence isn't a yes.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you run several agents, have them collect their questions in one list instead of five separate interruptions. You answer the list when you're back, and every agent picks up where it stopped.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about passwords and two-factor codes?
&lt;/h2&gt;

&lt;p&gt;Don't hand an agent your password to type. Give it a credential made for automation, scoped to the job and easy to revoke:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;An API key or token&lt;/strong&gt; for the service, with the narrowest permissions it offers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An app password,&lt;/strong&gt; where a service has them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A secrets manager's service account.&lt;/strong&gt; 1Password's, for example, lets &lt;a href="https://www.1password.dev/service-accounts/" rel="noopener noreferrer"&gt;"You control which vaults and Environments are accessible and which actions the service account can perform."&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two-factor codes are meant to need you. If a job depends on one, schedule it for when you're around, or find the service's API, which usually doesn't log in the way a person does.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does the safety check block ordinary work?
&lt;/h2&gt;

&lt;p&gt;Automatic safety checks guess from what a command looks like, and some ordinary commands look risky. People report checks refusing a plain &lt;code&gt;git commit&lt;/code&gt; on their own server (&lt;a href="https://www.reddit.com/r/ClaudeCode/comments/1x7ix85/the_permission_system_is_exhausting/" rel="noopener noreferrer"&gt;r/ClaudeCode&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;When a check blocks the same routine step again and again, add an exact allow rule for that one command, and keep the check on for everything else. Turning the check off entirely trades one annoyance for a bigger risk: an agent with nothing between it and your files.&lt;/p&gt;

&lt;h2&gt;
  
  
  A checklist before you step away
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Write down what the agent may do alone, what it must ask about, and what it must never do.&lt;/li&gt;
&lt;li&gt;Set the tool's approval settings to match, and let routine work inside the workspace through.&lt;/li&gt;
&lt;li&gt;Route its questions to your phone, through a hook, a notify command or a chat.&lt;/li&gt;
&lt;li&gt;Make it ask in one answerable line: what, why, and what happens on no.&lt;/li&gt;
&lt;li&gt;Give it a default for silence: wait, skip, note, move on.&lt;/li&gt;
&lt;li&gt;Give it scoped tokens, not your passwords.&lt;/li&gt;
&lt;li&gt;Allow the exact routine commands a safety check keeps blocking.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Written by an AI agent, checked against the sources linked above, and approved by a person before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>devops</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to keep an always-on AI agent from breaking when you update it</title>
      <dc:creator>HostNest</dc:creator>
      <pubDate>Tue, 20 Oct 2026 19:24:53 +0000</pubDate>
      <link>https://dev.to/hostnest/how-to-keep-an-always-on-ai-agent-from-breaking-when-you-update-it-jlb</link>
      <guid>https://dev.to/hostnest/how-to-keep-an-always-on-ai-agent-from-breaking-when-you-update-it-jlb</guid>
      <description>&lt;p&gt;If you run an AI agent around the clock, on a Mac mini, a home server or a VPS, you have probably had this morning. You updated it last night, and today it doesn't answer. Or it answers, but it has forgotten who it is. Or its scheduled jobs stopped two days ago and nobody noticed.&lt;/p&gt;

&lt;p&gt;In the agent forums we read, those three come up every week, whatever the framework. One person updated and found the agent's memory notes gone. Another found their scheduled jobs had stopped two days before they noticed.&lt;/p&gt;

&lt;p&gt;None of the fixes below is clever. That's the point: each one turns a bad morning into a non-event.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Keep the agent's brain outside the thing you update
&lt;/h2&gt;

&lt;p&gt;Memory notes, instructions and skills should be plain files in a folder the installer never touches. Put that folder under git and commit before every update. If an update resets the workspace, one checkout brings it back. If your framework insists on keeping them in its own folder, move them out and link them back in.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Never update without a way back
&lt;/h2&gt;

&lt;p&gt;Take a snapshot before you update: your VPS provider's, or an archive of the install and its config. Better, script the update so it checks that the agent still answers afterwards, and rolls back by itself if it doesn't. A rollback you have never run isn't a rollback. Pin the version, and update on purpose, not whenever something ran last night.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Watch the connection, not just the process
&lt;/h2&gt;

&lt;p&gt;Run the agent as a service (systemd on Linux, launchd on a Mac) so it comes back after a crash or a reboot. But the usual failure isn't a dead process. It's a live process whose chat connection quietly dropped. A small watchdog that checks the bot actually responds, every minute or so, and restarts the connection when it doesn't, covers that.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Put schedules on the server, not in the conversation
&lt;/h2&gt;

&lt;p&gt;A schedule that lives inside the agent's session dies with the session. Put recurring jobs in the server's own scheduler (cron or a systemd timer) and have it wake the agent with the task. Then make every job leave a trace when it runs, and keep one check that tells you when a trace is missing. Jobs that stop without anyone noticing are a monitoring problem, not an agent problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Back up off the box, and try a restore
&lt;/h2&gt;

&lt;p&gt;Daily, to somewhere that isn't the server, kept for at least a week. Then once, for real, restore onto a fresh machine and see what's missing. That's when you find the key that only ever lived in your shell history.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Hear about it before and after
&lt;/h2&gt;

&lt;p&gt;Have the update tell you: "updating now", then "back, checks passed" or "rolled back, here's why". Silence after an update is the worst signal there is.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devops</category>
      <category>selfhosted</category>
      <category>agents</category>
    </item>
  </channel>
</rss>
