Skip to content
Seggo

Claude Cowork

Status: not supported yet. Cowork appears on the Tools page so you know where it stands, but it can’t be turned on.

Why

Section titled “Why”

Seggo connects to a tool by running a small local server on your computer. It hasn’t been shown that Cowork can use one, so Seggo refuses to set it up until that’s proven. This is Seggo being careful, not a finding about Cowork. A Cowork session running in the cloud shouldn’t be assumed to reach your computer at all.

The route that works: Markdown import

Section titled “The route that works: Markdown import”

You can still bring a Cowork conversation into Seggo by hand.

  1. Copy the conversation (or the part you need) into a .md file, with ## User and ## Assistant headings:

    ## User
    Plan the sign-up page for example-app.
    

    ## Assistant
    Here's a plan: a form with email and password, then...

  2. Put the file in a folder and import that folder:

    Terminal window
    seggo import --sources markdown --export-root /path/to/folder

The conversation then shows up in Seggo’s search and history, and you can continue it in another tool.

This is an import, not a live connection. The result is a thread, not a saved handoff with “done, failed, next” fields.

seggo surfaces prints the current status of each Claude surface.