Credentials. The API key is stored in a plain user file, so restrict its permissions and never commit it to version control.
Who it is forA developer who works across several project folders and wants one launch command everywhere.
The problemCloning the repo and setting up the environment for each project is repetitive and easy to get wrong.
The outcomeA frontier-agent command that starts the TUI from any project directory using your saved endpoint settings.
What you need first
- Git
- Python 3.12
- uv
- An OpenAI-compatible model endpoint with its API key, base URL, and model name
- Docker (optional, only for the container path)
Steps
uv tool install --python 3.12 git+https://github.com/ApodexAI/FrontierAgent.git- Put OPENAI_API_KEY, OPENAI_BASE_URL, and OPENAI_MODEL into ${XDG_CONFIG_HOME:-$HOME/.config}/apodex/env, then run
chmod 600on that file cd /path/to/projectfrontier-agent
Prompt for your agent
Install the FrontierAgent command from the repo at git+https://github.com/ApodexAI/FrontierAgent.git, then start it inside <project path>. The expected output is an open TUI session scoped to that project. Verify that the endpoint settings load from the user config file and that the session starts without errors.
Caveat. On macOS with Docker running, the container image has to be built once from a clone before this command runs as expected.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page