# OpenFang

OpenFang — это операционная система с открытым исходным кодом для агентов, созданная на Rust, с возможностью запуска, настройки и контроля автономных агентов. Поддерживает локальное и самостоятельное размещение, встроенные шаблоны, пользовательские манифесты, каналы обмена сообщениями и управление через браузер или API.

- Findings24: <https://findings24.com/ru/tools/openfang>
- Сайт: <https://openfang.sh>
- Цены: Freemium
- Категории: AI DevOps Ассистент, AI Ассистент Кода, AI Инструменты Разработчика

## Что такое OpenFang?

OpenFang is an open-source Agent OS built in Rust for installing, configuring, and operating autonomous agents. The public docs position it as a runtime for hands, agents, tools, security, memory, channels, protocols, and a native desktop app, with a daemon for persistent and multi-user use.

It is aimed at people who want to run agents locally or self-host them, choose an LLM provider, attach messaging channels, and manage workflows from templates or custom manifests. The docs also show support for browser-based chat, API access, MCP, A2A, and a native desktop application.

## Что умеет OpenFang?

### One-binary runtime and desktop app

OpenFang ships as a Rust workspace with a single compiled binary, plus a native desktop app and a daemon for persistent operation.

### Pre-built autonomous Hands

The product includes 7 pre-built autonomous Hands such as Clip, Lead, Collector, Predictor, Researcher, Twitter, and Browser, each meant for a specific workflow.

### Security hardening stack

The docs describe 16 security systems including WASM dual metering, manifest signing, audit trails, taint tracking, SSRF protection, secret zeroization, mutual auth, and prompt-injection scanning.

### Channel, model, and skill integration

OpenFang supports 40 messaging channel adapters, 20 LLM providers, and 60 bundled skills, with additional agent templates and workflow composition.

### Multiple deployment and setup paths

The getting started guide shows installation via shell script, Cargo, or Docker, then configuration through \`config.toml\` and environment variables.

### API and protocol support

The docs expose REST, WebSocket, and SSE endpoints, plus an OpenAI-compatible \`/v1/chat/completions\` API for external integration.

## Варианты использования

### Start with a pre-built agent

Install OpenFang, set an API key, run \`openfang init\`, and spawn a built-in template such as \`hello-world\` to get a working agent running quickly.

### Define custom agents

Create a custom \`agent.toml\` with a chosen provider, model, and capability set when you want an agent tailored to a specific task or workflow.

### Operate agents continuously

Run \`openfang start\` to expose the REST API, WebSocket endpoint, WebChat UI, and persistent daemon behavior for ongoing use.

### Attach external systems

Connect messaging platforms, MCP servers, or A2A integrations when you need agents to interact with external tools and channels.

### Manage agents interactively

Use the native desktop app or browser chat interface when you want a local UI for monitoring running agents, reading responses, and checking token usage.

## Часто задаваемые вопросы

### How do I install OpenFang?

OpenFang’s getting started guide shows three installation paths: a shell installer for Linux and macOS, \`cargo install\` for any platform with Rust 1.75+, and Docker.

### What do I need to configure before running agents?

The docs say OpenFang needs at least one LLM provider API key. It supports environment variables such as \`ANTHROPIC\_API\_KEY\`, \`OPENAI\_API\_KEY\`, and \`GROQ\_API\_KEY\`.

### Can I use OpenFang with built-in templates or custom agents?

The getting started guide shows both built-in agent templates and custom \`agent.toml\` manifests. You can spawn a template agent or define your own model and capability settings.

### What does the daemon add beyond the CLI?

The daemon supports persistent agents, multi-user access, the WebChat UI, REST API, WebSocket access, and token usage visibility in the browser UI.

### What are OpenFang’s main limitations from the public docs?

The architecture and docs pages describe OpenFang as a Rust workspace with sandboxing, security hardening, channel adapters, skills, MCP, and A2A support. The public docs do not provide a complete list of every supported provider or integration detail on the pages used here.

## Краткие сведения

- **Category**: Developer Tool
- **Product type**: Open-source agent operating system
- **Platform**: Linux, macOS, Windows
- **Source domain**: openfang.sh
- **Primary users**: Developers and teams self-hosting agent workflows
- **Deployment**: CLI, daemon, native desktop app, Docker