FrontierAgent
🧩 FrontierAgent, our agent framework, open-sourced alongside it, native command-line TUI, ReAct and Agent Team modes, one command on macOS and Linux, no preinstall, no hard Docker dependency.
Runs with mockssource: GitHubhomepagePythonApache-2.0commit a3c1be339c24
Python, Apache-2.0 licensed. The project labels itself: agent orchestration, agentic ai, agentic framework, ai agents, harness, multi agent, terminal agent and tui.
FrontierAgent runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, 1786 tests pass, CLI binary produces help/version output and successfully executes tasks against an OpenAI-compatible endpoint returning correct agent responses.
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.
- Install time
- 3 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pytest apodex/tests: 877 passed; pytest tests: 909 passed, 3 skipped; frontier-agent --no-tui -y -p 'say hello' against mock OpenAI-compatible server (http://127.0.0.1:8979/v1) exited 0, returned expected response text; import_smoke.py: 291 framework + 340 eval modules OK
- Model tokens used
- 198,945
- Exact commit tested
- a3c1be339c24
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `apodex/tests`: **877 passed**, 0 failed - `tests/`: **909 passed**, 3 skipped (skips are `test_hf_space_leaks` — expected without HF tokens) - Total: **1786 tests passed**, 0 failures **CLI binary**: `frontier-agent --help` and `--version` both work (`FrontierAgent 0.1.0`). **Import smoke**: 291 framework + 340 eval modules imported cleanly (`tools/import_smoke.py` → OK). **End-to-end verification**: I stood up a mock Argusic-compatible API server (handling both streami… ``` frontier-agent --no-tui -y -p "say hello" ``` Exit code **0**, printed the expected response: `Hello! I am a mock AI assistant. ✓ done · turns=1 … **Pre-existing lint issues (13)** from ruff — all pre-existing, none introduced. **No errors encountered** — every step worked on first try.
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 3.2 minutes, faster than the median of the 20 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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.
Of the 21 agent-orchestration projects Argusic has installed and timed, FrontierAgent was the 6th fastest to reach a running state, and 15 of 21 reached one at all.
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 | 2/3 | Runs with mocks | 92.00 | 0.05 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.18 |
Topics (from GitHub)
agent-orchestrationagentic-aiagentic-frameworkai-agentsharnessmulti-agentterminal-agenttui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/frontieragent)Questions
- Does FrontierAgent run?
- FrontierAgent runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test FrontierAgent?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a3c1be339c24. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test FrontierAgent?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does FrontierAgent take to install?
- 3.2 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 FrontierAgent need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing FrontierAgent?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does FrontierAgent compare with the alternatives?
- Of the 21 agent-orchestration projects Argusic has installed and timed, FrontierAgent was the 6th fastest to reach a running state, and 15 of 21 reached one at all.
- Where is the evidence for FrontierAgent?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.