comparison
Lacy Shell vs Amazon Q Developer
Lightweight shell plugin vs AWS-integrated assistant.
The core difference
Amazon Q Developer CLI (the product that absorbed Fig and CodeWhisperer) is an AWS-backed assistant with autocomplete, chat, and inline suggestions. It’s a full platform. Lacy is a single-purpose shell plugin: it detects whether your input is a command or a question and routes it. That’s it.
| Lacy Shell | Amazon Q Developer CLI | |
|---|---|---|
| Type | ZSH/Bash plugin | Desktop app + CLI |
| AI routing | Automatic — detects NL vs commands | Explicit (q chat) |
| Autocomplete | No (use your existing completion) | Yes (command + argument suggestions) |
| AI backend | Your choice (Claude, Gemini, OpenCode, etc.) | Amazon Bedrock |
| AWS integration | None | Deep (IAM, CloudWatch, etc.) |
| Real-time indicator | Yes — green/magenta as you type | No |
| Account required | No | Yes (AWS Builder ID or IAM) |
| Price | Free, MIT licensed | Free tier + paid Pro plan |
| Open source | Yes | Partially |
| Install size | ~100KB (shell scripts) | Desktop app + CLI binary |
Different scopes
Amazon Q is trying to be your full development assistant: autocomplete, chat, code transformation, vulnerability scanning, AWS resource management. It does a lot of things.
Lacy does one thing. It watches what you type, decides if it’s a command or a question, and sends it to the right place. If you already have an AI CLI tool you like, Lacy makes it accessible without changing how you work.
When to use Lacy
- You want a lightweight plugin, not a platform
- You want to pick your own AI backend
- You don’t need AWS integration
- You want automatic NL routing without invoking a separate command
When to use Amazon Q
- You work heavily with AWS services
- You want IDE-style autocomplete in your terminal
- You want an all-in-one assistant with chat, completions, and scanning
- Your team is already on the AWS ecosystem
Can you use both?
They can coexist. Amazon Q’s autocomplete works at a different level than Lacy’s input routing. Lacy handles enter-to-execute classification; Q handles tab-to-complete suggestions. If you want Q’s autocomplete plus Lacy’s NL routing, both can be active.
Further reading
- Why I didn’t use AI to classify AI input — how Lacy decides whether your input is a shell command or natural language, without ML.