Support

Answers, fixes, and a direct line.

Most of what people ask about the assistant, privacy, keys, and where boards live — collected here. Everything else goes straight to an inbox.

FAQ

The short answers.

Click any question to open it.

What is the dashed card that appears on my board?

That's a suggestion from the built-in Smarti Assistant. It's dashed, muted, and a different hue on purpose: it lives in a separate layer from your board's data, so a suggestion cannot merge into your content — even by accident.

Accept or Dismiss, both one click. Accepting constructs a brand-new card with a small authorship dot; dismissing is remembered for the session, so it won't re-offer the same idea reworded.

When does the assistant speak — and when does it stay quiet?

Never per keystroke. It waits about four seconds of quiet after your last meaningful change, needs at least three non-empty ideas on the board, and offers one suggestion at a time. Dragging cards around never triggers it — only text, connections, the objective, and crossing ideas off do, because those change what the board says.

The wait is adjustable: ⚙ Settings → Ghost frequency offers 4s (default), 10s, 30s, 1 minute, or Off. Off stops the unsolicited ghost entirely; the ideas panel keeps working.

Do I need an API key or an account?

No account, ever — and no key is a supported configuration: the board is fully usable and the assistant simply stays off.

If you want the assistant, bring your own key: Anthropic (Claude), z.ai (GLM), z.ai Coding Plan, or any OpenAI-compatible endpoint (LM Studio, vLLM, OpenRouter…). Ollama runs locally with nothing leaving your machine. Keys are stored in your own database and are write-only — the settings panel only ever shows the last four characters.

What does Privacy Mode actually do?

⌘⇧P (or the Private button) marks the board you're looking at private: no suggestions arrive, the ideas button is unavailable, and nothing from that board is sent to any model.

It's per board, so the rest keep working. The promise is kept by the server, not the browser — a stale tab or a retry gets the same refusal — and ⌘Z can never switch it back on for you. Turning it off doesn't immediately wake the assistant; the next real edit does.

Where does my data live?

One SQLite file — ./data/smarti.db by default, one row per board. No accounts, no cloud, no telemetry. Back up by copying the file; move to another machine by copying the folder.

Can the AI change or move my cards?

No. The assistant never moves, edits, or deletes a node you placed — that rule has no exception. The only bridge from a suggestion to the board is your click.

How do undo and redo work?

⌘Z undoes, ⌘⇧Z or ⌘Y redoes. Every deliberate change to content — typing, adding or deleting cards, accepting a suggestion, crossing an idea off, the objective — is one undo step. Dragging and resizing aren't content, so they don't clutter the stack.

A suggestion appearing is never in your undo stack; accepting one is a normal, reversible edit.

Do I ever hit Save? Do I name boards?

There is no save button — the board autosaves continuously, and the status in the bottom-right corner says so. Boards name themselves after their first idea; rename from the top-right corner of the canvas and the override sticks.

The first board in a fresh install is a tutorial — a real board you can edit, wreck, or delete. Open the tutorial board on the library page brings a fresh copy back any time.

Can I present or print a board?

⌘⇧F presents: fullscreen, read-only, the whole board fitted to view — pan and zoom still work, and Esc brings you back exactly where you were.

⌘P prints a read-only paper copy (or saves it as PDF) — the whole board on one page, shrinking as far as ~40% to fit; only a truly sprawling board tiles across pages. Done strikes and formatting print; the pending suggestion, selections, and search highlights never do.

Does it work on a phone or tablet?

Yes — the canvas answers touch: drag to pan, pinch to zoom, drag a card to move it, and press and hold where you would press Shift (empty canvas to sweep a selection, a card to add it to one). Double-tap for a new idea; double-tap a card to edit.

To reach the board from another device, start it with ./start.sh --lan and type the address it prints. That's opt-in on every run, and deliberately so: there's no login, so only do it on networks you trust.

What is hand control — and does the camera watch me?

Hand control (new in v6) turns your webcam into a navigator: pinch and move to pan, pinch with both hands and spread them to zoom, and holding a pinch near the edge keeps the board scrolling. It works on the canvas and in Present mode — which is where it shines.

The tracker is MediaPipe's hand-landmark model running inside the app itself — no cloud, no upload, and nothing is ever recorded. The camera is off until you press Hand control and stops the moment you turn it off. And it's not the assistant: it's local computer vision, never a token.

What can hand control do to my board?

Pan and zoom — and that's the whole vocabulary. Hands can't select, edit, move, or cross off cards, and they can't accept or dismiss suggestions. Navigation-only is deliberate: your board's content stays out of the gesture vocabulary.

On-screen rings always show what the tracker sees — pinch state, zoom mode, and when you're close to losing it at the edge of the frame — and sensitivity is adjustable in ⚙ Settings.

What's deliberately not in Smarti Board?

No multiplayer, no freehand drawing or images, no cross-session memory, no cloud sync. One job, done well: thinking by arranging ideas — with an assistant that respects the arrangement.

Fixes

When something won't start, save, or speak.

The five things that come up, and the fix for each.

npm install refuses to run — or tries to compile things

Smarti Board needs Node 22–26 (a native dependency ships prebuilt binaries for those versions only). If your Node is older, npm stops with EBADENGINE, or attempts a source build that fails. Stopping is the good outcome — nothing gets half-installed.

Easiest fix, with nothing to install first:

./start.sh # downloads its own Node if needed — no sudo, no version manager

Or install Node 22+ yourself, then:

rm -rf node_modules && npm install

Windows isn't covered by start.sh — use WSL, or install Node 22+ and run the npm commands directly.

A second, empty library appeared

The database path is relative to the folder you start the app from. Start it somewhere else and you get a brand-new empty database instead of an error.

Start from the repo root, or point at the file explicitly — the server prints the path it opened on first use:

SMARTI_DB_PATH=/absolute/path/to/smarti.db ./start.sh

The assistant never says anything

Work down the list: a provider key configured in Settings (⚙ or ⌘,)? Privacy Mode off for this board (⌘⇧P)? At least three non-empty ideas on the canvas? Ghost frequency not set to Off?

Then use Test in Settings — one one-token call that tells you whether the key, the address, and the model name are right. Along with Load models, it's the only place AI failures are reported out loud; the ghost and the ideas panel fail quietly on purpose.

My phone can't reach the board

By default the server listens on 127.0.0.1 only — that's deliberate, since there is no login anywhere. To read or edit boards from a phone or tablet on the same network:

./start.sh --lan # binds every interface, prints the address to type

It's opt-in on every run. Fine on your own Wi-Fi; a bad idea on a café or conference network — anyone who can reach the address can read and edit every board.

Hand control says the camera is unavailable

Check the obvious first: another app holding the camera, a physical shutter, or an OS privacy switch (on macOS: System Settings → Privacy & Security → Camera).

In a browser, camera access needs a secure context: localhost and the desktop app qualify, but a plain http:// LAN address does not — a phone reached through ./start.sh --lan won't be able to use hand control (the rest of the touch canvas still works there). Re-grant camera permission for the site, then press the Hand control button again.

Feedback

Tell us what's broken — or what's working.

Bug reports, a FAQ entry that didn't answer your question, a feature you wish existed — it all reaches a person.

Or write to hello@pinecomputenj.com directly.

Code-level issues and pull requests are welcome on GitHub — the project is AGPL-3.0.