DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to schedule recurring agent tasks with natural-language prompts with Grok App

Set up one-off or repeating agent jobs and review their execution logs.

Remote script. A scheduled task can run agent tools without a person watching, so use Ask mode for anything that changes files or runs commands.

Who it is forA developer who wants routine checks or reports produced by the agent on a schedule.

The problemRoutine agent tasks like status checks need someone to start them manually each time.

The outcomeAn automation that runs on a schedule and leaves a visual execution log to review.

What you need first

  • Grok Build CLI (grok) version 0.2.112 or newer, installed and signed in, or an API key or custom relay configured in the app
  • A project folder you are willing to let the agent work in
  • Git installed if you plan to use Git worktrees or Git diff review

Steps

  1. Open the Scheduled Automations area in Grok App.
  2. Describe the task in plain language and let the app create the prompt.
  3. Choose whether the task is recurring or one-off and select the project it should run in.
  4. Keep Ask permission mode unless you have decided the task can run unattended.
  5. Open the visual execution log after the first run to check the output.

Prompt for your agent

Using the Grok App repo (https://github.com/RongleCat/grok-app), create a scheduled automation for project <project-name> that runs the task <task-description> on <schedule>. Expected output: an automation entry with an execution log after its first run. Verify the permission mode before the first scheduled run.

Caveat. The README does not describe the schedule syntax or limits, so verify how recurrence is set in the app before relying on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page