
Filo, run many Claude Code and Codex agents in one chat
Filo is a native macOS app where you make agents, each with a name, a picture and instructions of its own, and talk with
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
Filo is a native macOS app where you make agents, each with a name, a picture and instructions of its own, and talk with them one at a time or all together in a group chat. The answers come from a coding tool you already use, Claude Code, Codex, Muse Code or OpenCode, running on your Mac under your own account. Filo has no account of its own, and your conversations, notes and agents stay in a folder on your Mac.
Built with GPUI, the UI framework behind the Zed editor, and gpui-component.
macOS 13 (Ventura) or later, on Apple silicon or Intel. Computer use (an agent working in your other apps) needs macOS 14.
Rust 1.90 or later. Install it with rustup.
Xcode or the Xcode Command Line Tools (xcode-select --install), with Swift 6.1 or later: scripts/app.sh builds the computer use helper (computer-use/) with swift build. You don't need Xcode's Metal toolchain, as debug builds compile GPUI's shaders when the app starts.
At least one coding tool, installed and signed in: Claude Code (claude), Codex (codex), Muse Code (muse) or OpenCode (opencode). Filo finds them on your login shell's PATH, and in ~/.local/bin, ~/.claude/local, ~/.opencode/bin, ~/.npm-global/bin, ~/.bun/bin, /opt/homebrew/bin and /usr/local/bin.
A first build downloads and compiles about 600 crates. Leave it about 20 GB of free disk space for target/.
git clone https://github.com/bitooz/filo-desktop.git cd filo-desktop scripts/app.sh # builds target/debug/Filo.app, signs it and opens it scripts/app.sh --release # the same, optimised (use this one to judge speed)
Run Filo through scripts/app.sh instead of plain cargo run. macOS asks for the microphone and shows notifications only for an app bundle: run straight from a terminal, the binary counts as part of the terminal app. The script signs the bundle with your Mac's "Developer ID Application" or "Apple Development" certificate if it has one (SIGN_IDENTITY=<name> picks another). Without one it signs ad hoc, which runs fine but gets no notifications. FILO_LOG=<file> collects the app's output.
cargo run still works for a quick look. So do the tests:
cargo test -p filo-local # chat storage, the database, the MCP server and the coding tools' runner (no GPUI) cargo test --bin filo # the app's own tests
To build a release bundle and disk image as they're shipped (without the developer modes, the dev feature), see the options at the top of scripts/package.sh:
BUILD=1 scripts/package.sh # dist/Filo.app, a zip and a .dmg
Pull requests are checked with cargo fmt, clippy and the tests; signed releases are built by GitHub Actions (docs/how-it-works.md).
A short welcome tour checks which coding tools are on your Mac and signed in, helps you set one up if none is, and makes your first agent. Nothing is asked for at launch: macOS asks for the microphone the first time you record a voice message, and for notifications the first time Filo has one to show. Settings › Welcome tour shows the tour again.
Everything Filo keeps is under ~/.config/filo/local: a SQLite database (filo.db) with your agents, notes, reminders, artifacts and the rest, the conversations' files, and the last three daily backups of the database. Keys for apps you connect go in your login Keychain. Set FILO_CONFIG_DIR=<folder> to run Filo on another folder, for example a throwaway one while you try a change.
A few features use Filo's own servers, and only when you use them:
The release builds also send anonymous usage counts (docs/telemetry.md) and check for updates. A build from source does neither unless it's given a PostHog key and an update feed at build time.
src/: the app. main.rs starts it, app.rs and nav.rs hold the sidebar and the pages, screens/ has one module per page, and local_backend.rs answers every page's calls from the data on your Mac.
crates/filo-local: everything with no UI. Chat storage and the database, Filo's MCP server (the tools agents get), and the runner that drives Claude Code, Codex, Muse Code and OpenCode. It builds and tests on its own.
crates/filo-resample: draws a zoomed-in picture sharp, at the screen's pixels.
computer-use/: the Swift helper behind computer use.
vendor/gpui, vendor/gpui-component: our copies of gpui 0.2.2 and gpui-component 0.5.1 with Filo's fixes. Each FILO.md lists what changed and why.
assets/: icons, fonts, pictures and the colour themes. web/: the note editor and other pages shown in web views.
docs/how-it-works.md explains each part in detail: the database, the group chat, coding, artifacts, apps, scheduled work and the command-line checks.
Licence
Filo's own code is released under the MIT licence. The third-party code, fonts and pictures it includes keep their own licences, listed in THIRD_PARTY_NOTICES.md.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。