u/Status_Support2913

I built a Flutter terminal widget powered by Alacritty's Rust engine — feedback welcome

I built a Flutter terminal widget powered by Alacritty's Rust engine — feedback welcome

👋 I’ve been working on flutter_alacritty — a Flutter terminal widget you can drop into desktop apps, backed by an Alacritty-based Rust engine.

Why I moved away from xterm:

I used xterm for a long time, but kept running into limitations that mattered for my use case:

  • Text rendering — many glyphs/styles didn’t render correctly
  • No OSC hyperlinks — modern CLIs and tools that emit OSC 8 links weren’t supported
  • Resize, scrolling, and high-density output — performance was poor when the terminal was under real load

So I built flutter_alacritty (with AI coding agents helping along the way). It’s what TeamPilot uses today, and it has held up well across multiple agent TUIs rendering at once.

Links:

Real usage: TeamPilot uses it for embedded terminals (local PTY + SSH) in a multi-agent desktop client.

Try it via the standalone demo in the release.

I’d love feedback from anyone embedding terminals in Flutter.

u/Status_Support2913 — 4 days ago

I built a desktop workbench for multi-agent CLI workflows — isolated Alacritty PTY per member, saved team presets, git worktrees

I've been shipping real work with terminal AI agents (Claude Code, etc.). GUI coding assistants (Cursor, Windsurf, VS Code extensions) are great for inline edits — but they don't solve what I kept running into when I wanted multiple agents as a team:

  1. One model for everything — Opus on every typo is $$$; one cheap model can't plan + review well.
  2. "Multi-agent" in IDEs — usually one product, one chat stack. I wanted Claude Code + Codex + cursor-agent in the same workflow, not three disconnected terminal tabs.
  3. Context bleed — multiple agents in one session or sloppy tab switching mixes configs and history.
  4. IDE ↔ terminal ping-pong — git, file tree, diff in the IDE; agents in terminals; copy-paste coordination.
  5. Mixed CLI teams — Claude Code plans, another CLI implements — coordinated via an in-process bus (mailbox/board), not copy-paste
  6. Git worktrees — one branch / one checkout / one agent session — parallel feature work without stepping on each other

So I built TeamPilot — MIT, Flutter desktop (Linux/macOS/Windows) + Android client (SSH to a host with the CLIs). It's not "Cursor but Flutter." It's a team orchestration shell around existing CLI agents.

What IDEs / single-chat agents don't give you

Capability Typical IDE agent TeamPilot
Per-role model tier Global model picker Each member has its own provider + model + effort
Truly parallel agents Subagents, same stack Separate PTY per member — isolated CONFIG_DIR, session ids
Mixed vendors Locked to one agent Mixed team: Claude Code, Codex, opencode, Cursor agent, flashskyai + in-process message bus
Team as a saved preset Roster, prompts, skills/plugins/MCP per team; import templates from Team Hub
MCP/skills once Per-tool manual setup Global library → auto-provisioned into each CLI's config format
Worktree + agents Partial Native git worktree UI; sessions grouped by branch; spawn agent in new worktree

Simple mode still exists (single CLI, no roster) — same per-CLI model maps and presets. Team mode is the point.

https://reddit.com/link/1ucfksj/video/j4pnorrows8h1/player

Links

MIT licensed — feedback and contributors welcome.

reddit.com
u/Status_Support2913 — 14 days ago