Short answer
Aeon is an autonomous agent framework built around scheduled tasks. Its dashboard runs on a small computer, and the tasks themselves run on your own GitHub Actions, using the GitHub credentials you connect. On Hivra, the dashboard lives on a Hivra Cloud computer that needs a paid plan. GitHub governs the task compute.
What Aeon is
Aeon is an autonomous agent framework for work that should happen on a schedule: a daily briefing, a recurring repository check, a research update that arrives without you asking. You describe a task and when it runs, and it happens whether you are online or not.
It is different from agents you open and talk to. You are not sitting in a chat while it works. You configure tasks in a dashboard, and the agent does them when the schedule fires. If you want a conversation, other agents fit better. If you want a routine that runs on its own, that is what Aeon is for.
Where the work actually runs
This is the part that surprises people. Aeon's dashboard runs on a small computer. Its tasks do not. They run as GitHub Actions workflows in a fork of Aeon inside your own GitHub account.
That separation has practical effects. The dashboard is always there when you want to check in or change a task. The work itself does not compete for the CPU and memory of the computer hosting the dashboard. And the limits and pricing for task runs are GitHub's, not Hivra's: your GitHub account may incur its own Actions usage charges.
Your agent needs computer access. It doesn't need your computer. Here the agent gets two homes: a hosted computer for its dashboard, and GitHub's runners for its tasks. Nothing runs on your laptop.
What Hivra hosts, and what it does not
Hivra hosts the dashboard. It sets up a small computer for it, puts it behind Hivra's authenticated gateway, and gives you a connection flow for your GitHub account and your Aeon fork. You come back to that dashboard to inspect and change tasks.
Hivra does not take over your fork, and it does not turn your scheduled jobs into Hivra compute. They stay in GitHub, with your repository settings and your task credentials. Hivra cannot exempt them from GitHub's Actions limits or pricing.
The dashboard computer is small, with a floor of 0.5 vCPU and 1 GB of RAM. Every Hivra Cloud computer needs a paid plan, and the entry plan is $9.99 a month for 2 vCPU and 4 GB of RAM. A free Hivra account works with a server you connect yourself.
Connecting GitHub
After the dashboard is up, you connect a GitHub token. The current integration needs read and write access to Secrets, Actions, Contents and Workflows. Grant it the narrowest repository scope you can, rather than your whole account.
The connection flow creates or syncs your fork, enables Actions and stores the task secrets as GitHub repository secrets. If the token does not have enough permission to write secrets, the connection stops and tells you what to change.
Treat that token as a powerful credential. It can change workflows in your repository. If you stop using Aeon, revoke it and review the secrets stored in the fork.
Models and what to automate first
A task needs a model to think with. Aeon on Hivra can use Hivra credits, which reach models through Venice, or the model access you set up yourself. Either way, model usage is a separate cost from the dashboard computer and from GitHub's minutes.
Start with a low-risk task you can read the output of: a research digest on a topic you follow, or a scheduled review of a repository you own. Check the first few runs before you widen what a task is allowed to touch. You stay responsible for what each task can access and change.
For more on turning routines into agent work, see AI agent automation examples. The Aeon docs page covers setup, and the Aeon agent page shows the launch options.
Aeon or an agent that stays open
Pick Aeon when the unit of work is a scheduled job and you are happy for GitHub to run it. Pick an agent such as Agent Zero when the unit of work is a goal you hand over and watch. Aeon's tasks run on a schedule you set, and they only do what the credentials and tools you connect allow.
Hivra is an independent hosting service and is not affiliated with or endorsed by the Aeon project.
Common questions
Does Aeon run its tasks on my Hivra computer?
No. The dashboard lives on a Hivra computer, but Aeon's scheduled tasks run on your own GitHub Actions. That is the main difference from the other agents.
What GitHub permissions does it need?
A token with read and write access to Secrets, Actions, Contents and Workflows. Scope it to the repository where possible, and revoke it if you stop using Aeon.
What does Aeon cost to host?
Every Hivra Cloud computer needs a paid plan, even though the dashboard computer is small. GitHub Actions usage and model usage are billed separately by their own providers.
Will tasks keep running when I close my laptop?
Yes, as long as your GitHub Actions setup is active and the tasks are configured correctly. They do not depend on an open browser.