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

How to run a saved agent on a schedule and review each session with Trueforge

Save an agent once, run it on a recurring cadence without you present, and audit each run.

Who it is forAn operations or support engineer who needs the same agent task to run repeatedly, such as a daily check.

The problemRepeating agent work by hand is slow, and unattended runs are hard to audit without a record of what the agent did.

The outcomeA saved agent that runs on a schedule, with each run's turns, tool calls, subagents, tokens, and timing available for review.

What you need first

  • A machine where you can run npx, for the local quickstart
  • API access to at least one model provider you plan to connect (OpenAI, Anthropic, Google Gemini, or an OpenAI-compatible endpoint)
  • Optional: credentials for any remote MCP server you plan to use (header auth or OAuth)
  • For hosted mode: Postgres and Redis, plus Docker Compose, Helm, or Railway

Steps

  1. Create and save an agent that selects the models, MCP tools, and skills it needs.
  2. Open Schedules and set the saved agent to run on a recurring cadence.
  3. Wait for one scheduled run to finish.
  4. Open Sessions and review that run's turns, tool calls, subagents, tokens, and timing.
  5. Adjust which tools need approval so that unattended runs behave as you expect.

Prompt for your agent

Using the truefoundry/trueforge repo, take the saved agent named <agent-name> and set a schedule that runs it every <cadence>. After one scheduled run, report its session ID and tool call count from Sessions. Verify that the run completed without a pending approval.

Caveat. The README does not describe how approvals behave during scheduled runs, so test one run before relying on it unattended.

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