README

Tech Blog ·
  Tech Report


 FrontierAgent

FrontierAgent is an open-source agent runtime, terminal product, and evaluation
suite for long-horizon research and file-based work. The frontier-agent TUI
ships two native workflows:

- ReAct — one stateful agent researches, reads files, writes deliverables,
  runs commands, and iterates in a task-scoped sandbox.
- Agent Team — a coordinator maintains a task board, delegates independent
  work to parallel sub-agents, collects their reports, and synthesizes the result.

The same workflow engine powers the benchmark runner used to evaluate Apodex
models. The framework, tools, workflows, and evaluation layer remain separate,
so each can be reused independently.

 [!IMPORTANT]
  🚀 Try FrontierAgent on the Apodex API — free for the next two weeks!

 No model hosting required. Get an API key, connect to the OpenAI-compatible
 Apodex-1.1 endpoint, and start running FrontierAgent in minutes.

 → Start building for free at platform.apodex.ai

 ⏳ This is a limited-time offer—come try it and let us know what you build!

New here? Use the documentation index to find the right
installation, SGLang, workflow, evaluation, or developer guide.


  


 Highlights

- Native Agent Team workflow. The coordinator decomposes the request,
  dispatches bounded parallel assignments, receives structured reports, and can
  use an optional fast reporter for final evidence review.
- Task Board. Agent Team's add_task and update_task events appear live in
  the TUI sidebar with pending, active, completed, blocked, and cancelled state.
- Sandboxed file work. Shell and file tools share one task-scoped filesystem:
  /inputs is read-only, /workspace is working state, and /outputs contains
  persistent deliverables. Authorization and sandbox failures are fail-closed.
- Asynchronous intervention. Type while an agent is running to queue a new
  instruction. It is injected at the next safe turn boundary without discarding
  the active run. In Agent Team mode it steers the coordinator; already-running
  sub-agents are allowed to finish.
- Transparent deliverables. On macOS/Docker, /outputs maps to
  .apodex/runs//outputs on the host. The same run directory also
  contains its checkpoint, trace, engine log, and trajectories.
- Approval, trace, and recovery. Mutating operations show a diff and require
  approval unless --yes is enabled. Sessions are checkpointed, every action is
  traced locally, /revert restores session changes, and --resume continues a
  saved run.
- Evaluation included. The subprocess runner supports research and
  file-grounded benchmarks, deterministic artifact collection, concurrency,
  progress inspection, and rerunning individual failures.


  


Conceptual Agent Team workflow, from task delegation and asynchronous report collection to verification and final synthesis.

 How it fits together

mermaid
flowchart LR
    U["User / benchmark task"] -- TUI["TUI or subprocess runner"]
    TUI -- R["Stateful ReAct"]
    TUI -- 

Top issues

Discussions