Magi banner
BolivarTech BolivarTech

Magi

AI community

Description

Magi Agent — terminal AI assistant in Rust

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Magi Agent — Terminal AI Assistant in Rust

[![Rust 2021](https://img.shields.io/badge/rust-2021_edition-orange.svg)](https://www.rust-lang.org/) [![CI](https://github.com/BolivarTech/magi/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/BolivarTech/magi/actions/workflows/ci.yml) [![Lints](https://img.shields.io/badge/lints-clippy%20clean-blue.svg)](https://github.com/rust-lang/rust-clippy) [![License](https://img.shields.io/badge/license-MIT%20OR%20Apache--2.0-blue.svg)](#license) [![crates.io](https://img.shields.io/crates/v/magi-rs.svg?label=version)](https://crates.io/crates/magi-rs)

**Magi Agent** (`magi-rs`) is a terminal AI assistant in Rust, modeled on Claude Code. It drives an LLM provider through a multi-turn **tool loop** with sandboxed filesystem and shell access, and persists every conversation to a **locally-encrypted SQLite store**. Nothing leaves your machine except the model API calls you explicitly authorize.


Why Magi?

Most AI coding agents are SaaS-bound and tied to a single vendor. Magi is built for the opposite constraint: **environments where source code cannot leave the machine.**

Principle What it means in Magi
Local-first A single static Rust binary. Conversation history and project knowledge live in an encrypted SQLite file on disk, never a third-party vault.
Encrypted at rest Every stored record is sealed with AES-256-GCM-SIV + error-correcting FEC under a random data key, itself wrapped by an Argon2id-derived key, via the audited `cryptovault` crate. The data key is unlocked by a user passphrase (zero-knowledge: nothing persisted opens the DB without it), and a wrong passphrase never wipes the DB.
Sandboxed by default Every filesystem tool is confined to the workspace via PathGuard; the shell tool runs a strict command allowlist with a hard ban on shell metacharacters.
**Human-in-the-lo