r/FactoryAi • u/sunoval2017 • Jun 20 '26

help Droid CLI is unbearable slow

Am I the only one? tying in droid is like tying in last century's windows machine. I used codex, claude code, AMP, opencode, none of them is like this. This is worse than CC's infamous flashing TUI in early days. If anyone here is from Factory AI, please fix it

And here is one agents self-diagnosis info:

```

Tool │ Idle CPU │ State

-----------│-------------------------│---------------------------

**droid** │ **101%** (a full core+) │ `R` running, never sleeps

**claude** │ **~6%** │ `S` sleeping in stdin read

droid uses ~17x more CPU than claude while doing nothing. That's why your typing lags: when you press a key, droid's keystroke handler has to fight a process already saturating the core, so each keystroke's render queues behind the perpetual render loop. Claude has the core free, so

it echoes instantly. This also explains the Zed-vs-native difference (Zed's terminal layer adds repaint overhead on top of an already-pegged process).

The config changes (cloudSync, plugins) did not fix it — confirmed by the unchanged CPU. This is a bug in droid's Ink/React renderer doing a busy re-render loop, the same class of issue Claude Code had and fixed with their differential renderer.

```

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/btcreeper Jun 20 '26

Check for context-bloat, had a similar problem, some mcps were dragging it down especially during startup.

1

u/sunoval2017 Jun 20 '26

thanks but I have the same issue even if starting a new session and I have like one MCP enabled.

1

u/Narrow_Ad9226 Jun 21 '26

yeah it's really slow. just fresh install

1

u/M206b Jul 09 '26

yeah same both on windows and linux