9. Configuration

Most configuration lives in Tools → Options → Aefos. This page summarizes the options and the files involved.

Tools → Options → Aefos

Option What it does
Provider / executor Chooses the AI CLI (Claude / Codex / Copilot / Gemini)
Model Chooses the provider's model (remembered per provider)
Terminal session Name of the MCP session used by the Terminal (default: plugin)
Test MCP Checks whether the selected CLI sees the aefos server

Test MCP

The Test MCP action is executor-aware: for Claude it expects the word "connected"; for the others it treats the aefos server appearing in the CLI's listing as "configured". Use it whenever you switch providers or suspect MCP is not connected.

MCP configuration (advanced)

Aefos self-provisions; you generally do not need to edit anything by hand. For reference:

File Purpose
%APPDATA%\Aefos\aefos-mcp.json Global MCP configuration — the built-in aefos server + your extra servers. All CLIs point to this file
%APPDATA%\Aefos\mcp-bridge.ps1 Bridge (stdio ↔ named pipe) for CLIs that connect over the pipe
.mcp.json (in the project root) Per-project MCP config, generated by the install for the Terminal

Important: the .mcp.json is per-machine — do not commit it to your repository.

Extra MCP servers

If you use other MCP servers, you can add them via the "MCP Servers" modal — they are merged into the global configuration and become available to all CLIs.

WebView2 (rich Markdown in the Chat)

For the Chat to show formatted Markdown (with syntax highlighting), install the WebView2 Runtime: https://aka.ms/webview2. Without it, the Chat uses plain-text mode.

PyTools (Python tools)

PyTools let you extend the agent with tools written in Python:

  1. Create a folder for your tool inside %APPDATA%\Aefos\pytools.
  2. Add a tool.json (description) and a main.py (the logic).
  3. The tool then appears as a live MCP tool for the agent.

PyTools need a Python interpreter installed to run (Aefos does not bundle Python). See Requirements.

➡️ Next: Licensing & editions