Install gptme with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• gptme
• gptme-dspy
• gptme-eval
• gptme-nc
• gptme-server
• gptme-util
• gptme-wut

Project history

The official repository describes gptme as an agent in the terminal, equipped with local tools to write code, use the terminal, and browse the web. The project site positions it as a small, simple assistant rather than a platform trying to cover every workflow.

The documentation and release pages show a project organized around CLI usage, tools, prompts, configuration files, local logs, project workspaces, plugins, RAG/context features, and autonomous agent patterns.

The release documentation records a long sequence of tagged versions. By v0.8.1, release notes already included auto-continue/recovery after tool execution, project-context work, web UI conversation creation, command-output capture, and integration-test improvements.

Adoption history

gptme belongs to the package-manager wave of LLM developer tools that moved from simple chat wrappers toward local agent workflows. Its Homebrew package exposes several executables, reflecting a broader tool suite rather than a single chat binary.

The project's adoption signal is strongest among developers who want a terminal-native assistant with reproducible logs, configurable model/provider settings, and explicit local tool use.

How it is used

Users run `gptme` as an interactive terminal assistant and configure user preferences in `~/.config/gptme/config.toml`. Secrets and local overrides can live in `~/.config/gptme/config.local.toml`, and project-specific behavior can be configured with `gptme.toml` in a workspace root.

The docs cover CLI subcommands, prompt/context handling, tool execution, project config, MCP server configuration, plugin settings, chat logs, and agent-oriented workflows.

The package also installs helper commands such as `gptme-server`, `gptme-util`, and evaluation or integration utilities, making it more of a local developer-assistant toolkit than a plain chat command.

Why package nerds care

gptme is significant for package nerds because it packages an AI agent as a normal terminal tool with config files, subcommands, logs, plugins, and optional integrations instead of hiding everything behind a hosted UI.

Its config split between committed preferences and local secret overrides is also packaging-relevant: it gives dotfile users a predictable Unix-style setup while leaving room for provider keys and MCP credentials.

Timeline

• 2020s: gptme develops as a terminal AI assistant and local agent toolkit.
• 2024: Public project discussion includes config.toml documentation needs.
• 2026: Official documentation lists release pages back through early v0.x versions.
• 2026: Release notes for v0.8.1 document agent/tooling features such as auto-continue after code execution and project-context work.

Related projects

• OpenAI, Anthropic, llama.cpp, OpenRouter, MCP servers, RAG tools, and local shell/file/browser tooling are all part of gptme's documented integration space.
• gptme-contrib provides related scripts, plugins, lessons, and integration examples around the core project.

Sources

• https://github.com/gptme/gptme
• https://gptme.org/docs
• https://gptme.org/docs/arewetiny.html
• https://gptme.org/docs/cli.html
• https://gptme.org/docs/config.html
• https://gptme.org/docs/releases/v0.8.1.html
• https://gptme.org/docs/tools.html