AgentiLoopGo

🌐 English · Español · Français · Deutsch · 中文 (简体) · Русский · 한국어 · 日本語

🎉 We just shipped release v0.0.4 for Mac, Windows and Linux!

Take it for a spin! Read the README and see how long it takes you to get AgentiLoop up and running. If you hit any issues, let us know. We'd love your feedback.

Bonus: A Rust version is available too: AgentiLoopCLI → https://github.com/AgentiLoop/AgentiLoopCLI

Try both and tell us which one does it better: Go or Rust? 🐹 vs 🦀

💖 Sponsor AgentiLoop

Like what you see? Help keep AgentiLoop fast and cross-platform. Sponsor us on GitHub Sponsors → AgentiLoop. Tiers and perks are in the Sponsorship guide.

AgentiLoop is an AI coding agent that runs in your terminal, in the spirit of Claude Code. You describe what you want in plain language. The agent reads your files, edits code and runs commands to get it done, and it asks your permission before it changes anything.

It's written in Go and runs on macOS, Linux and Windows. It is the Go twin of AgentiLoopCLI (Rust): same features, same options, same settings, session and MCP files, so you can switch between them freely. It works with Claude (Anthropic), OpenAI, local models through Ollama or LM Studio, and oMLX on Apple Silicon.

Created with AgentiLoop Agent! This is our baby. Prebuilt binaries for macOS, Linux and Windows are on the Releases page, or compile it from source with Go.

🚀 New here? Up and running in 5 minutes

No Rust, no Go, no compiling. You download one file, give it an API key and start chatting. Follow the steps in order.

1. Download AgentiLoop

First find out which file you need:

Your computer	File to download
Mac with Apple Silicon (M1, M2, M3, M4…)	`agentiloop-macos-arm64.tar.gz`
Mac with an Intel chip	`agentiloop-macos-x86_64.tar.gz`
Linux, 64-bit PC	`agentiloop-linux-x86_64.tar.gz`
Linux on ARM (Raspberry Pi 4/5, ARM servers)	`agentiloop-linux-arm64.tar.gz`
Windows 10/11	`agentiloop-windows-x86_64.zip`

Not sure? On Mac or Linux, run uname -m. arm64 or aarch64 means arm64, and x86_64 means x86_64.

macOS and Linux. Open Terminal and paste these lines. This example uses the Apple Silicon file, so change macos-arm64 in the first three lines if yours is different:

curl -LO https://github.com/AgentiLoop/AgentiLoopGo/releases/download/v0.0.4/agentiloop-macos-arm64.tar.gz
tar xzf agentiloop-macos-arm64.tar.gz
mkdir -p ~/.local/bin && mv agentiloop-macos-arm64/agentiloop ~/.local/bin/

That puts the program in ~/.local/bin, a folder in your home directory. The setup wizard in step 3 offers to tell your terminal to look there.

Windows. Open PowerShell (Start menu → type "PowerShell") and paste:

Invoke-WebRequest https://github.com/AgentiLoop/AgentiLoopGo/releases/download/v0.0.4/agentiloop-windows-x86_64.zip -OutFile agentiloop.zip
Expand-Archive agentiloop.zip -DestinationPath $HOME\agentiloop -Force
$p = [Environment]::GetEnvironmentVariable("Path", "User")
[Environment]::SetEnvironmentVariable("Path", "$p;$HOME\agentiloop\agentiloop-windows-x86_64", "User")

The last two lines add AgentiLoop to your PATH. Close PowerShell and open a new window so it picks up the change.

2. Get an API key

AgentiLoop is the agent. The "brain" is an AI model that you connect it to. Pick one:

Option	Where to get it	Cost
Claude (recommended)	console.anthropic.com → Create Key. It starts with `sk-ant-`	Pay per use
OpenAI	platform.openai.com/api-keys. It starts with `sk-`	Pay per use
Ollama (runs on your own computer)	Install from ollama.com, then run `ollama pull qwen2.5-coder`	Free, no key

Copy the key somewhere safe. You'll paste it in the next step.

3. Run the setup wizard

Because ~/.local/bin isn't on your PATH yet, start it with its full path this one time (on Windows step 1 already fixed the PATH, so just type agentiloop):

~/.local/bin/agentiloop

When no key is saved yet, the wizard starts on its own and asks five things:

Which provider — Claude, OpenAI, a local OpenAI-compatible server (Ollama, LM Studio, …) or oMLX. Type a number.
Your API key — typed hidden, nothing shows on screen. Local servers usually need none; for oMLX on the same Mac the wizard reads the key from oMLX's own settings, so it doesn't even ask.
Connection check — the wizard talks to the provider right away. If the key is wrong it tells you and offers to try again; nothing is saved until it works.
Which model — pick one from the list the provider returned, or press Enter for the default. You can change it any time later with /model.
Where to keep the key — press Enter for the default, ~/.agentiloop/env, a private file only AgentiLoop reads. The other choices, for people who also want the key in their shell or in the macOS Keychain, are explained under Advanced below.

Last, the wizard notices that ~/.local/bin isn't on your PATH and offers to add it. Press Enter (yes). Then it says All set and drops you at the prompt. Here is a full run choosing Claude and accepting the defaults (your model list will differ):

$ ~/.local/bin/agentiloop
Welcome to AgentiLoop! Let's set things up (about a minute).
Settings are kept in /Users/you/.agentiloop. Run `agentiloop --setup` or `/setup` to redo this, `agentiloop --reset` to start over.

Which model provider do you want to use?
  1  Claude (Anthropic) — API key from console.anthropic.com
  2  OpenAI — API key from platform.openai.com
  3  Ollama, LM Studio or another OpenAI-compatible server (local, usually no key)
  4  oMLX (local Apple Silicon server; reads ~/.omlx/settings.json)
Provider [1-4, default 1]: 1
Anthropic API key (starts with sk-ant-, input hidden):
Checking the connection…
Connected (8 model(s) available).

Pick a model (change it any time with /model):
   1  claude-sonnet-5  (default)
   2  claude-…
   3  claude-…
   …
Model [1-8, an id, or Enter for claude-sonnet-5]:

Where should the credential be saved?
  1  /Users/you/.agentiloop/env (recommended; only agentiloop reads it, file mode 600)
  2  Also add it to /Users/you/.zshrc so other tools in your terminal see it
  3  macOS Keychain, with a line in /Users/you/.zshrc that reads it (nothing stored in plain text)
Save to [1-3, default 1]:
saved to /Users/you/.agentiloop/env

`/Users/you/.local/bin` is not on your PATH, so `agentiloop` only works with its full path.
Add it to PATH in /Users/you/.zshrc? [Y/n]
updated /Users/you/.zshrc (between `# >>> agentiloop >>>` and `# <<< agentiloop <<<`); it applies to new terminals

All set: anthropic / claude-sonnet-5. Type a request at the prompt, /help for commands, /exit to leave.

You can start chatting right here, or type /exit and carry on with step 4. From now on a plain agentiloop starts straight into the prompt.

Good to know:

For Claude you can paste either a normal API key (sk-ant-api…) or a Claude Code token (sk-ant-oat01-…, from claude setup-token); AgentiLoop detects which kind it is.
Option 3 (Ollama, LM Studio, …) also asks for the server URL. The default, http://localhost:11434/v1, is right for a local Ollama, so just press Enter.
The wizard runs in whichever interface you use. Start with --tui and the same questions appear inside the full-screen interface; when it finishes you are already at the prompt:

Rerun or redo it any time:

agentiloop --setup          # wizard on the plain terminal
agentiloop --setup --tui    # wizard inside the full-screen TUI (as in the screenshot)
/setup                      # from inside a running session (REPL or TUI)
agentiloop --reset          # forget everything and start from brand new

🔒 Keep your key private. ~/.agentiloop/env is readable only by you. Don't paste the key into chats or commit it to git. On a Mac, option 3 in the "Where should the credential be saved?" question stores it in the Keychain instead, so it's never on disk in plain text.

Advanced: setting the key by hand (skip this if the wizard worked for you)

If you'd rather manage the key yourself, or you are running AgentiLoop in a script or CI where nobody can answer the wizard, set one of these environment variables and AgentiLoop will use it without asking:

I want to use…	Set this
Claude (Anthropic)	`export ANTHROPIC_API_KEY=sk-ant-...`
OpenAI	`export OPENAI_API_KEY=sk-...`
Ollama, LM Studio, or any OpenAI-compatible server	`export OPENAI_BASE_URL=http://localhost:11434/v1` (your server's address; no key needed for local servers)
oMLX (local models on Apple Silicon)	Usually nothing. Start oMLX, then run AgentiLoop with `-p omlx`

oMLX details. When oMLX runs on the same Mac, AgentiLoop reads the server port and API key from oMLX's own settings file (~/.omlx/settings.json). If oMLX runs on another machine, or you want to override those settings:

export OMLX_BASE_URL=http://192.168.1.50:7777/v1   # the oMLX server's address (or OMLX_PORT=7777 for localhost)
export OMLX_API_KEY=...                            # the API key from oMLX's settings

If oMLX has API key verification turned off, no key is needed.

An export only lasts for the terminal tab you typed it in. To make it permanent you'd add the line to your shell profile (~/.zshrc on macOS), which is exactly what the wizard's "Also add it to ~/.zshrc" choice does for you. Likewise the wizard's "macOS Keychain" choice is the hands-free version of this:

# one time: store the key in your Keychain
security add-generic-password -a "$USER" -s ANTHROPIC_API_KEY -w "sk-ant-..."

# in ~/.zshrc: load it for every new terminal
export ANTHROPIC_API_KEY="$(security find-generic-password -a "$USER" -s ANTHROPIC_API_KEY -w 2>/dev/null)"

4. Check that it works

Open a new terminal window so it picks up the PATH change from the wizard (Windows: a new PowerShell window). Then:

agentiloop --version

You should see agentiloop 0.0.4. Now run it with no options:

agentiloop

It should go straight to the prompt. If the wizard starts again instead, the key didn't get saved: go through step 3 once more.

5. Your first session

Go to a project folder and start the full-screen interface:

Start with a new, empty test folder so you can try it safely. For a real project, cd into that project's folder instead (for example cd ~/code/my-app).

mkdir -p ~/agentiloop-test
cd ~/agentiloop-test
agentiloop --tui

Using Ollama? Tell it the provider and a model you've pulled: agentiloop -p openai -m qwen2.5-coder --tui.

Now just type what you want in plain English and press Enter. Some good first prompts:

explain what this project does
list the files in src and tell me which one is the entry point
find the TODO comments and summarize them
add a --verbose flag to the command-line parser
run the tests and fix anything that fails
create a README.md for this project

Before the agent changes a file or runs a command, it asks you. Press y for yes, n for no, a to always allow that tool for the session, or Esc to cancel the request. Esc also stops the agent at any point while it is working; the conversation is kept, so just type your next prompt. Press Ctrl-C to quit. Next time, a plain agentiloop starts the same way and picks up your last conversation.

Just want one answer without the chat? Pass the question as an argument:

agentiloop "explain what this project does"

What can it do? (tools)

The agent works with five built-in tools. You don't call them yourself. You describe the goal, and the agent picks the tool:

Tool	What it does	Asks first?
`read_file`	Reads a file (with line numbers)	No
`list_dir`	Lists the files in a folder	No
`write_file`	Creates a new file or overwrites one	Yes
`edit_file`	Changes an exact piece of text in a file	Yes
`bash`	Runs a shell command, like tests, builds or `git` (`sh -c` on Mac/Linux, `cmd /C` on Windows)	Yes

Want more tools, like web search, databases or GitHub? Add MCP servers; see Adding tools with MCP.

The help command

agentiloop --help lists every option:

$ agentiloop --help
AgentiLoop — a cross-platform agentic coding loop for your terminal.

Usage: agentiloop [OPTIONS] [PROMPT]...

Arguments:
  [PROMPT]...  One-shot prompt. If omitted, starts an interactive REPL

Options:
  -p, --provider PROVIDER   Model backend (PROVIDER): anthropic, openai (OpenAI-compatible: OpenAI, Ollama,
                            LM Studio, Groq, OpenRouter, … via OPENAI_BASE_URL), or omlx (local
                            oMLX server, http://localhost:8000/v1). Defaults to the last one used,
                            then auto-detected from which credentials are set. [env: AGENTILOOP_PROVIDER]
  -m, --model MODEL         MODEL id to use. Defaults to the last model used with this provider
                            (~/.agentiloop/settings.json), then the provider's default. [env: AGENTILOOP_MODEL]
      --yes                 Skip all permission prompts (dangerous; intended for CI). Never remembered. [env: AGENTILOOP_YES]
      --max-turns N         Max provider round-trips (N) per prompt [default: last used, then 50]
      --compact-at TOKENS   Summarize the conversation once a request reaches this many input TOKENS (0 = never)
                            [default: last used, then 150000] [env: AGENTILOOP_COMPACT_AT]
  -C, --cwd DIR             Working directory (DIR) the agent operates in (defaults to cwd)
  -r, --resume ID           Resume a saved session by ID (see /sessions)
  -c, --continue            Resume the most recent session for this working directory
                            (the default for interactive launches; kept for scripts)
      --new                 Start a new session instead of continuing the last one in this directory
      --tui                 Full-screen terminal UI instead of the line REPL. Remembered. [env: AGENTILOOP_TUI]
      --no-tui              Use the line REPL even if the TUI was used last time
      --no-mcp              Don't start MCP servers from ~/.agentiloop/mcp.json / ./.mcp.json. [env: AGENTILOOP_NO_MCP]
  -h, --help                Print help
  -V, --version             Print version

Inside a session, type /help to see the chat commands (/model, /sessions, /resume, /clear, /compact, /mcp, /exit). The full reference is in All options and Commands inside the chat.

Stuck? Quick fixes

You see	Fix
`command not found: agentiloop`	`~/.local/bin` isn't on your PATH. Open a new terminal window first; if that doesn't help, run `~/.local/bin/agentiloop --setup` and say yes when it offers to add it to PATH. On Windows, open a new PowerShell window
`Error: no provider credentials found`	No key is saved. Run `agentiloop --setup` (step 3), then check with step 4
macOS: "agentiloop" cannot be opened / unidentified developer	This happens if you downloaded with a browser instead of `curl`. Run `xattr -d com.apple.quarantine ~/.local/bin/agentiloop`
Windows: Windows protected your PC	Click More info → Run anyway
`401` / `invalid x-api-key` / authentication error	The key is wrong or was pasted with spaces or quotes. Copy it again and run `agentiloop --setup` to enter it afresh
Ollama: model not found	Run `ollama list` and pass the exact name with `-m`
It keeps using an old model or provider	It remembers your last choices. Pass `-p` / `-m` to change them, or run `agentiloop --reset` to start over

Still stuck? Open an issue and paste the command and the error. We'll help.

Quick start

Three steps: install it, give it a model, run it.

Step 1: Install

Download: grab the archive for your platform from Releases, unpack it and put agentiloop (agentiloop.exe on Windows) on your PATH.

Or build it: if you don't have Go yet (1.25 or newer), install it from go.dev/dl. Then:

go install github.com/AgentiLoop/AgentiLoopGo/cmd/agentiloop@latest

or from a clone:

git clone https://github.com/AgentiLoop/AgentiLoopGo.git
cd AgentiLoopGo
go install ./cmd/agentiloop

This builds the program and puts an agentiloop command on your PATH, in ~/go/bin (%USERPROFILE%\go\bin on Windows). No C compiler is needed.

Not installing? Everything in this README also works from inside the repo folder. Wherever you see agentiloop <options>, type go run ./cmd/agentiloop <options> instead.

Step 2: Connect a model

AgentiLoop needs a model to talk to.

Easiest: just run agentiloop. On a machine with no key set up it starts a short wizard that asks which provider you want, takes your key (typed hidden), checks the connection, lets you pick a model and saves the key to ~/.agentiloop/env (only AgentiLoop reads it). You can rerun it any time with agentiloop --setup, and agentiloop --reset puts everything back to brand new.

agentiloop --setup          # wizard on the plain terminal
agentiloop --setup --tui    # wizard inside the full-screen TUI (as in the screenshot)
/setup                      # rerun it from inside a running session (REPL or TUI)

The wizard runs in whichever interface you use. agentiloop --setup asks its questions on the plain terminal; agentiloop --setup --tui (or a remembered TUI) asks them inside the full-screen interface, as in the screenshot, and drops you straight into the prompt when it is done. Inside a running session, /setup does the same in both.

By hand: set one of these in your terminal instead:

I want to use…	Do this
Claude (Anthropic)	`export ANTHROPIC_API_KEY=sk-ant-...`
OpenAI	`export OPENAI_API_KEY=sk-...`
Ollama, LM Studio, or any OpenAI-compatible server	`export OPENAI_BASE_URL=http://localhost:11434/v1` (use your server's address; no key needed for local servers)
oMLX (local models on Apple Silicon)	Usually nothing. Start oMLX, then run AgentiLoop with `-p omlx` (see below)

For Claude you can use a normal API key (sk-ant-api…) or a Claude Code token (sk-ant-oat01-…, which you get from claude setup-token). AgentiLoop detects which kind it is.

oMLX details. When oMLX runs on the same Mac, AgentiLoop reads the server port and API key from oMLX's own settings file (~/.omlx/settings.json), so you don't need to export anything. If oMLX runs on another machine, or you want to override those settings, export them yourself:

export OMLX_BASE_URL=http://192.168.1.50:7777/v1   # the oMLX server's address (or OMLX_PORT=7777 for localhost)
export OMLX_API_KEY=...                            # the API key from oMLX's settings

If oMLX has API key verification turned off, no key is needed.

An export only lasts for the terminal tab you typed it in. To make it permanent, add the line to your shell profile (~/.zshrc on macOS). On a Mac you can keep the key in the Keychain rather than in the file:

# one time: store the key in your Keychain
security add-generic-password -a "$USER" -s ANTHROPIC_API_KEY -w "sk-ant-..."

# in ~/.zshrc: load it for every new terminal
export ANTHROPIC_API_KEY="$(security find-generic-password -a "$USER" -s ANTHROPIC_API_KEY -w 2>/dev/null)"

Step 3: Run it

Go to the project you want to work on and start AgentiLoop:

cd ~/my-project
agentiloop --tui

--tui opens the full-screen interface, which we recommend. Type what you want, e.g. "find where the config file is loaded and add a --verbose flag", and press Enter.

You'll see the agent's replies, each tool it uses (🔧) and each result (✓ or ✖). The box at the bottom shows what it's doing right now, for example ✻ Thinking... 12s. Before it writes a file or runs a command, it asks you:

y: yes, this time
n: no
a: always allow this tool for the rest of the session
Esc: cancel the whole request; the conversation is kept

Press Esc any time the agent is working to stop it. What it already did and said stays in the session, so you can type a correction or a new prompt right away. (Without --tui, Ctrl-C stops a running request instead.)

Three ways to use it

Mode	Command	Good for
TUI (full screen)	`agentiloop --tui`	Everyday use: scrolling history, live status, clickable links
Chat (line by line)	`agentiloop`	Simple terminals, or if you prefer plain text
One-shot	`agentiloop "explain this project"`	One question: it answers, then exits. Handy in scripts

Keys in the TUI: Enter sends · ↑ / ↓ go through earlier prompts · PgUp / PgDn or the mouse wheel scrolls · Esc stops the running request (the session is kept) · Ctrl-U clears the line · Ctrl-C quits.

It remembers your setup

You only type your options once. AgentiLoop saves how you launched it, so next time a plain agentiloop starts the same way:

agentiloop -p anthropic --tui    # first time: choose provider and TUI
agentiloop                       # from now on: same provider, same model, TUI, and your last conversation

What it remembers:

Provider (-p) and TUI on/off (--tui / --no-tui)
Model: the last one you used, separately for each provider. Switching back to a provider brings back its model.
Limits: --max-turns and --compact-at
Your conversation: it picks up the last conversation in the current folder, if that conversation used the same provider. The earlier messages are shown again on screen, so you can scroll back and see where you left off

To change something, pass the new option. It applies right away and is remembered from then on:

agentiloop -p omlx        # switch to oMLX (its last-used model comes back too)
agentiloop -m <model>     # switch model
agentiloop --no-tui       # back to the line-by-line chat
agentiloop --new          # start a fresh conversation (the old one stays saved)

Some things are never remembered on purpose:

--yes: skipping permission prompts has to be a deliberate choice every time
--no-mcp, -C and one-shot prompts
API keys: those live in ~/.agentiloop/env (written by the wizard) or your shell environment, never in settings.json

To forget everything, delete ~/.agentiloop/settings.json.

All options

Every option can also be set with an environment variable, shown in the second column. An option you type always beats a remembered value.

Option	Env variable	What it does
`-p, --provider <name>`	`AGENTILOOP_PROVIDER`	`anthropic`, `openai` or `omlx`. If you don't set one, AgentiLoop uses the last one, or detects it from your keys (Anthropic first, then OpenAI, then oMLX)
`-m, --model <id>`	`AGENTILOOP_MODEL`	Which model to use
`--tui` / `--no-tui`	`AGENTILOOP_TUI`	Full-screen interface on / off
`--new`		Start a new conversation instead of continuing
`-c, --continue`		Continue the last conversation here (already the default)
`-r, --resume <id>`		Reopen a specific conversation (find ids with `/sessions`)
`-C, --cwd <folder>`		Work in a different folder than the one you're in
`--yes`	`AGENTILOOP_YES`	Don't ask before running tools. ⚠️ Only for trusted, automated use
`--no-mcp`	`AGENTILOOP_NO_MCP`	Don't start MCP servers (see below)
`--setup`		Run the first-time wizard again (provider, key, model). Combine with `--tui` to run it inside the full-screen interface
`--reset`		Back to brand new: deletes `~/.agentiloop`, the agentiloop block in your shell profile and Keychain items the wizard created (on Windows: the user environment variables it set). Hand-written `export` lines are only commented out, and only if you say yes. Add `--yes` to skip the questions
`--max-turns <n>`		Max steps the agent may take per request (default 50)
`--compact-at <tokens>`	`AGENTILOOP_COMPACT_AT`	When to summarize a long conversation (default 150000, `0` = never)
`-h` / `-V`		Help / version

Some examples:

agentiloop -p openai -m gpt-4o-mini "summarize this repo"    # one question with a specific model
agentiloop -C ../other-repo --tui                            # work on another project
agentiloop --yes "run the tests and fix any failures"        # unattended, no prompts

Which model is used? The first one that applies wins:

-m on the command line
the model of the conversation you're continuing
the last model you used with this provider
the provider's default: claude-sonnet-5 for Anthropic, gpt-4o-mini for OpenAI, or the first model oMLX offers

Commands inside the chat

Type these at the prompt, in the TUI or the chat:

Command	What it does
`/model`	Show available models. `/model 3` or `/model <id>` switches (and is remembered)
`/sessions`	List your saved conversations, newest first
`/resume <n or id>`	Reopen one of them
`/clear`	Clear the conversation and start a new one
`/compact`	Summarize the conversation now to free up space
`/mcp`	Show connected MCP servers and their tools
`/setup`	Run the setup wizard again (works in the TUI too). A new key or provider takes effect after a restart
`/help`	List these commands
`/exit`	Quit

Long conversations

Models can only read so much at once. When a conversation gets big (by default, when a request reaches 150,000 tokens), AgentiLoop asks the model to summarize it so far and carries on from the summary. You'll see a 📦 note when that happens. /compact does it on demand, and --compact-at 0 turns it off.

Adding tools with MCP (optional)

MCP servers give the agent extra tools, like database access, web search or your own scripts. List them in a JSON file:

~/.agentiloop/mcp.json: available in every project
.mcp.json in a project folder: only in that project. If a name appears in both files, this one wins.

The format is the same one Claude Code, Claude Desktop and Agent! use, so you can copy existing configs:

{ "mcpServers": {
    "Local":  { "command": "my-mcp-server", "args": ["--flag"], "env": { "API_KEY": "${MY_KEY}" } },
    "Remote": { "url": "https://example.com/mcp", "headers": { "Authorization": "Bearer ${TOKEN}" } }
} }

How it works:

Two kinds of server. A server with a command is a local program that AgentiLoop starts for you. A server with a url is reached over HTTP. Newer "Streamable HTTP" and older "SSE" servers both work; a URL ending in /sse (or "transport": "sse") selects the older style.
Tool names. Each server tool shows up for the agent as mcp_<server>_<tool>, e.g. mcp_Local_search.
Secrets. ${VAR} (or ${VAR:-default}) is filled in from your environment, so keys don't need to be in the file.
Permissions. MCP tools ask permission like any other tool, unless the server marks a tool as read-only.
Turning servers off. Add "disabled": true to skip one server, or run with --no-mcp to skip them all.
Safety. Plain http:// is only allowed for localhost; remote servers need https://.

Type /mcp to see which servers connected, their tools, and any errors.

Where things are saved

Everything lives in ~/.agentiloop/. Set AGENTILOOP_HOME to use a different folder, e.g. a separate test profile.

File	What's in it
`settings.json`	Remembered provider, models and options, plus what the wizard wrote elsewhere
`env`	Your key, written by the wizard (`KEY=value`, file mode 600). Loaded at startup; an `export` in your shell wins over it
`sessions/`	Your conversations, one file each
`mcp.json`	Your MCP servers
`history.txt`	Prompts you've typed (for ↑ / ↓)

Other environment variables

You'll rarely need these:

Variable	Use
`ANTHROPIC_BASE_URL`	Send Anthropic requests to a proxy or compatible server
`ANTHROPIC_OAUTH_TOKEN`	Alternative to `ANTHROPIC_API_KEY` for a Claude Code token
`OMLX_BASE_URL`, `OMLX_PORT`, `OMLX_API_KEY`	oMLX server address and key. They override `~/.omlx/settings.json`, which is read by default (port 8000 if neither is set)
`AGENTILOOP_LOG=debug` (or `RUST_LOG=debug`)	Show debug logs, including token usage per request

For developers

Build and test

go build -o agentiloop ./cmd/agentiloop   # → ./agentiloop
go test ./...                             # runs offline, no API keys needed

Cross-compiling needs nothing extra, for example GOOS=windows GOARCH=amd64 go build ./cmd/agentiloop.

The tests don't touch the network. The agent loop runs against a scripted fake model, and the streaming parsers against a local test server. The TUI is drawn on tcell's simulated screen. The MCP client is tested against a bundled example server over all three connection types (stdio, HTTP, SSE). You can run that server yourself to try MCP by hand:

go run ./examples/mcp-example-server --http 8791   # or --sse 8792, or --stdio

How the code is organized

The project is split into five packages, and each one builds on the ones before it:

Package	What's in it
`core`	The heart: the agent loop, messages, the tool and provider interfaces, permissions, sessions, summarizing
`provider`	Talks to the models: Anthropic, OpenAI-compatible servers, oMLX
`tools`	Built-in tools: `read_file`, `write_file`, `edit_file`, `list_dir`, `bash`
`mcp`	The MCP client, ported from Agent!'s Swift AgentMCP
`cmd/agentiloop`	The `agentiloop` program: options, chat, TUI, settings

core, provider, tools and mcp use only the Go standard library, so they can be embedded in other programs.

Dependencies

Everything that isn't the TUI or the command line is standard library. The agentiloop program adds:

Module	Used for
`github.com/spf13/pflag`	Command-line options
`github.com/peterh/liner`	The line-by-line chat
`github.com/gdamore/tcell/v2`, `github.com/mattn/go-runewidth`	The TUI
`github.com/yuin/goldmark`, `github.com/alecthomas/chroma/v2`	Markdown and code highlighting

Roadmap

The AgentiLoop Agent! family

AgentiLoopGo is the terminal sibling of AgentiLoop Agent!, the native AI agent for Mac (macOS 14.6+, Apple Silicon and Intel). Its twin, AgentiLoopCLI, has the exact same capabilities, written in Rust.

🖥 Mac app: AgentiLoop/Agent · brew install --cask agentiloop-agent
🦀 Rust CLI: AgentiLoopCLI · 🐹 Go CLI: AgentiLoopGo
🧩 Swift packages behind the Mac app: AgentTools · AgentLLM · AgentMCP · AgentAccess · AgentEventBridges · AgentScripts · AgentD1F · AgentSwift · AgentColorSyntax · AgentTerminalNeo · AgentAudit
🌐 Website: agentiloop.ai

License

PolyForm Noncommercial 1.0.0. You may use, change and share this software for personal and noncommercial purposes. Commercial use, including building or selling commercial versions, is reserved to AgentiLoop. Contact AgentiLoop for a commercial license.

Name		Name	Last commit message	Last commit date
.github		.github
cmd/agentiloop		cmd/agentiloop
core		core
docs		docs
examples/mcp-example-server		examples/mcp-example-server
mcp		mcp
provider		provider
scripts		scripts
tools		tools
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
README_de.md		README_de.md
README_es.md		README_es.md
README_fr.md		README_fr.md
README_ja.md		README_ja.md
README_ko.md		README_ko.md
README_ru.md		README_ru.md
README_zh.md		README_zh.md
agentiloop.txt		agentiloop.txt
go.mod		go.mod
go.sum		go.sum

Navigation Menu

Uh oh!

Repository files navigation

AgentiLoopGo

🎉 We just shipped release v0.0.4 for Mac, Windows and Linux!

💖 Sponsor AgentiLoop

🚀 New here? Up and running in 5 minutes

1. Download AgentiLoop

2. Get an API key

3. Run the setup wizard

4. Check that it works

5. Your first session

What can it do? (tools)

The help command

Stuck? Quick fixes

Quick start

Step 1: Install

Step 2: Connect a model

Step 3: Run it

Three ways to use it

It remembers your setup

All options

Commands inside the chat

Long conversations

Adding tools with MCP (optional)

Where things are saved

Other environment variables

For developers

Build and test

How the code is organized

Dependencies

Roadmap

The AgentiLoop Agent! family

License

About

Releases

Sponsor this project

Packages

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

AgentiLoopGo

🎉 We just shipped release v0.0.4 for Mac, Windows and Linux!

💖 Sponsor AgentiLoop

🚀 New here? Up and running in 5 minutes

1. Download AgentiLoop

2. Get an API key

3. Run the setup wizard

4. Check that it works

5. Your first session

What can it do? (tools)

The help command

Stuck? Quick fixes

Quick start

Step 1: Install

Step 2: Connect a model

Step 3: Run it

Three ways to use it

It remembers your setup

All options

Commands inside the chat

Long conversations

Adding tools with MCP (optional)

Where things are saved

Other environment variables

For developers

Build and test

How the code is organized

Dependencies

Roadmap

The AgentiLoop Agent! family

License

About

Topics

Resources

Stars

Watchers

Forks

Releases

Sponsor this project

Packages

Contributors

Languages