A native Mac app for your Markdown notes. Your Markdown notes in VS Code, Neovim, Zed or Helix, on Mac, Windows and Linux. Claude Code or Codex pulls the right note and its links into context in milliseconds, so it never starts from zero.
The editor brings the whole product knowledge base into one window: feature specs, plans and bug records, linked into a single graph. Structure comes from links, shape comes from schemas, and the milestones set the order.
After the laptop sleeps during a focus session, the timer sometimes shows more remaining time than before sleep, or jumps straight to negative values.
Reproduction
Start a 25-minute session, wait until ~10:00 remaining.
Close the lid for 5+ minutes, reopen.
Timer shows 10:04, 10:31, or -42:17 depending on sleep length.
Root cause
The tick handler recomputes remaining time from Date.now() deltas, so the wall clock leaks into elapsed time across sleep — a direct violation of the “Wall-clock independence” requirement in the 📐 Timer spec.
Fix
Compute elapsed time from performance.now() (monotonic) and reconcile once on the wake event instead of every tick.
Add the code anchors for this bug
Reading 🧭 Timer engine
+2 blocks in Key references
timer
🐛 Bugs / Timer drifts after laptop sleep
📐 Spec / Timer
🧭 Codebase / Timer engine
Documents
📜Meditations515
👑The Prince27
⚡Beyond Good and Evil296
💡Concepts
🗂️Categories
⏳Seventeen Centuries
Directories
#Tags
💡Concepts
Meditations, The Prince, Beyond Good and Evil
💡Virtue
Same word. Three completely different meanings across seventeen centuries.
Marcus Aurelius — virtue is acting according to nature and reason, serving the common good as naturally as the eye sees.
Machiavelli — a prince who acts entirely virtuously will be ruined among so much evil.
Nietzsche — every virtue inclines toward stupidity.
He who fights with monsters should be careful lest he thereby become a monster. And if thou gaze long into an abyss, the abyss will also gaze into thee.
iwe retrieve -k virtue --expand-includes 2
iwe find --references will-to-power
iwe tree -k bge
Explain this aphorism in two lines for my notes
Reading Beyond Good and Evil · 146
+1 block in Study notes
nietzsche
Beyond Good and Evil
Concepts / Will to Power
Concepts / Virtue
Documents
📋Backlog9
🎨Brand
🏘️Communities1
🥊Competitors1
✏️Drafts1
🌲Evergreen1
🧪Experiments1
🎙️Interviews2
💬Mentions1
📊Metrics
🏷️Offer
👥People8
🏛️Pillars1
🗺️Plan4
Directories
#Tags
🎙️InterviewsMarco (agency owner)
interviewchurnedJuly 24, 2026
Marco (agency owner) — churned after two months
30-minute call with Marco, who cancelled PlainInvoice after two months. Not a product rejection — a workflow mismatch: his agency grew and bookkeeping moved to an assistant who doesn’t live in the terminal.
Verbatim quotes
“It was perfect when it was just me. The moment someone else had to send invoices, the terminal became a wall.”
“I’d come back for solo side work in a heartbeat.”
Learnings
The free→paid boundary holds for solo freelancers but breaks at first hire. Filed the pricing-page wording as an experiment idea; updated the anti-persona in Product.
Turn Marco’s learnings into an experiment
Reading Experiments
+1 note in Experiments
sarah
People / Sarah K.
Mentions / Sarah recommends PlainInvoice
Interviews / Sarah K. — why she switched
Documents
📋Backlog9
🎨Brand
🏘️Communities1
🥊Competitors1
✏️Drafts1
🌲Evergreen1
🧪Experiments1
🎙️Interviews2
💬Mentions1
📊Metrics
🏷️Offer
👥People8
🏛️Pillars1
🗺️Plan4
Directories
#Tags
Foundation
trackerlivingJuly 26, 2026
🎨Brand
Voice, visuals, and the reusable description variants. Copy and creative skills read this so output stays consistent without re-briefing every session.
Voice
3–5 personality traits, tone rules (e.g. “plain speech, no exclamation marks, technical precision over hype”), and a banned-words list.
Descriptions
One-liner — the party sentence
Tagline — ≤10 words
Short — ≤60 characters, for directory listings
Medium — ≤150 words, for launch platforms
Boilerplate — the press-release paragraph
Visual kit
Brand colors (hex), fonts, logo file locations (light/dark variants), illustration or screenshot style notes.
Fill in the visual kit from our design files
Reading Brand
+4 blocks in Visual kit
landing
Experiments / Landing page social proof above the fold
The editor brings the whole product knowledge base into one window: feature specs, plans and bug records, linked into a single graph. Structure comes from links, shape comes from schemas, and the milestones set the order.
After the laptop sleeps during a focus session, the timer sometimes shows more remaining time than before sleep, or jumps straight to negative values.
Reproduction
Start a 25-minute session, wait until ~10:00 remaining.
Close the lid for 5+ minutes, reopen.
Timer shows 10:04, 10:31, or -42:17 depending on sleep length.
Root cause
The tick handler recomputes remaining time from Date.now() deltas, so the wall clock leaks into elapsed time across sleep — a direct violation of the “Wall-clock independence” requirement in the 📐 Timer spec.
Fix
Compute elapsed time from performance.now() (monotonic) and reconcile once on the wake event instead of every tick.
Home
🧭Codebase
Codebase maps derived from the code, each pinned to the commit it was read at.
30-minute call with Marco, who cancelled PlainInvoice after two months. Not a product rejection — a workflow mismatch: his agency grew and bookkeeping moved to an assistant who doesn’t live in the terminal.
Verbatim quotes
“It was perfect when it was just me. The moment someone else had to send invoices, the terminal became a wall.”
“I’d come back for solo side work in a heartbeat.”
Learnings
The free→paid boundary holds for solo freelancers but breaks at first hire. Filed the pricing-page wording as an experiment idea; updated the anti-persona in Product.
Home
💬Mentions
Every third-party mention of the product — comments, threads, listings, reviews.
Voice, visuals, and the reusable description variants. Copy and creative skills read this so output stays consistent without re-briefing every session.
Voice
3–5 personality traits, tone rules (e.g. “plain speech, no exclamation marks, technical precision over hype”), and a banned-words list.
Descriptions
One-liner — the party sentence
Tagline — ≤10 words
Short — ≤60 characters, for directory listings
Medium — ≤150 words, for launch platforms
Boilerplate — the press-release paragraph
Visual kit
Brand colors (hex), fonts, logo file locations (light/dark variants), illustration or screenshot style notes.
Home
🏘️Communities
Every venue this campaign targets or tracks, from launch platforms to subreddits.
He who fights with monsters should be careful lest he thereby become a monster. And if thou gaze long into an abyss, the abyss will also gaze into thee.
One ticket per bug, closed with status: done or cancelled.
FiledFixed
11
Aug 31
3631
Sep 7
4744
Sep 14
4546
Sep 21
8275
Sep 28
Home
💡Concept
Product vision and the principles that outlive any single release.
Documents
12 documents in this collection.
Home
💭Someday
Ideas and POCs that are not commitments yet.
Documents
7 documents in this collection.
Home
📋Backlog
Prioritized single-topic work items waiting to become a plan or a quick fix.
Documents
58 documents in this collection.
Home
📐Spec
Behavioral specifications — the durable truth about how the product must work.
Documents
57 documents in this collection.
Home
📝Plans
Implementation plans. A plan is active while it has no status; it is scheduled by an inclusion link from the 🏁 Milestones plan that ships it, and moves to the archive once its status becomes done or cancelled. The plans below are active but not yet scheduled under any milestone.
The first major release. Documents get themes, charts draw live from your notes, and the agent answers "show me" with a chart or a table that stays current instead of a paragraph of numbers. Mermaid diagrams are drawn by Mermaid itself, the toolbar's back and forward buttons remember where you have been, and a long list of fixes makes standard editing mode, the cursor and the agent UI behave the way you expect.
Highlights
Themes for your documents. Pick how documents look in Settings ▸ Appearance ▸ Theme: Standard, Book, Compact, Typewriter, Gruvbox or Solarized, or a theme of your own. The editor, previews, diagrams and pages all follow it.
Live charts from your notes. A chart block draws a chart from your documents and keeps it current as they change, and the agent builds charts, tables and dashboards when you ask to see something.
The editor brings the whole product knowledge base into one window: feature specs, plans and bug records, linked into a single graph. Structure comes from links, shape comes from schemas, and the milestones set the order.
A document in Architecture. System design notes and the reasoning behind them, rejected alternatives included.
📋Backlog
Capture the current architecture
A document in Backlog. Prioritized single-topic work items waiting to become a plan or a quick fix.
📋Backlog
Fill in the product doc
A document in Backlog. Prioritized single-topic work items waiting to become a plan or a quick fix.
📋Backlog
Import the existing backlog
A document in Backlog. Prioritized single-topic work items waiting to become a plan or a quick fix.
📋Backlog
Plan the first feature
A document in Backlog. Prioritized single-topic work items waiting to become a plan or a quick fix.
🐛BugsFlow: session lifecycleTimer engine
bugTimer
Bug: Timer drifts after laptop sleep
After the laptop sleeps during a focus session, the timer sometimes shows more remaining time than before sleep, or jumps straight to negative values.
Reproduction
Start a 25-minute session, wait until ~10:00 remaining.
Close the lid for 5+ minutes, reopen.
Timer shows 10:04, 10:31, or -42:17 depending on sleep length.
Root cause
The tick handler recomputes remaining time from Date.now() deltas, so the wall clock leaks into elapsed time across sleep — a direct violation of the “Wall-clock independence” requirement in the 📐 Timer spec.
Fix
Compute elapsed time from performance.now() (monotonic) and reconcile once on the wake event instead of every tick.
🧭Codebase
Flow: session lifecycle
A document in Codebase. Codebase maps derived from the code, each pinned to the commit it was read at.
🧭Codebase
Session store
A document in Codebase. Codebase maps derived from the code, each pinned to the commit it was read at.
🧭Codebase
Store
A document in Codebase. Codebase maps derived from the code, each pinned to the commit it was read at.
🧭Codebase
Timer engine
A document in Codebase. Codebase maps derived from the code, each pinned to the commit it was read at.
💡Concept
Why Pomodux
A document in Concept. Product vision and the principles that outlive any single release.
✨Features
Focus sessions
A document in Features. Feature design documents, each carrying its lifecycle stage.
✨Features
Streak widget
A document in Features. Feature design documents, each carrying its lifecycle stage.
🗺️Plans
Focus sessions
A document in Plans. Implementation plans, migrations, and design proposals, one document per unit of work.
🗺️Plans
Streak widget
A document in Plans. Implementation plans, migrations, and design proposals, one document per unit of work.
🗺️Plans
MVP
A document in Plans. Implementation plans, migrations, and design proposals, one document per unit of work.
🚀Releases
0.1.0
A document in Releases. One page per version, aggregating the features and fixes it shipped.
🚀Releases
Unreleased
A document in Releases. One page per version, aggregating the features and fixes it shipped.
💭Someday
Watch app
A document in Someday. Ideas and POCs that are not commitments yet.
📐Spec
Timer
A document in Spec. Behavioral specifications — the durable truth about how the product must work.
📋Backlog
Fill in the product doc
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
📋Backlog
Pick and schedule the first launch venue
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
📋Backlog
Profile your top competitors
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
📋Backlog
Prune the venue list to your ICP
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
📋Backlog
Record your baseline numbers
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
🏘️Communities
Reddit
A document in Communities. Every venue this campaign targets or tracks, from launch platforms to subreddits.
🥊Competitors
BillingBear
A document in Competitors. One profile per competitor, refreshed through dated snapshots.
✏️Drafts
Hn
A document in Drafts. Posts and launch copy that are not published yet.
🌲Evergreen
Your invoices should live in git, like everything else you make
A document in Evergreen. Long-lived pieces that keep bringing readers in.
🧪Experiments
Landing page social proof above the fold
A document in Experiments. Everything tried and its verdict — the permanent answer to “what have you already tested”.
🎙️Interviews
Sarah K. (freelance backend dev) — why she switched from BillingBear
A document in Interviews. Deliberate research events — customer interviews and surveys, one dated record each.
🎙️InterviewsMarco (agency owner)
interviewchurnedJuly 24, 2026
Marco (agency owner) — churned after two months
30-minute call with Marco, who cancelled PlainInvoice after two months. Not a product rejection — a workflow mismatch: his agency grew and bookkeeping moved to an assistant who doesn’t live in the terminal.
Verbatim quotes
“It was perfect when it was just me. The moment someone else had to send invoices, the terminal became a wall.”
“I’d come back for solo side work in a heartbeat.”
Learnings
The free→paid boundary holds for solo freelancers but breaks at first hire. Filed the pricing-page wording as an experiment idea; updated the anti-persona in Product.
💬Mentions
Sarah recommends PlainInvoice in an HN invoicing-tools thread
A document in Mentions. Every third-party mention of the product — comments, threads, listings, reviews.
👥People
Devon (Tools Weekly)
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
👥People
Marco (agency owner)
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
👥People
Amplifiers
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
👥People
Contacts
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
👥People
Creators
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
🏛️Pillars
Invoice without leaving the terminal
A document in Pillars. Every publication grouped by the messaging pillar it carries.
🗺️Plan
Get the first 10 users
A document in Plan. Campaign-level moves, each a plan step with its own definition of done.
🗺️Plan
Get the first 100 users
A document in Plan. Campaign-level moves, each a plan step with its own definition of done.
🗺️Plan
Get the first 1000 users
A document in Plan. Campaign-level moves, each a plan step with its own definition of done.
🗺️Plan
Launch on r/SideProject
A document in Plan. Campaign-level moves, each a plan step with its own definition of done.
📋Backlog
Fill in the product doc
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
📋Backlog
Pick and schedule the first launch venue
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
📋Backlog
Profile your top competitors
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
📋Backlog
Prune the venue list to your ICP
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
📋Backlog
Record your baseline numbers
A document in Backlog. Atomic, single-sitting tasks, linked here by state.
🏘️Communities
Reddit
A document in Communities. Every venue this campaign targets or tracks, from launch platforms to subreddits.
🥊Competitors
BillingBear
A document in Competitors. One profile per competitor, refreshed through dated snapshots.
✏️Drafts
Hn
A document in Drafts. Posts and launch copy that are not published yet.
🌲Evergreen
Your invoices should live in git, like everything else you make
A document in Evergreen. Long-lived pieces that keep bringing readers in.
🧪Experiments
Landing page social proof above the fold
A document in Experiments. Everything tried and its verdict — the permanent answer to “what have you already tested”.
🎙️Interviews
Sarah K. (freelance backend dev) — why she switched from BillingBear
A document in Interviews. Deliberate research events — customer interviews and surveys, one dated record each.
🎙️InterviewsMarco (agency owner)
interviewchurnedJuly 24, 2026
Marco (agency owner) — churned after two months
30-minute call with Marco, who cancelled PlainInvoice after two months. Not a product rejection — a workflow mismatch: his agency grew and bookkeeping moved to an assistant who doesn’t live in the terminal.
Verbatim quotes
“It was perfect when it was just me. The moment someone else had to send invoices, the terminal became a wall.”
“I’d come back for solo side work in a heartbeat.”
Learnings
The free→paid boundary holds for solo freelancers but breaks at first hire. Filed the pricing-page wording as an experiment idea; updated the anti-persona in Product.
💬Mentions
Sarah recommends PlainInvoice in an HN invoicing-tools thread
A document in Mentions. Every third-party mention of the product — comments, threads, listings, reviews.
👥People
Devon (Tools Weekly)
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
👥People
Marco (agency owner)
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
👥People
Amplifiers
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
👥People
Contacts
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
👥People
Creators
A document in People. The campaign’s CRM — one document per person, grouped by the role they play.
🏛️Pillars
Invoice without leaving the terminal
A document in Pillars. Every publication grouped by the messaging pillar it carries.
🗺️Plan
Get the first 10 users
A document in Plan. Campaign-level moves, each a plan step with its own definition of done.
🗺️Plan
Get the first 100 users
A document in Plan. Campaign-level moves, each a plan step with its own definition of done.
🗺️Plan
Get the first 1000 users
A document in Plan. Campaign-level moves, each a plan step with its own definition of done.
🗺️Plan
Launch on r/SideProject
A document in Plan. Campaign-level moves, each a plan step with its own definition of done.
📜Meditations
Virtue
Linked from Meditations.
📜Meditations
Nature
Linked from Meditations.
📜Meditations
Reason
Linked from Meditations.
👑The Prince
Virtue
Linked from The Prince.
👑The Prince
Power
Linked from The Prince.
👑The Prince
Cruelty
Linked from The Prince.
⚡Beyond Good and Evil
1886Nietzsche
146
He who fights with monsters should be careful lest he thereby become a monster. And if thou gaze long into an abyss, the abyss will also gaze into thee.
He who fights with monsters should be careful lest he thereby become a monster. And if thou gaze long into an abyss, the abyss will also gaze into thee.
Linked from Product knowledge base. Version, collection and status come from the note’s own front matter.
✨Features
✨ FeaturesImplemented
Search and Query Pages
Linked from Product knowledge base. A search page filters notes by their properties and links, and groups the results.
✨Features
0.1.1✨ FeaturesImplemented
Extract Section
Linked from Product knowledge base. Version, collection and status come from the note’s own front matter.
✨Features
0.21.0✨ FeaturesImplemented
Tabs and Working Contexts
Linked from Product knowledge base. Tabs and split view keep several notes open at once.
📝Plans
Localization — The App in 26 Languages
A document in Plans. Implementation plans, migrations, and design proposals, one document per unit of work.
📝Plans
Right-to-Left Editing
A document in Plans. Implementation plans, migrations, and design proposals, one document per unit of work.
📝Plans
Chart Blocks — Named Queries
A document in Plans. Implementation plans, migrations, and design proposals, one document per unit of work.
🚀Releases
1.0.0ReleasedOctober 3, 2026
1.0.0
The first major release. Documents get themes, charts draw live from your notes, and the agent answers "show me" with a chart or a table that stays current instead of a paragraph of numbers. Mermaid diagrams are drawn by Mermaid itself, the toolbar's back and forward buttons remember where you have been, and a long list of fixes makes standard editing mode, the cursor and the agent UI behave the way you expect.
Highlights
Themes for your documents. Pick how documents look in Settings ▸ Appearance ▸ Theme: Standard, Book, Compact, Typewriter, Gruvbox or Solarized, or a theme of your own. The editor, previews, diagrams and pages all follow it.
Live charts from your notes. A chart block draws a chart from your documents and keeps it current as they change, and the agent builds charts, tables and dashboards when you ask to see something.
How does Nietzsche explain the origin of morality?
What does “will to power” mean?
Explain aphorism §146 in your own words.
Your exam notes are ready in 📝 Exam notes: the main ideas, a key aphorism with its number, and a likely exam question. Each point links back to its fragment.
TimerEngine.tick() derives elapsed time from Date.now(). The wall clock jumps when the Mac sleeps and when it resyncs, and the jump leaks into the countdown — against the “wall-clock independence” rule in 📐 Timer spec.
Lid closes→System sleeps→Wake event→tick() reads Date.now()→Drift
Fix
swift · TimerEngine.swift
- let elapsed = Date.now() - startedAt+ let elapsed = clock.monotonicNow() - startedAt+ session.onWake { engine.reconcile(at: clock.monotonicNow()) }
Root cause: TimerEngine.tick() reads Date.now(), so wall-clock jumps across sleep leak into the countdown. The fix moves the tick to a monotonic clock and reconciles once on wake, with a regression test. Plan, risks and rollout are in 🧭 Fix plan: timer drift, ready for review.
Release 1.1 ships localization, right-to-left editing and chart blocks. I wrote 🚀 Release 1.1 with the scope as a checklist and the four blocking bugs.
hero · terminalpricing · one planinvoice cardinstall snippetfooter · links
Calm and precise, like the product: one accent color, no hype.🎨 Brand · voice
Next steps
Pick one hero direction with the team
Add the palette to 🎨 Brand
Draft the landing from the library
I went through 9 references and kept the three closest to our brand. 🎨 Landing references breaks down their type, color and layout, and the blocks we reuse are saved as a library.
Claude Code is editing this note
Preview
📝 Plans
collection240 notes
Implementation plans. A plan is active while it has no status; it is scheduled by an inclusion link from the Milestones plan that ships it, and moves to the archive once its status becomes done or cancelled.
FreemacOS 15 or latermacOS 15+No accountWorks with the tools you already use
Works with the tools you already use
Claude CodeCodexCursorWindsurfVS CodeNeovimZedHelixObsidian vaultsGitOllamaOpenAIAnthropicGoogle
Claude CodeCodexCursorWindsurfVS CodeNeovimZedHelixObsidian vaultsGitOllamaOpenAIAnthropicGoogle
How it works
One folder. Every tool.
The app, your editor and your agent all work on the same Markdown files. Your agent gets a note and everything it links to in one call, and your notes never move.
iWe for MacWrite notes with your agent
Block editor with live charts
⌘K opens any note
Claude Code or Codex inside the app
>_TerminalThe iwe CLI and git, same files
iwe find --references launch-plan
iwe retrieve -k launch-plan
git tag v1.0
~/notes/launch-plan.md4 tools, one note
↖ 📝 Plans
Launch plan
Set the goal: launch onboarding by Friday
Tag the v1.0 release
Update the setup guide
Sum up feedback from 3 interviews
Plain Markdown · on your Mac · no account
Tap a tool to see what it does to the note
Your editorVS Code, Neovim, Zed or Helix
Links autocomplete as you type
Rename a note, links follow
Hover to preview a linked note
✦Your agentClaude Code or Codex over MCP
iwe_find · iwe_retrieve
iwe_create · iwe_update
+10 more tools
Inside the app
See how the iWe app works. Real screens, real notes.
Every view below is the iWe Mac app, filled with a product team’s plans, specs, bugs and releases.
01 Links
Notes connect into one structure
Plans, specs, bugs and releases are plain Markdown notes. Links tie them together: a plan is scheduled by a link from its milestone and moves to the archive once its status is done.
Documents
✨Features95
🏁Milestones153
🏛️Architecture47
🐞Bugs208
💡Concept12
💭Someday7
📋Backlog60
📐Spec57
📝Plans245
📥Inbox5
🧠Learnings63
🚀Releases264
Product knowledge base4
Home
📝Plans
Implementation plans. A plan is active while it has no status; it is scheduled by an inclusion link from the 🏁 Milestones plan that ships it, and moves to the archive once its status becomes done or cancelled. The plans below are active but not yet scheduled under any milestone.
Front matter shows above the title, here a release’s version, status and date. In the file it stays plain YAML at the top of the Markdown.
Documents
✨Features95
🏁Milestones153
🏛️Architecture47
🐞Bugs208
💡Concept12
💭Someday7
📋Backlog60
📐Spec57
📝Plans246
📥Inbox5
🧠Learnings63
🚀Releases264
Product knowledge base4
🚀Releases
1.0.0ReleasedOctober 3, 2026
1.0.0
The first major release. Documents get themes, charts draw live from your notes, and the agent answers "show me" with a chart or a table that stays current instead of a paragraph of numbers. Mermaid diagrams are drawn by Mermaid itself, the toolbar's back and forward buttons remember where you have been, and a long list of fixes makes standard editing mode, the cursor and the agent UI behave the way you expect.
Highlights
Themes for your documents. Pick how documents look in Settings ▸ Appearance ▸ Theme: Standard, Book, Compact, Typewriter, Gruvbox or Solarized, or a theme of your own. The editor, previews, diagrams and pages all follow it.
Live charts from your notes. A chart block draws a chart from your documents and keeps it current as they change, and the agent builds charts, tables and dashboards when you ask to see something.
03 Charts
Charts that stay current
A chart block draws live from your notes and updates as they change. Ask the agent to show you something, and it answers with a chart or a table.
Documents
✨Features95
🏁Milestones153
🏛️Architecture47
🐞Bugs208
💡Concept12
💭Someday7
📋Backlog60
📐Spec57
📝Plans246
📥Inbox5
🧠Learnings63
🚀Releases264
Product knowledge base4
Home
🐞Bugs
One ticket per bug, closed with status: done or cancelled.
FiledFixed
11
Aug 31
3631
Sep 7
4744
Sep 14
4546
Sep 21
8275
Sep 28
04 Code
Technical docs with real code
Keep design notes and code side by side. Code blocks are highlighted and copy with one click.
Implementation plans. A plan is active while it has no status; it is scheduled by an inclusion link from the 🏁 Milestones plan that ships it, and moves to the archive once its status becomes done or cancelled. The plans below are active but not yet scheduled under any milestone.
The first major release. Documents get themes, charts draw live from your notes, and the agent answers "show me" with a chart or a table that stays current instead of a paragraph of numbers. Mermaid diagrams are drawn by Mermaid itself, the toolbar's back and forward buttons remember where you have been, and a long list of fixes makes standard editing mode, the cursor and the agent UI behave the way you expect.
Highlights
Themes for your documents. Pick how documents look in Settings ▸ Appearance ▸ Theme: Standard, Book, Compact, Typewriter, Gruvbox or Solarized, or a theme of your own. The editor, previews, diagrams and pages all follow it.
Live charts from your notes. A chart block draws a chart from your documents and keeps it current as they change, and the agent builds charts, tables and dashboards when you ask to see something.
Documents
✨Features95
🏁Milestones153
🏛️Architecture47
🐞Bugs208
💡Concept12
💭Someday7
📋Backlog60
📐Spec57
📝Plans246
📥Inbox5
🧠Learnings63
🚀Releases264
Product knowledge base4
Home
🐞Bugs
One ticket per bug, closed with status: done or cancelled.
Four steps to shared memory. Start in five minutes.
Install IWE, point it at your notes, connect your agent and ask. Prefer not to do it yourself? Hand it to your agent.
Download the app, or use one command.
Pick how you edit: Standard or Vim.
Connect Claude Code or Codex.
Ask, and watch your agent work.
Step 01 · Install
$brew install iwe-org/iwe/iwe# installs the CLI (iwe), the LSP server (iwes)# and the MCP server (iwec)$npm install -g @iwe-org/iwe# the same three binaries, Windows included$
Installs the iwe CLI, the iwes language server and the iwec MCP server. Prefer an app? Download iWe for Mac (macOS 15 or later).
Step 02 · First launch
$cd ~/notes$iwe init.iwe/└── config.toml # Project configuration# your Markdown stays as it is$
init reads your files first and fits the configuration to the conventions you already use. An existing folder of Markdown works as-is.
Step 03 · Connect
◇iwecMCP server · ~/notesReady
✳Claude Codeor Codex, in the Mac appSigned in
iwec exposes 14 tools to your agent
iwe_findiwe_retrieveiwe_treeiwe_statsiwe_squashiwe_createiwe_updateiwe_delete+6 more
Add the iwec MCP server with its working directory set to your notes, or run your agent inside the iWe app on your own login.
Step 04 · Ask
$iwe retrieve --lexical "auth rewrite" \--expand-includes 2# finds the note, then brings its linked context$iwe find --references will-to-power# everything that links to will-to-power$iwe tree -k bge# a note and its children as a tree$
Search finds the entry point; one retrieve call expands the surrounding structure into context.
Open source coreThe IWE engine, CLI and language server, all on GitHub. The iWe Mac app is built on them and is free.Star on GitHub ↗
Start with the Mac app, or use IWE in VS Code, Neovim, Zed or Helix on Mac, Windows or Linux.Use IWE in VS Code, Neovim, Zed or Helix on Mac, Windows or Linux, or start with the Mac app. Your notes stay the same Markdown files.