future-agi
Open-source, end-to-end platform for evaluating, observing, and improving LLM and AI agent applications. Tracing · Evals · Simulations · Datasets · Gateway · Guardrails. Self-hostable. Apache 2.0.
Runs with mockssource: GitHubhomepagePythonApache-2.0commit ec05d596da56
Python, Apache-2.0 licensed. The project labels itself: agent evaluation, ai agents, ai evals, ai gateway, ai observability, evals, evaluation framework and guardrails.
future-agi runs, with stand-ins for the services it depends on. An Argusic agent installed it in 49 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Frontend dependencies installed with yarn, unit and integration tests pass (11/11) using jsdom environment. Backend dependencies installed via uv sync (441 packages). Django 5.1.8 and Django REST framework import correctly. Backend cannot fully start or run tests without Docker for PostgreSQL, ClickHouse, Redis, and MinIO.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Docker daemon available - required for the standard install (docker compose)
- Node.js v18.19.1 installed, but frontend requires >=22.18.0
- Frontend test: 1 performance test fails with timing flake - expected duration <200ms but got ~365ms in this container
- Backend tests require Docker-based test infrastructure (PostgreSQL, ClickHouse, Redis, MinIO via docker-compose.test.yml) - cannot run without it
- Install time
- 49 minutes
- Cold machine to finish
- 50 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npx vitest run src/__tests__/unit/utils.test.js src/__tests__/integration/component-integration.test.jsx --reporter=verbose exited 0 with 11/11 tests passed
- Model tokens used
- 433,979
- Exact commit tested
- ec05d596da56
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
PROPERTY_CATALOG_SEQUENCER.md README.md cmd config docker-compose.catalog-kafka.dev.yml docker-compose.standalone.yml Here's my comprehensive report on what was accomplished and where the blockers are. 2026-10-04T17:06:10.332284Z ERROR codex_core::session: failed to record rollout items: thread 01a10… 2026-10-04T17:06:10.335356Z ERROR codex_core::session: failed to record rollout items: thread 01a10… tokens used 433,979 Here's my comprehensive report on what was accomplished and where the blockers are.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 49 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.31 |
Topics (from GitHub)
agent-evaluationai-agentsai-evalsai-gatewayai-observabilityevalsevaluation-frameworkguardrailshallucination-detectionllm-evaluationllm-observabilityllm-tracingllmopsmodel-evaluationobservabilityopentelemetryrag-evaluationsimulationtelemetrytracing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/future-agi)Questions
- Does future-agi run?
- future-agi runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 49 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test future-agi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ec05d596da56. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test future-agi?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does future-agi take to install?
- 49 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does future-agi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing future-agi?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for future-agi?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.