Skip to content
Seggo

Troubleshooting and feedback

Check your setup

Section titled “Check your setup”
Terminal window
seggo doctor

seggo doctor checks your setup and prints where Seggo keeps its program, data, log and settings on your computer. seggo doctor --json gives the same status as JSON.

Common problems

Section titled “Common problems”

seggo isn’t found. Open a new terminal window after installing, so it sees the updated PATH. On macOS, if the installer said ~/.local/bin isn’t on your PATH, add the line it printed to ~/.zshrc.

macOS or Windows blocks it. The builds aren’t signed yet. See If macOS blocks it or If Windows blocks it.

seggo open doesn’t open the page. Look at the end of seggo-ui.log in Seggo’s data folder:

macOS Windows
~/.local/share/seggo/seggo-ui.log %LOCALAPPDATA%\Seggo\seggo-ui.log

Your tool says Seggo is unavailable. Check the tool is switched On for that project in Tools, then start a new session in the tool. See Connect your tools.

“Couldn’t check right now” under Updates. That’s expected during the pilot. See Update Seggo.

Send feedback

Section titled “Send feedback”

In Seggo, click Send feedback at the bottom of the sidebar (also in Workspace settings > Help and feedback).

  1. Type what happened or what you’d like (optional).
  2. Read the preview. It shows exactly what will be copied.
  3. Click Copy report and paste it where you choose, or Save report… to get a file named seggo-feedback-<version>-<date>.txt to attach.

From a terminal, this prints the same report:

Terminal window
seggo feedback

Add --json for JSON.

What the report includes

Section titled “What the report includes”
  • Your Seggo version and OS.
  • The same status check and paths as seggo doctor.

What it leaves out

Section titled “What it leaves out”
  • Your threads, handoffs, project context, prompts, files and project names.
  • Your home folder (shown as ~, or %USERPROFILE% on Windows) and your user name.

Seggo sends nothing itself. You choose where to paste the report.

Also helpful

Section titled “Also helpful”
  • Your OS and version (for example macOS 15.1 on Apple Silicon, or Windows 11 23H2), and which tool you were using.
  • The exact error text, or a screenshot (check it shows nothing private).
  • If seggo open failed, the last 30 lines of seggo-ui.log.

Please don’t send your session transcripts or project files.