Requirements
Install uv >=0.12.20, <0.14. Node.js and npm are needed when you build the OpenSlide project. Choose one agent host. Plugin commands are host commands, not FrontierOps CLI commands.
Claude Code
claude plugin marketplace add Yuankai619/FrontierOps
claude plugin install frontierops@frontieropsCodex CLI
codex plugin marketplace add Yuankai619/FrontierOps
codex plugin add frontierops@frontieropsGitHub Copilot CLI
copilot plugin install Yuankai619/FrontierOps:plugins/frontieropsHost syntax may change. Consult the official Claude Code, Codex, and Copilot CLI documentation. The current end-to-end check used a local Codex checkout; remote Claude and Copilot installation has not been verified here.
Initialize the research workspace
Open the directory where you want to keep your research configuration and outputs. Ask the agent to run frontier-setup, or type setup. In Claude Code the explicit form is /frontierops:frontier-setup; in Codex it is $frontier-setup; in Copilot CLI it is /frontierops/frontier-setup.
For a normal installation, Setup uses uv tool install git+https://github.com/Yuankai619/FrontierOps.git. This puts the packaged Python tool in uv's tool environment. It creates frontier.yaml and frontier_output/ in your research workspace, but does not copy the FrontierOps source tree or fetch papers. An existing YAML file is validated and preserved. In a development checkout, the agent can use uv sync --locked and uv run --locked frontier from that checkout instead.
Continue with Config and Discover
Say config and describe the subject you want to track, then say discover. If live providers need credentials, set them in the agent process environment first; see Credentials. Discovery only runs when requested. Use its local page to select papers, then say briefing. The workflow page explains each action; the YAML reference explains every field.