Ficus
A workspace for teams of AI agents.
Give a squad a goal. Its manager coordinates specialized agents, tracks work,
and brings you in for decisions and review. Follow the conversation, steer a
running agent, or let the squad continue while you're away.
Run Ficus on your own machine or server, or use Ficus Cloud.
Your squads can work across repositories, tools, and services from the web app
or CLI.
Documentation · Quick start · Self-hosting · Contributing
Quick start
Install and run Ficus locally on macOS or Linux:
curl -fsSL https://ficus.sh/cli/setup.sh | bash
You'll need curl and git. Bun's installer needs unzip too; on Debian/Ubuntu with passwordless sudo the installer adds it for you, elsewhere install it first.
Setup installs the remaining dependencies, asks
where agents should run, and starts your instance.
- Open the URL printed by setup and complete the first-admin sign-in.
- Connect a model provider under Settings → AI Providers.
- Create a squad and give it a goal.
See the setup guide for requirements, runtime
choices, headless installation, and troubleshooting. Prefer managed hosting?
Get started with Ficus Cloud.
From source
git clone --recurse-submodules https://github.com/ficushq/ficus.git
cd ficus
bun install
bun run setup
CLI only, for an instance running elsewhere:
curl -fsSL https://ficus.sh/cli/install.sh | bash
The CLI is installed to ~/.ficus/bin. See CLI setup
for authentication and usage.
Operate Ficus from an AI coding agent: the CLI bundles the
Ficus operator skill. Install it for your agent with
ficus skill install ficus --agent claude-code --global # or --agent pi | codex
What you can do
- Delegate ongoing work. Squads organize tasks into work streams with
dependencies, handoffs, and review. Schedules keep recurring work moving.
- Stay involved when it matters. Live conversations, an Action Center, and
notifications let you answer questions, review results, and steer active work.
- Choose models and execution environments. Connect model providers and run
agents locally, in Docker, on VM hosts, or in Kubernetes. Choose the isolation
and infrastructure that fit your workload.
- Keep shared knowledge. Squads retain file-based memory with keyword and
vector search, so useful context survives individual conversations.
- Connect your tools. Work with GitHub, Linear, chat channels, browser tools,
webhooks, and app previews. The CLI and REST API support scripted workflows.
- Collaborate across people and instances. Multi-user permissions control
access; AMTP connects agents across Ficus instances and other compatible nodes.
Explore the user guides or the
technical documentation for the full feature set.
Run it your way
| Run Ficus | Best for |
|---|
| Local | Run on your computer and use the web app or CLI. Local setup |
| Self-hosted | Deploy on your own infrastructure and choose where agent workloads run. Hosting guide |
| Ficus Cloud | Use managed hosting at ficus.sh. |
This repository includes the server, worker, web app, CLI, sandbox runtimes,
and shared client libraries. Instance documentation is also available at
/docs/ on your Ficus server.
Developing Ficus
Ficus is built with Bun, TypeScript, Hono, and React. The API and worker run as
separate processes; agents use the same CLI and APIs available to people.
Contributing
Read CONTRIBUTING.md and AGENTS.md before opening
a pull request. The CLA Check guides contributors through the
Contributor License Agreement signing process.
License
Ficus is licensed under AGPL-3.0-only. Contributors retain their
copyright; the CLA grants Intentional Design LLC permission to offer
contributions under additional licenses, including commercial licenses.
Copyright (C) 2026 Intentional Design LLC
