Personal continuity OS

Write it down.
Keep the thread.

HowsLife turns journals, git commits, and daily notes into one private continuity engine — so you can pick up where you left off without losing context.

Second brain

Public identity

Resume and portfolio, separately curated.

HowsLife stays private. What the world sees is a deliberate projection — a scan-friendly resume for hiring, and a narrative portfolio for how the work was actually built. Neither exposes journals, raw git history, or unpublished evidence.

Resume

Can this person do the job?

A concise, recruiter-oriented overview — experience, skills, selected projects, and a PDF download. Built for a fast scan.

Open resume

Portfolio

How does this engineer think?

Curated project stories — context, constraints, decisions, and outcomes. Only what has been explicitly published from HowsLife.

Open portfolio

Write

Capture journals from the web or Telegram. Daily notes land in one private inbox — no scattered docs, no lost context.

Journals · Telegram · Web

Evidence

Git commits and structured events become evidence. Your work history stays linked to what you were thinking when you wrote it.

Git hooks · Events · Extraction

Memories

Threads and memory nodes connect entries over time. Patterns surface without turning your life into a performance dashboard.

Memory threads · Continuity graph

Continue

Open the app and resume. The life map, recent journals, and open loops wait for you — not a blank page.

Continue view · Life map · Reasoning

From anywhere. Anytime. Even offline.

Journals from the web or Telegram. Git commits from this laptop. The hook writes a queue file first, so every commit is recorded even when HowsLife is offline. n8n can watch the same folder and replay when the API is back.

Offline-first

Capture
Persist
Sync
Understand
Continue

Laptop commits land in ~/.howslife/queue even when the app is down.

Write it down.Keep the thread.