robit

robit (robo it) is an LLM-powered AI automation agent framework. It provides an extensible agent runtime, terminal UI, desktop GUI, unified multi-provider LLM API, and configurable tool and skill systems.

This repository is a Rust monorepo focused on personal automation, programming assistance, and multi-frontend agent experiments.

Features

• Unified LLM configuration: Connect to OpenAI-compatible providers such as DeepSeek and QWen.
• Agent runtime: Event-driven loop with streaming output, tool calls, user confirmation, and progressive context management (output truncation → segmented history compression with merge and bounded discard → LLM summary generation).
• Terminal frontend: The robit TUI is built with ratatui and crossterm, and supports Windows, Linux, and macOS.
• Desktop GUI: robit-gui is built with Tauri v2 and React for a native desktop experience.
• Multi-session Bot framework: robit-chatbot provides platform-agnostic Bot infrastructure with independent Agent sessions per chat.
• QQ Bot frontend: robit-qq implements QQ Official Bot integration (WebSocket gateway + HTTP messaging), supporting both group and private chats.
• Tool system: Built-in tools include read, bash, write, edit, grep, find, and ls; tools can be enabled or disabled through configuration.
• Skill system: Load predefined prompt templates from Markdown/YAML files and trigger them with slash commands.
• Project/global configuration: Project-local .robit/config.toml can override the global ~/.robit/config.toml.

Repository Layout

crates/
  robit-ai       # Multi-provider LLM API and configuration loading
  robit-agent    # Agent runtime, tool system, skill system, Frontend trait
  robit-tui      # Terminal frontend; crate/package name and binary command are robit
  robit-gui      # Desktop GUI frontend (Tauri v2 + React)
  robit-chatbot  # Multi-session Bot infrastructure (PlatformAdapter trait, ChatbotManager)
  robit-qq       # QQ Official Bot frontend (WebSocket + HTTP API), binary command robit-qq
examples/
  robit-chat     # REPL for validating the LLM API layer
  robit-agent    # stdin/stdout frontend for validating the agent runtime
docs/            # Architecture, protocol, roadmap, and implementation plans

Installation and Usage

Prerequisites

• Rust stable toolchain
• For robit-gui: Node.js, npm, and the Tauri platform prerequisites
• An API key for an OpenAI-compatible model provider, such as DeepSeek or QWen

Clone and Build

git clone https://github.com/leexgone/robit.git
cd robit
cargo check --workspace

Run the Terminal App

cargo run -p robit

Specify a working directory:

cargo run -p robit -- --workdir /path/to/project

Auto-approve tool calls:

cargo run -p robit -- --auto-approve

Install locally from this checkout:

cargo install --path crates/robit-tui
robit

After publishing to crates.io, the intended installation command is cargo install robit.

Run the Desktop GUI

cargo run -p robit-gui

By default, GUI session history is stored at <workdir>/.robit/memory/robit.db. Use global storage when you want all projects to share one session database:

cargo run -p robit-gui -- --global-storage

With global storage enabled, the GUI uses ~/.robit/memory/robit.db.

The GUI frontend builds and loads the React app according to crates/robit-gui/tauri.conf.json.

Run the QQ Bot

cargo run -p robit-qq

Specify a working directory:

cargo run -p robit-qq -- --workdir /path/to/project

Enable global storage:

cargo run -p robit-qq -- --global-storage

robit-qq creates an independent Agent session for each QQ group or private chat, and supports inline tool confirmation (reply "确认"/"同意"/"y"/"yes" or "取消"/"拒绝"/"n"/"no").

Configuration

robit uses a unified config.toml file. The lookup order is:

1. workdir/.robit/config.toml or .robit/config.toml in the current directory
2. ~/.robit/config.toml

API keys support ${ENV_VAR} substitution. robit also attempts to load ~/.robit/.env automatically.

toml note: top-level keys such as default_model and default_image_model must appear before any [section] (e.g. [providers.*], [app]). Placing a top-level key after a [[providers.*.models]] array entry silently attaches it to that model instead of the root, and it will be ignored.

Minimal configuration example:

default_model = "deepseek/deepseek-chat"
# default_image_model = "wanxiang/wan2.7-image"  # optional, top-level, enables generate_image

[providers.deepseek]
name = "DeepSeek"
base_url = "https://api.deepseek.com/v1"
api_key = "${DEEPSEEK_API_KEY}"

[[providers.deepseek.models]]
id = "deepseek-chat"
name = "DeepSeek Chat"
context_window = 65536
max_tokens = 4096
temperature = 0.0
supports_tools = true

[app]
log_level = "INFO"
max_steps = 10
enabled_tools = ["read", "bash", "edit", "write", "grep", "find", "ls"]
auto_approve = false
global_storage = false  # true stores GUI sessions in ~/.robit/memory/robit.db

[app.context]
max_output_lines = 500
max_output_bytes = 51200
reserve_ratio = 0.2
truncation_ratio = 0.7
min_keep_rounds = 3
token_safety_margin = 1.3
compression_enabled = true
compression_token_threshold = 5000
max_tool_calls_per_turn = 30

# Image generation providers (optional, used by the generate_image tool)
# [image_providers.wanxiang]
# name = "通义万相"
# base_url = "https://dashscope.aliyuncs.com/api/v1"
# api_key = "${DASHSCOPE_API_KEY}"
# protocol = "dashscope"   # dashscope | openai
# mode = "async"           # sync | async (dashscope only)
#
# [[image_providers.wanxiang.models]]
# id = "wan2.7-image"
# name = "万相2.7"

# QQ Bot configuration (required when using robit-qq)
[channels.qq_bot]
app_id = "your-app-id"
app_secret = "${QQ_BOT_SECRET}"

# Bot platform shared configuration (optional)
[app.bot]
auto_approve = false
confirm_timeout_secs = 60
session_timeout_minutes = 30

[app.bot.confirm_keywords]
approve = ["确认", "同意", "yes", "y", "approve", "ok", "允许"]
reject = ["取消", "拒绝", "no", "n", "reject", "cancel", "deny"]

Store secrets in ~/.robit/.env:

DEEPSEEK_API_KEY=your-api-key

TUI Commands and Shortcuts

After starting robit, enter natural-language tasks directly or use slash commands:

Keyboard shortcuts:

• Enter: send message
• Tab: toggle single-line/multi-line input
• Ctrl+J: send message in multi-line mode
• Ctrl+C: cancel the current task while the agent is busy
• Ctrl+D: exit the application
• F8: toggle scroll mode
• Y / N: approve or reject a tool call that requires confirmation

Tool System

Built-in tools:

read, load_skill, query_task, and the memory/history tools are always registered. Other tools can be controlled through [app].enabled_tools. generate_image requires image_providers + default_image_model configuration.

Skill System

Skills are prompt templates stored as Markdown/YAML files. They can be placed in:

~/.robit/skills/
.robit/skills/

Use /skills in the TUI to inspect loaded skills. See docs/architecture.md for the skill file format and registration mechanism.

Releases

Pre-built binaries are available on GitHub Releases. Each release includes CLI and GUI packages for Linux, macOS, and Windows.

CLI (Terminal)

GUI (Desktop)

From Source

• robit-ai and robit-agent: suitable for crates.io as Rust library crates.
• robit (TUI): install with cargo install robit.
• robit-gui: better distributed through GitHub Releases, a website, Homebrew Cask, Winget, Scoop, AppImage, deb/rpm, dmg/msi, or similar desktop distribution channels.

Documentation

• docs/architecture.md: agent runtime, Frontend trait, tool system, skill system, and context management
• docs/protocol.md: message structures and agent events
• docs/roadmap.md: project roadmap
• docs/plans/phase2-implementation.md: agent runtime implementation plan
• docs/superpowers/specs/2026-06-18-robit-chatbot-qq-design.md: robit-chatbot & robit-qq design specification
• docs/superpowers/2026-06-11-robit-gui-progress.md: GUI development progress

Project Status

robit is in early development. The core LLM API, agent runtime, and TUI frontend are already usable at a basic level; the GUI frontend is still being iterated on. APIs, configuration format, and release strategy may change before a stable release.

License

This project is licensed under the Apache License 2.0.

Apache-2.0 allows use, copy, modification, and distribution, including commercial use. When redistributing, preserve the copyright notice and license text, and comply with the patent grant, NOTICE, and other terms of the license.