Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Schedule tasks on the web

code.claude.com

Post reply on HN
Print view View original

41–50 of 261 posts

Re: Schedule tasks on the web

#41

Post by tossandthrow »

_puk wrote: post #32
tossandthrow wrote: post #15

Earlier quoted context omitted.

I think the Ai agent will directly make a PR - tickets are for humans with limited mental capacity. At least in my company we are close to that flywheel.

Tickets need to exist purely from a governance perspective. Tickets may well not look like they do now, but some semblance of them will exist. I'm sure someone is building that right now. No. It's not Jira.

Yes, so my point is that PRs act as that governance layer - with preview environments, you can see the complexity and risk of the change etc.

Re: Schedule tasks on the web

#42

Post by esperent »

NuclearPM wrote: post #20
iBelieve wrote: post #7

Looks like I'm limited to only 3 cloud scheduled tasks. And I'm on the Max 20x plan, too :( "Your plan gets 3 daily cloud scheduled sessions. Disable or delete an existing schedule to continue." But otherwise, this looks really cool. I've tried using local scheduled tasks in both Claude Code Desktop and the Codex desktop app, and very quickly got annoyed with permissions prompts, so it'll be nice to be able to run sc…

0 7 * * 1-5 ANTHROPIC_API_KEY=sk-... /path/to/claude-cron.sh /path/to/repo >> ~/claude-reports.md 2>&1 Seems trivial.

A trivial way to rack up hundreds of dollars in API costs, sure.

But you can set up a claude -p call via a cronjob without too much hassle and that can use subscriptions.

Re: Schedule tasks on the web

#45

Post by tuo-lei »

nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

The missing piece for me is post-hoc review.

A PR tells me what changed, but not how an AI coding session got there: which prompts changed direction, which files churned repeatedly, where context started bloating, what tools were used, and where the human intervened.

I ended up building a local replay/inspection tool for Claude Code / Cursor sessions mostly because I wanted something more reviewable than screenshots or raw logs.

Re: Schedule tasks on the web

#46

Post by eru »

nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

Instead of having a trusted user, you can also do statistics on many users.

(That's basically what A/B testing is about.)

Re: Schedule tasks on the web

#47

Post by eru »

Gigachad wrote: post #26
tossandthrow wrote: post #15

Earlier quoted context omitted.

I think the Ai agent will directly make a PR - tickets are for humans with limited mental capacity. At least in my company we are close to that flywheel.

The agents have even more limited capacity

At the moment, maybe. But it's growing.

Re: Schedule tasks on the web

#48

Post by slopinthebag »

Leptonmaniac wrote: post #30
nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

I think that as a user I'm so far removed from the actual (human) creation of software that if I think about it, I don't really care either way. Take for example this article on Hacker News: I am reading it in a custom app someone programmed, which pulls articles hosted on Hacker News which themselves are on some server somewhere and everything gets transported across wires according to a specification. For me, this…

Art is and has always been about the creator.

Re: Schedule tasks on the web

#49

Post by hyperionultra »

nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

"Trusted user" also can be an Agent.

Re: Schedule tasks on the web

#50

Post by simianwords »

I remember when I tried to set something up with the ChatGPT equivalent like "notify me only if there are traffic disruptions in my route every morning at 8am" and it would notify me every morning even if there was no disruption.
Post reply on HN