5 ms·

This is powerful. Combined with MCPs, you can pretty much automate a ton of work.

• esperent 6mo ago
  Can you give some examples?
  • adobrawy 6mo ago
    That feature was silent launched about week ago for me. I use it to: - perform review of latest changes of code to update my documentation (security policies, user documentation etc.) - perform review to latest changes of code, triage them, deduplicate and improve code - I review them, close them with comments for over-engoneering / add review for auto-fix - perform review of open GitHub issue with label, select the one with highest impact, comment with rationale, implement it and make pull request - I wake up and I have a few pull request to fix issues that I can approve /finish in existing Claude Code thread I want also use it to: - review recent Sentry issues, make GitHub issues for the one with highest priority, make pull request with proposed fix - I can just wake up and see that some crash is ready to be resolved Limit of 3 scheduled jobs is pretty impactful, but playing with it give me a nice idea on how I can reduce my manual work.
    • nerptastic 6mo ago
      Maybe I’m missing the point but we have some of these implemented without the tool - the only one that needs an API key is the log scraping. It’s been surprisingly cheap and if we want to swap models we can.
      • adobrawy 6mo ago
        Of course, this scheduled can be implemented on top of existing tools. However, it's incredibly convenient to have a UI where: - you can easily edit the prompt - you can see the prompt execution history - you don't need any infrastructure to orchestrate it - it works even when your computer is off Once you start using it, it turns out to be very convenient.