The loop
smiet is built around one loop:
- Capture — get a thought out of your head with as little friction as possible.
- Triage — the note is classified into a destination (task, feedback, event, reply, or idea) with structured fields extracted, automatically within seconds.
- Act — you work the inbox, or a connected assistant (e.g. Claude over MCP) carries notes out and reports back.
Everything below is in service of that loop.
Capturing
Type or speak a thought on the Capture screen and press Add to inbox. That's the whole contract — no folders, no tags, no decisions at capture time.
Don't self-censor or pre-sort. Capture in whatever language and shape the thought arrives; triage's job is to make sense of it.
- Voice: the mic button records and transcribes server-side, so dictation quality is consistent across devices (and multilingual).
- Compound thoughts get split. "Publish the release and clean the car" becomes two separately triaged notes; the original is closed out as Split into 2 items. Splitting is conservative — details and steps of one action are never torn apart.
From your iPhone
The iOS app is the lowest-friction capture surface:
- Hold to talk — press and hold the mic, speak, release. With an empty editor the transcript is captured immediately, no second tap.
- Share sheet — share text or a link from any app to Smiet.
- Siri and the Action button — "Capture in Smiet" takes dictation without opening the app.
- Offline — captures made without connectivity are queued on the device and sync when the app next comes to the foreground.
Triage
Every note ends up with exactly one destination:
Task
An actionable to-do. Extracted: title, due date, priority, and a work/personal space hint.
Event
Something happening at a date or time. Extracted: title, start, end, location.
Reply
A message you need to send. Extracted: recipient, channel, a ready-to-send draft, and a work/personal space hint.
Feedback
Feedback about a project or product. Extracted: project name and message. Set up a SeggWat destination in Connections, then review and create from the note.
Idea
A thought to keep — the catch-all. Extracted: tags.
Auto-triage runs on every capture and resolves relative dates ("tomorrow at 10") against your local timezone at capture time. Each note shows how it was triaged:
- Auto — the built-in classifier did it.
- Manual — you tapped a destination yourself.
- AI — an external assistant assigned it over MCP.
Got it wrong? Tap the destination badge on any note and pick another — or clear it to send the note back to triage. Manual triage always wins.
The inbox
The inbox has three sections:
- Inbox — captured, not yet triaged. Needs a decision (yours or the classifier's).
- Triaged — has a destination, waiting to be carried out.
- Processed — done. Each processed note keeps a short outcome ("Added to Todoist", "Marked done by you").
Mark a note Done when you've handled it yourself, or delete what turned out to be noise. Every note carries an activity log — captured, triaged (and by whom), cleared, processed — so you can always reconstruct what happened to a thought.
The widget
The iOS/macOS home-screen widget shows your untriaged count and the current next action — the oldest open note, preferring ones that are ready to act on. It refreshes every ~15 minutes and immediately after you use the app.
Connecting an assistant (MCP)
smiet is an MCP server, so an assistant like Claude can work your inbox for you. Add a custom connector pointing at:
OAuth discovery handles the rest — you'll sign in and approve access once. The assistant then gets these tools:
| Tool | What it does |
|---|---|
capture |
Add a note to your inbox. |
list_inbox |
Read the inbox, including destinations and extracted payloads. |
get_next_action |
The single next note to handle, with what to do about it. |
triage_note |
Assign a destination (shows up as triaged by AI). |
mark_actuated |
Record that a note was carried out, with an outcome summary. |
note_activity |
Read a note's history. |
The intended rhythm: the assistant calls get_next_action, carries the note out in the external system its destination implies (create the task, draft the reply, add the event), then calls mark_actuated with a short outcome — which lands in the note's activity log for you to see.
API keys
For scripts, CLI tools, or anything that isn't OAuth, create a key under Settings → API keys. Keys are shown once, start with oat_, and authenticate via X-API-Key or Authorization: Bearer. Tokens minted through the OAuth flow (the iOS app, MCP connectors) appear in the same list, named after the app that requested them — revoke them there anytime.