The aeon Log

Hot off the press Aeon vs Meta Muse: the agent that knows your life and the one you own
Meta launched Muse, a personal agent that runs your life from its cloud. Aeon runs your work from a repo you own: MIT-licensed skills on GitHub Actions, scored and self-repairing. A side-by-side on ownership, credentials, model choice, and cost.

The Articles

1. The Aeon Self-Healing Loop: How an AI Agent Repairs Itself
   The five-layer loop that scores every skill output, files issues when quality drops, patches skills that keep breaking, and reports weekly - so a scheduled aeon agent catches its own silent drift before you would.

2. Aeon vs Grok Bot: the $300 agent and the free one
   Grok Bot rents you a fleet of cloud agents; Aeon gives you one you own. The closest fight in the series, split by ownership, credentials, and cost - and Aeon can run on Grok for a fraction of the price.

3. How to Run an Autonomous AI Agent on GitHub Actions
   Schedule an AI agent as a GitHub Actions workflow: cron trigger, committed state, no server to run or patch yourself.

4. Aeon vs ChatGPT: the agent that works while you're gone
   ChatGPT answers when you ask. Aeon runs when you don't. Not about which chatbot is smarter, but where a chatbot stops being enough.

5. Aeon vs Claude Code: same engine, nobody at the wheel
   Claude Code is a session you drive, Aeon puts that session on cron. A stack, not a rivalry: Claude Code is one of the ten engines Aeon can drive unattended.

6. Aeon vs Hermes: two autonomous agents, one big difference
   Hermes lives on your machine, Aeon lives in the cloud and heals itself. The closest pair in the series, split by where an autonomous agent should live.

7. Make Your Agent Charismatic and Centered with SOUL.md and STRATEGY.md
   aeon's entire control surface is two Markdown files: SOUL.md says who the agent is, STRATEGY.md says what it's trying to do. Why prose beats tunable knobs.

8. aeon on the Wire: MCP and a Fleet of Forks
   Earlier posts framed aeon as a scheduler. This one argues an instance is a node: reachable over MCP as a tool provider, aware of forks it does not own.

9. Least Privilege for an Autonomous Agent
   aeon’s secret curl rewrite: every skill declares the keys it needs, and only those keys are injected, only for that call, only into the skill that asked.

10. **An Agent That Scans Itself**  
    

    Three scheduled scanners read aeon’s own codebase: vuln-scanner, skill-security-scan, and workflow-security-audit. What each one does with what it finds.

11. Signed by the Agent: Sigstore Attestation
    aeon now signs skill runs via Sigstore. Every eligible run produces an attestation binding its output to the GitHub Actions identity, verifiable independently.

12. 60 Days of aeon: Sigstore, Secrets, Self-Repair
    Two months of shipping: signed runs via Sigstore, per-skill secrets, a headless CLI, and a scanner that patches the framework workflows.

13. Receipts, Not Just Vibes
    The GitHub Actions tab is aeon’s entire observability stack. Why “quiet is a feature,” and how to read what your agent actually did last Tuesday at 04:00 UTC.

14. Skills That Build Skills
    A skill on aeon is a Markdown file - no DSL, no SDK, no compile step. And the agent can author new ones for itself, with git as the audit trail.

15. Letting Your Agent Spend Money
    How an aeon agent pays for the APIs it needs itself - x402, USDC, and a Base Account wallet via the Base MCP, no API keys, credit cards, or prefunded billing.

16. The Agent That Runs While You Sleep
    Why aeon does not need a server, a Dockerfile, or a 3 AM page. The architecture behind background-first agents on GitHub Actions.

17. Open-Source AI Agent Framework on GitHub Actions
    61 skills, scheduled on cron, no server, no SaaS dashboard. An autonomous agent that lives in your repo and runs on GitHub Actions.

RUN AEON733