llama-agentic
A local agentic AI CLI powered by llama.cpp. It runs on your machine, uses GGUF models, and exposes tools for files, shell commands, git, web access, memory, plugins, MCP servers, and A2A agents.
Think of it as a terminal coding agent driven by your local model instead of a hosted API.
You: Refactor the auth module to use JWT, run the tests, and commit
Agent: ⚙ view_file ✓ Read agent/auth.py
⚙ edit_file ✓ Applied JWT changes
⚙ run_shell ✓ pytest tests/test_auth.py
⚙ git_commit ✓ refactor: replace session auth with JWT
Done — all tests pass and changes are committed.
What it does
- Runs a ReAct loop: reason, choose a tool, observe results, repeat
- Works with local llama.cpp models through the OpenAI-compatible server API
- Includes built-in tools for files, editing, shell, Python, git, web, and memory
- Supports MCP servers so you can add GitHub, databases, browsers, Slack, and more
- Supports A2A agents so your local agent can delegate to remote JSON-RPC A2A agents
- Loads LLAMA.md automatically for project-specific context
- Supports persistent memory, session save/load, watch mode, and plugin loading
Documentation
The repo docs are the primary guide set:
| Guide | Description |
|---|---|
| Documentation Index | Overview of all guides |
| Getting Started | Install, setup, download a model, first run |
| User Guide | REPL usage, sessions, memory, watch mode |
| Tools Reference | Built-in tools and examples |
| Configuration | Environment variables and config hierarchy |
| Plugin Development | Add custom tools |
| MCP Integration | Configure and use MCP servers |
Requirements
| Requirement | Version | Install |
|---|---|---|
| macOS or Linux | macOS 12+ / Ubuntu 22+ | — |
| Python | 3.11+ | python.org |
| llama.cpp | latest | brew install llama.cpp |
| uv | latest | curl -LsSf https://astral.sh/uv/install.sh | sh |
Apple Silicon works well with Metal GPU offload by default.
Installation
From PyPI
pip install llama-agentic
# or
uv tool install llama-agentic
From source
git clone https://github.com/minrahim1999/llama-agentic.git
cd llama-agentic
uv tool install --editable .
Verify
llama-agent --help
Quick Start
1. Run first-time setup
llama-agent
This creates ~/.config/llama-agentic/config.env and can help detect llama-server, choose settings, and offer a starter model download.
It also saves a preferred LLAMA_MODEL_PATH so auto-start uses a deterministic GGUF file instead of guessing from the cache.
2. Download a model
llama-agent download
llama-agent download qwen2.5-coder-7b
Downloaded models are added to the cache and the selected file is persisted to LLAMA_MODEL_PATH automatically.
Recommended model:
llama-agent download qwen2.5-coder-7b
3. Start or verify the server
llama-agent doctor
llama-agent autostart enable
llama-agent autostart start
autostart enable and autostart start prefer the configured LLAMA_MODEL_PATH when it is set.
Or start it manually:
./scripts/start_server.sh /path/to/model.gguf
4. Generate project context
cd your-project
llama-agent --init
5. Start a session
llama-agent
llama-agent --task "Find and fix the failing tests"
Common Commands
llama-agent # interactive REPL
llama-agent --task "review the latest changes" # one-shot task
llama-agent --resume sessions/chat_2026-01-15.json
llama-agent doctor # environment checks
llama-agent download qwen2.5-coder-7b # download a model
llama-agent models # list cached models and the selected one
llama-agent mcp list # list configured MCP servers
llama-agent a2a list # list configured A2A agents
Common REPL commands:
/help/init/refresh/add <glob>/tools/memory/sessions/cost/exit
See docs/user-guide.md for the full command list.
Key Features
- Diff-aware editing:
edit_filepreviews changes before writing and keeps.bakbackups - Confirmation-gated actions: destructive tools require approval unless
UNSAFE_MODE=true - Persistent memory: store facts across sessions
- Session management: save, load, resume, and inspect history
- MCP integration: dynamically register tools from external MCP servers over the currently supported transports
- A2A integration: register remote A2A agents as callable tools and inspect their Agent Cards
- Plugin system: load custom tools from configured plugin directories
.llamaignoresupport: block reads and writes to protected paths
Development
uv sync --dev
uv run pytest tests/ -v --tb=short
uv run ruff check agent/ tests/
uv build
Project layout and development conventions are documented in AGENTS.md.
License
MIT. See LICENSE.
Release files for llama-agentic 0.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| llama_agentic-0.3.4.tar.gz | 220.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llama_agentic-0.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 310.6 kB
Release files / llama_agentic-0.3.4.tar.gz
| Download URL | llama_agentic-0.3.4.tar.gz |
|---|---|
| Size | 220.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff8b4fec52f7c9b0e9d0287618abc6da8e81aefddd97778f286ef109f221563b
|
|
BLAKE2b-256 checksum How to use checksums |
d40b2392e02222ed4063e4714105ef576fec99ecdd6522c542ef0fca155d0915
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 26, 2026.
Transparency logRelease files / llama_agentic-0.3.4-py3-none-any.whl
| Download URL | llama_agentic-0.3.4-py3-none-any.whl |
|---|---|
| Size | 90.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
12f6b6a5b2c47fe49868cbc7959d0205dc062e78d83b971a3590d9e4e38bc6cb
|
|
BLAKE2b-256 checksum How to use checksums |
7ba9be396ede1056162b21607dd68850ee38900c6600f9d109b0c4bb87eba4cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 26, 2026.
Transparency log