Reference
Feedback and bug reports
Report a bug, an idea or a question with cloudex feedback, from your computer or inside a sandbox, and what a report holds. Security problems go to private reporting.
cloudex feedback "fork is slow on a 15 GB sandbox"
cloudex feedback --last-error "this happened while deploying"
cat notes.md | cloudex feedback -
cloudex feedback sends a report to the Cloudex maintainers as a public issue on github.com/lucataco/cloudex. With --last-error, it includes the last command that failed on this computer and its error. When a command fails because of a problem on the deployment’s side, or the CLI crashes, it suggests this. Flags go before the message; a message of - is read from standard input.
What a report holds
- your message;
- with
--last-error, the failed command, as its name and flag names only (cloudex new --name … --size standard-4), its error, and a stack trace if the CLI itself crashed; - the CLI’s version and your OS, the deployment’s version, and whether preview links and backups are on.
Before anything is sent, Cloudex removes the deployment’s admin key, API URL and host, your account id and preview domain, the tokens in preview links, the sandbox names it knows of, what the failed command was given, your home directory, email addresses, public IP addresses, private keys, and anything that looks like a key, token or password. A sandbox name in your own message stays if it’s an ordinary word, such as web, so read the report before you send it.
How it’s sent
In a terminal, it prints the report, says how it would be sent, and asks first. If the GitHub CLI (gh) is installed and signed in, the issue is filed under that GitHub account, which the question names. Otherwise GitHub’s new-issue page opens with the report filled in, for you to read once more and submit. --web always uses the page.
| Flag | Effect |
|---|---|
--last-error |
Include the last failed command and its error |
--send <id> |
Send the report saved with that id, exactly as it was shown |
--yes, -y |
Send without asking; the report is printed as it goes |
--web |
Open GitHub’s new-issue page instead of filing with gh |
From agents
Without a terminal, as when an agent runs it, or with a piped message, nothing is sent: cloudex feedback prints the report (as JSON with --json), says how it would go, and saves it with an id. The agent should show you the report and, once you agree, run cloudex feedback --send <id>. That sends exactly that report, the way it said: if it was to go with gh as one GitHub account and gh is now another, it refuses. The skill and the notes inside sandboxes tell Claude Code and Codex to do that.
Inside a sandbox
The sandbox’s own cloudex feedback "message" makes the same kind of report, with drafts and --send <id> as above; --last-error and --web exist only on your computer. Its report says it came from inside a sandbox, with its size, the API’s version and the system. It removes the values of the sandbox’s environment variables, its id, its name when that can’t be an ordinary word, the preview domain, and the same shapes of secrets. It files with gh when gh is signed in there (for example with a GH_TOKEN in the sandbox’s settings), under that account, and prints the new-issue link otherwise.
Security problems
Don’t report security problems in public. Use private reporting instead.