First run

Open Seggo

Mac app: double-click Seggo in your Applications folder. Seggo opens in its own Mac window, with a Dock icon. No Terminal or browser tab is needed.

Seggo’s icon (two crossing lines) also sits in the menu bar at the top right of your screen. Click it to bring the window back (Open Seggo), see whether Seggo is running, show its log, open the same pages in your browser, or quit. Cmd+W closes the window but keeps Seggo running; Cmd+Q quits.

Terminal install or Windows: run

seggo open

Your browser opens http://127.0.0.1:7420/.

Either way, Seggo’s pages come from your own computer at http://127.0.0.1: nothing is loaded from the internet.

• Opening Seggo again while it runs brings back the same Seggo instead of starting a second copy.
• seggo open --no-browser just prints the address.
• Seggo keeps running until you quit it or log out.

The guided tour

The first time you open Seggo, in the Mac app’s window or your browser, a short tour starts. It has four steps:

1. Welcome. What Seggo does, where it keeps its data on your computer, and that everything stays there.
2. Your tools. Every tool Seggo looks for, marked “Found”, “Not installed” or “Found but can’t read”. The found tool with the most recent history is suggested first.
3. Turn one on. Switch on one tool. Seggo shows a preview of exactly what it will change before it changes anything (see below).
4. See a handoff. Seggo waits for the first handoff that tool saves. If you’d rather look around first, choose Try with sample data. It’s clearly labelled as example data, kept apart from your real history, and removed with Clear sample data.

Skip tour is on every step. If you close it part way, it picks up where you left off next time. To see it again, click Take the tour in the sidebar or under Help and feedback in Settings, or run seggo open --tour.

Turn on your first tool

You can do this in the tour, or later from Tools in the sidebar.

1. Switch a tool, for example Claude Code or Codex, On.
2. Pick the project you want to use it in.
3. Read the preview. It lists every file Seggo will change and what it will add. Click Confirm.

The switch then shows On in 1 project.

What turning a tool on changes, only after you confirm:

• a seggo entry in that tool’s MCP settings file, so the tool can save handoffs and read project context;
• a marked Seggo section in the project’s CLAUDE.md or AGENTS.md (or similar);
• for Claude Code, a session-end hook.

Every change is listed under What Seggo changed, and switching the tool Off undoes it, with its own preview. More on this in Connect your tools.

Try it

1. In your project, start the tool you turned on (for example claude or codex).
2. Ask for something small, such as “Add a README section describing this folder.”
3. Before you finish, ask: “Save a Seggo handoff for this work.”
4. Back in Seggo, pick the project in the sidebar. The session and its handoff are under Threads. Anything the tool saved about goals, decisions or open tasks is under Project context.

Now start the other tool in the same project and ask “What was done here last?” It should pick up from the handoff.

For the full version with the task board, try a two-tool handoff in 10 minutes.

Start at login (optional)

In Settings, Start at login (Windows: Start when you sign in) starts Seggo each time you log in. It’s off unless you turn it on.