Building in public · early MVP

Build it. Ship it.
Let the work speak for itself.

FingShip keeps up with what you’re building, recognizes the progress that matters, and turns approved proof into a clear explanation and something polished to share—quietly, locally, and under your control.

FingShip showing what it understands about the project, the latest meaningful capabilities, and why they matter
Current build · real FingShip dogfoodFingShip understood what it was building before asking the builder to organize anything.

The missing memory layer

What is FingShip?

It understands what you’re building.

Approved commits, builds, tests, agent outcomes, and visual checkpoints become a grounded view of the product and the outcome you are pursuing.

It recognizes progress that matters.

Related evidence becomes one clear feature story: what changed, why it matters, how the product evolved, and what remains unproven. Routine activity stays out of the way.

You decide what leaves.

FingShip prepares the update and keeps its proof attached. You review, edit, and choose the final handoff. Nothing publishes automatically.

How it works

Progress becomes a story—without becoming a chore.

01

Work normally

FingShip watches the projects you choose and listens for small, trustworthy signals from tools you explicitly enable.

02

See what changed

FingShip connects related work into one clear feature update and keeps routine activity out of the way.

03

Scrub the progress

Move through the product’s visual history, compare meaningful states, and see the evidence behind each explanation.

04

Share deliberately

Review the prepared update, card, or share pack. Nothing leaves FingShip until you choose it.

FingShip documenting FingShip

It noticed the fix—and kept the uncertainty honest.

One meaningful change, its consequence, and the proof that matters. The activity behind it stays out of the way.
Fix · noticed todayObserved

Keep project history through macOS reapproval

FingShip now recognizes expired project access, asks for one focused folder approval, and reconnects under the existing project identity instead of creating a duplicate.

Why it mattersThe builder keeps every Moment, screenshot, and narrative relationship while macOS refreshes only the folder permission.
  • Observer recorded the changeObserved
  • Project identity survives reconnectVerified
  • Folder approval on this MacAwaiting approval

Private by default

Your project is not content inventory.

FingShip is designed to collect minimal metadata and approved artifacts—not source code, prompts, secrets, hidden agent state, or continuous screen recordings.

  • Local-first storage
  • Deterministic secret checks
  • No automatic publishing
  • No forced watermark

Current product status

A working local slice—not a public release.

Today the Mac app can watch chosen projects, receive standardized evidence from agents and UI tests, explain meaningful changes, answer questions with targeted project context, show visual history, prepare grounded updates and submission materials, and keep every external handoff under human review. The build is functional and dogfooding itself, but it is not yet signed for public distribution.

Builder story 001
“FingShip captured, reviewed, rendered, and preserved its own progress without storing source code or private agent state.”
Internal dogfood observation · not a customer testimonial