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

How to have an agent work a goal across many turns on a schedule with Centra Gideon Agent

Set up a long-running goal loop that works unattended and reports to your inbox.

Credentials. An unattended loop calls your configured model provider and tools on a schedule, so the provider key and any connected service can be used without you watching each run.

Who it is forA person with a recurring or multi-step research or admin goal who does not want to supervise each step of the work.

The problemA single chat reply cannot keep working on a goal over many turns, and remembering to restart the work each day is easy to forget.

The outcomeA loop that works the goal across turns on a schedule, with results collected in the inbox and the console showing running loops and scheduled jobs.

What you need first

  • Python 3.12 or newer
  • Node.js 22.12 or newer with npm, if you build the console from source
  • macOS or Linux, or Docker on Windows
  • A model provider credential or a local model, configured in the console after first start
  • A workspace directory and timezone for gideon setup

Steps

  1. Complete the self-host steps through .venv/bin/gideon gateway --no-open --port 10000 and open the console.
  2. In the console, add a model provider so the loop has a model to call.
  3. Create a goal loop in the console with a clear goal and a schedule.
  4. Check the console for running loops and scheduled jobs after the first scheduled run.
  5. Review items that need you in the inbox, and approve tool use when the console asks.

Prompt for your agent

In the Sidiora-Labs/centra-gideon-agent console, create a goal loop for <goal> on <schedule> and report the loop name, its schedule, and its first status. Verify that the loop appears under running loops and scheduled jobs before you report it as set up.

Caveat. The README lists loops, schedules and tool approvals but does not describe the exact console steps for creating a loop, so confirm the current console screens before you rely on the steps.

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