Help & troubleshooting.

Ask Squeezy first

Type /help for a categorized topic index, /help <topic> for a topic, or /help /<command> (for example /help /router) for a single slash command's syntax and examples. A known topic or command is answered locally from the documentation bundled in the binary and your redacted configuration, with no provider call. A free-text /help question that no local topic covers is answered by a small doc-help model pass over the same bundled docs. It is the fastest way to learn a command or setting.

Each answer is tagged with where it came from (a local curated answer, a doc-help model answer, or a doc-help web answer), and lists the bundled docs, config sections, and any links it drew on. Rate an answer with Ctrl+G or Ctrl+B to send anonymous feedback on whether it helped.

If you turn on the optional web fallback, a question the bundled docs don't cover can be answered from published Squeezy documentation with the source link cited. It is off by default and only runs when web access is permitted.

When startup looks wrong

Run squeezy doctor. It reports your merged configuration sources, repo profile, the configured provider credential, the session-store path, and shell-sandbox availability, which is usually enough to spot a missing key, a wrong provider, or a config that is not being picked up.

squeezy doctor

Reporting an issue

Use the in-product paths so a report is tied to a session: /feedback for a short note, /report for the current run, and squeezy sessions report for an earlier one. Each produces a redacted bundle you can preview before sending.

/feedback
/report
squeezy sessions report <session_id> --preview
squeezy sessions report <session_id> --send

Keep the feedback or report id with a short sanitized description of the symptom, your platform, provider route, and the command that failed. If support asks you to share it, never include secrets, private code, or report-archive contents in the message.