Skip to Content
REDCELLDocs

Troubleshooting

Diagnose and fix common RedCell problems.

Start with doctor

redcell doctor

It checks your install, config, sign-in, and connection to RedCell, and tells you what's wrong.

FlagWhat it does
--summaryShow only grouped results and the final count
--allExpand long lists
--jsonMachine-readable output with secrets removed. Attach this when you ask for help

Common problems

ProblemFix
redcell: command not foundOpen a new terminal. If it still fails, add ~/.local/bin to your PATH. See Install
Not signed in, or sign-in expiredRun redcell login. See Sign in
CLI access: falseYour plan doesn't include CLI access. Compare plans
Out of quotaCheck redcell usage. Upgrade your plan or wait for the reset
RedCell keeps asking for approvalChange your preset with /permissions. See Permissions
Network requests are blockedThe sandbox blocks network access by default. Approve the request, or allow network access
A plugin's tool isn't workingRun redcell plugin doctor. See Plugins
A config change does nothingRun redcell config show to see what's actually in effect
The conversation gets slow or confusedRun /compact, or start fresh with /new

Get logs

Write a session log to a folder:

redcell -c log_dir=./redcell-logs

Then watch it in another terminal:

tail -F ./redcell-logs/redcell-tui.log

For more detail, set RUST_LOG=debug before running RedCell.

Update

Many problems are fixed in newer releases:

redcell update

Still stuck?

Run /feedback in a session to send a report, with logs if you choose, to the RedCell team.