Troubleshooting
Diagnose and fix common RedCell problems.
Start with doctor
redcell doctorIt checks your install, config, sign-in, and connection to RedCell, and tells you what's wrong.
| Flag | What it does |
|---|---|
--summary | Show only grouped results and the final count |
--all | Expand long lists |
--json | Machine-readable output with secrets removed. Attach this when you ask for help |
Common problems
| Problem | Fix |
|---|---|
redcell: command not found | Open a new terminal. If it still fails, add ~/.local/bin to your PATH. See Install |
| Not signed in, or sign-in expired | Run redcell login. See Sign in |
CLI access: false | Your plan doesn't include CLI access. Compare plans |
| Out of quota | Check redcell usage. Upgrade your plan or wait for the reset |
| RedCell keeps asking for approval | Change your preset with /permissions. See Permissions |
| Network requests are blocked | The sandbox blocks network access by default. Approve the request, or allow network access |
| A plugin's tool isn't working | Run redcell plugin doctor. See Plugins |
| A config change does nothing | Run redcell config show to see what's actually in effect |
| The conversation gets slow or confused | Run /compact, or start fresh with /new |
Get logs
Write a session log to a folder:
redcell -c log_dir=./redcell-logsThen watch it in another terminal:
tail -F ./redcell-logs/redcell-tui.logFor more detail, set RUST_LOG=debug before running RedCell.
Update
Many problems are fixed in newer releases:
redcell updateStill stuck?
Run /feedback in a session to send a report, with logs if you choose, to the RedCell team.