Using it

Clearing things

When you’ve looked at something and you’re happy with it, clear it. It stops asking, until its code changes.

#What clearing means

Clearing says: I’ve seen this, it’s fine. The item turns mint in the harbour and leaves the review queue. Once everything that needed you is cleared, the verdict becomes cleared to sail.

A clear is tied to the item’s exact bytes. slowship fingerprints every item by its content. If a new version of a package arrives, or a skill’s file changes by a single byte, the fingerprint changes and the item asks again. So a clear can never quietly cover code you haven’t seen.

#Three ways to clear

In the morning report

Select the item in the review list and press Clear, or press a. A ship takes it aboard, a painter rolls it green, and the next one comes up. Undo in the message at the bottom puts it back.

In the terminal review

Select it and press c. It slides away. u brings it back.

From the command line

--approve clears in bulk after a watch:

# clear one item by name
slowship --approve tidy-dates

# clear everything that's only "noted"
slowship --approve notable

# clear everything worth a glance (and below)
slowship --approve review

It prints how many it cleared and reminds you that they’ll ask again when their code changes.

#Who can clear

Only you. Your coding agent can ask slowship to check things and to watch the project, but it gets no tool to clear anything. That’s on purpose: an agent reads text that packages wrote, and that text can be written to talk it into things. See Your coding agent.

#Where it’s kept

Clears live in state.json inside ~/.slowship (or SLOWSHIP_HOME), next to slowship’s memory of what it has read. Delete that file and every item asks again.

Suggest a change to this page