Detailed Analysis
This Reddit post from r/ClaudeAI illustrates a common gap between what Claude Code power users expect from the platform and what it currently offers out of the box. The user, a self-described active Claude Code user who works entirely through manual, one-off sessions, is asking whether Claude (or a competing tool like GitHub Copilot) can be configured to autonomously monitor flight and hotel prices for an upcoming Japan trip, log results to a table, and send alerts when prices drop below a threshold. The request is notable not for its complexity as a use case, but because it exposes a structural limitation: Claude Code, in its default form, is a session-based, human-initiated tool. It doesn't natively run as a persistent background daemon that wakes up on a schedule, hits external APIs, and pushes notifications without a user manually invoking it each time.
The underlying technical challenge is real and worth unpacking. To build the workflow the user describes, someone would need to combine several pieces that Claude itself doesn't provide natively: a scheduling mechanism (cron job, GitHub Actions on a timer, or a cloud function), a way to programmatically query flight/hotel pricing (since airlines and OTAs like Google Flights, Skyscanner, or Booking.com don't offer simple free public APIs for this, most solutions rely on scraping or paid third-party aggregator APIs), persistent storage (a spreadsheet, database, or simple CSV/JSON log), and a notification layer (email, Slack, Discord webhook, or SMS via a service like Twilio). Claude Code could plausibly be used to write and maintain the scripts that do this scraping/API-calling and logging, and could even be invoked periodically to analyze the data and draft a summary, but the "always-on, checks-by-itself" behavior the user wants requires wrapping Claude's capabilities in external infrastructure that runs independently of a chat session.
This matters because it highlights a broader tension in how casual and even fairly technical users perceive "agentic AI" versus how these systems are actually architected today. There's an intuitive expectation that a capable coding assistant should be able to "just handle it" — set up a recurring task and forget about it — but true autonomy of that kind (persistent monitoring, self-triggering, notification-sending) is still something users have to engineer themselves using traditional automation tools (cron, Zapier, Make, n8n, GitHub Actions), with the LLM playing a supporting role in writing code or interpreting results rather than being the orchestrator itself. Anthropic has been pushing Claude Code toward more autonomous, longer-running workflows (subagents, hooks, background task support, and integrations with tools like GitHub Actions), but a fully self-scheduling "check prices and notify me" consumer use case still sits at the edge of what's turnkey versus what requires DIY plumbing.
This thread also reflects a growing pattern in the Claude community: non-developers or lightly technical users bringing everyday personal-automation problems (price tracking, trip planning, deal alerts) to a tool primarily built and marketed for software engineering. As agentic coding tools like Claude Code, Copilot, and Cursor mature, there's increasing pressure — and opportunity — for these platforms to abstract away the scheduling/infrastructure layer so that "set it and forget it" personal automations become as easy to request as a one-off coding task, closing the gap between user expectation and current agentic capability.
Read original article →