Fanad

The Rules of Three

The rules live in chat too — ask for them any time.

Just talk to capture

Say what's on your mind in your own words and Fanad files it as a task, quietly picking a category and effort. You unload; Fanad organizes.

See and clear your list

Your open tasks, always numbered 1..N for whatever's on screen. Finish what's done, clear what isn't yours anymore.

One thing to do now

When the list feels like a lot, ask for a single next step, sized to your time, energy, and mood — never a wall.

Tell Fanad how you feel

Drop a mood anytime; it gently softens and sizes what Fanad suggests for a while.

Where to get help

Friendly, tappable references whenever you need them. Prefer a story to a reference? The how-to articles walk one real use case each, start to finish.

Lists & nesting

A separate outliner for anything that isn't a task — checklists, packing lists, anything nestable. (Opt-in.)

Notes recall, grounding & photos

Fanad finds your real notes by meaning — and only ever surfaces notes and tasks that actually exist. It never invents a row.

Guessing steps

The one place Fanad draws on general know-how: once a task is started, it can guess a first-draft checklist — always labeled a guess, always yours to edit.

Templates

The calm alternative to recurring tasks: save a task's shape and steps, then drop a fresh copy whenever you need it.

Metrics

Track any number you like — water, pages, push-ups — and see a daily tally and a chart against optional targets. (Opt-in.)

Diet & foods

Calorie logging the way it actually works: weigh the food, multiply by a per-ounce density — or skip the scale entirely and teach a food (or a whole meal) its typical serving. Each food’s number is confirmed once — after that it’s canonical and never re-guessed. One calories number, no macros. (Opt-in — its own module, separate from Metrics, though both share the calories metric.)

The day changes at 2:00 am, not midnight — a late snack at 1 am still counts toward the evening’s day. Days follow your timezone: the server adopts the timezone of your weather location (Settings → Weather), so set that if Fanad runs on a hosted box — the web Diet view warns you when the server’s clock and your device disagree. (The TZ environment variable overrides it.)

Medication

A logger, not medical advice. Medication is a calm “did I take it?” journal: you tell it what you take, tap when you take it, and see today’s doses and your streak. It records only what you type — it never guesses a dose, never offers drug or interaction information, and never suggests changes. For anything about your medications, ask your pharmacist or doctor. (Opt-in — its own module. Each med is tracked on its own, kept out of the general Metrics tally so it doesn’t clutter your numbers.)

The day changes at 2:00 am, not midnight, so a late bedtime dose still counts toward the right day — the same rollover Diet and the charts use. A reminder you set fires on the wall-clock minute you picked and only once a day, and it stays quiet once that template’s meds are already logged.

💊 Medication is an adherence journal, not medical advice, and never suggests doses. Talk to your pharmacist or doctor about your medications.

Journal & trends

A named daily checklist + note that Fanad reads back over weeks — its heaviest AI feature. Good for spotting slow problems: a food that doesn’t sit right, sleep that slips, even a pet’s on-again-off-again limp. (Opt-in.)

How-to: running a trend journal, start to finish

The journal only pays off as a small daily habit, so here’s the whole loop once, end to end — using the classic case it was built for: “is it the dairy?” (Swap in sleep, a medication, or your dog’s limp — the shape is identical.)

1. Turn it on: optin journal. (It’s per-person, like every module.)
2. Build the daily checklist as a template. File a task (“morning checks”), give it steps (step walk the dog · step no dairy breakfast · step meds), then save it: /template 1 morning-checks. Track whatever you want to correlate later — the “no dairy” item is the experiment.
3. Point a journal at it: journal new food, then journal template morning-checks. The steps are copied in — editing the template later won’t rewrite your journal.
4. Each day, two small moves: entry opens today (tap the boxes, or check 1 2), and the note carries the story: j note had dairy at lunch, headache by 3pm. Skipped a day? Fine — a gap is data too.
5. Let the nights do the heavy lifting. Fanad summarizes each finished day overnight, and weeks/months are built from those summaries — so the AI stays fast and cheap no matter how old the journal gets.
6. Read it back: journal week after a few days, journal month once it’s been running, and journal trends for the long look. Trends name their evidence (“headaches on 4 of the 5 days after dairy”) and stay tentative on thin data.
7. Act on it like a scientist, not a patient. A pattern is a hypothesis: tighten the checklist (“no dairy after noon”), keep logging, and take a real question to a doctor — or the vet, if the journal is journal new pepper and the mystery is the morning limp.

Honest by design: summaries and trends only ever describe what you logged — Fanad never invents days, and the not-medical-advice line is part of every trends reply on purpose.

Batches

Track each run of something you make again and again — a sourdough, a kombucha, a batch of soap. Write the directions once as a template; every run gets its own numbered checklist snapshotted from it, a dated log of how it went, and a closing verdict — so batch #7 can actually beat batch #3. A run is a working copy: tweak its steps as you learn, then batch save to graduate the winners into a new, auto-numbered recipe version that the next run starts from (a dud version can be rejected back out). No AI and no reminders: a batch only moves when you say so. (Opt-in.)

The whole loop, once: optin batches → file a task, give it steps, save it (/template 1 sourdough) → batch new sourdough → tick steps, batch log …, and batch add/edit/rm as you learn → batch save to keep the winning steps as the next version → batch done … to file the verdict. Each run refines the recipe; a dud version is batch reject-ed out. A batch is a run, not a recurring chore — there are no reminders, on purpose.

Home Assistant: ring the house

Home Assistant has no reminders of its own that survive a restart — Fanad does. With this module on, the timers and reminders you already set here also ring the house: a voice satellite speaks the ding, a script you name can flash lights or sound a siren, and your phone gets a push through the HA companion app. You can also talk straight to HA (ha turn off the kitchen light) and push a dated task onto a house calendar. Fanad never reads your house — no sensors, no presence; the house is an output, not an input. (Opt-in.)

Setup (owner, once): in HA open your profile → Security and create a long-lived access token; paste the HA URL + token in Settings → Home Assistant and pick the outputs — voice satellites to announce on, an optional script (it receives kind and title variables — wire a siren or lights there), and any companion-app notify services. For the calendar push, add the Local Calendar integration in HA first. The token is stored encrypted, like every other secret. Then optin ha and ha test.

Dashboards: let Home Assistant read Fanad

The other direction: GET /api/ha/summary is one read-only JSON bundle built for HA dashboards — open tasks, due today, overdue, cleared today, the next deadline and ding, plus a block per module you have on (calories today, journal entries, timers…). It carries counts and timestamps only: no task text leaves Fanad unless you add ?titles=1, because entity states flow into HA’s recorder, logbook, and whatever voice assistant you wired up. “Today” rolls at Fanad’s 02:00 logical day, not midnight. Pair it with a read-only token (Settings → Security → Terminal client tokens → tick Read-only, or fanad token --read-only) — that token can never post chat or change anything, so the credential sitting in your HA config is harmless. A minimal HA REST sensor:

rest:
  - resource: http://YOUR_FANAD_HOST:8787/api/ha/summary
    headers:
      Authorization: Bearer YOUR_READ_ONLY_TOKEN
    scan_interval: 300
    sensor:
      - name: Fanad tasks due today
        value_template: "{{ value_json.tasks.due_today }}"
      - name: Fanad overdue
        value_template: "{{ value_json.tasks.overdue }}"
      - name: Fanad next deadline
        device_class: timestamp
        value_template: "{{ value_json.tasks.next_deadline }}"

Live updates: GET /api/stream (SSE, same token) emits a counts event whenever these numbers change — poll on that instead of a timer if your integration can. The payload carries version: 1; the shape only changes with that number.

Speed Dial: give someone a few house buttons

Like the old phone speed dial. You (the owner) give another Telegram person a pad of numbers 0–9, and set each number to one specific Home Assistant command you write. They send the number — or tap it — and only that command runs. It’s how you hand a houseguest, a kid, or a roommate a handful of house controls without giving them the run of your whole Home Assistant. A person with a pad never gets the free-text ha <command> — their pad is their only line to the house, and since they only ever send a digit, their words never reach HA. (Owner-managed; needs the Home Assistant connection set up.)

Each person can be one of three kinds, your choice per account:

• Full account + pad — a normal Fanad user (their own tasks and chat) who also has the pad.
• Limited to speed dial — the account can do nothing but its 0–9 pad: no tasks, no chat, no other commands. Anything else they send just shows the pad again. A limited account also can’t vouch anyone in — the pad is its whole reach, so it can’t grow the guest list around its own limit.
• Local (no Telegram) — a household name, not a Telegram handle: for a family member who doesn’t use Telegram at all. A local account is a pad and nothing else — it’s always speed-dial-only, is never let through the Telegram gate, and is used entirely through its remote-control link (below).

Setup (owner): in Settings → Access, every allowed Telegram account is a row you can expand. Add a person by @username (they can then reach the bot), open their row, fill the numbers you want, tick Limit to speed dial only if you want them locked to it, and Save. You can program a pad before the person has ever messaged — it links to them on their first message. Numbers run against the one Home Assistant connection you set in the Channels tab, so set that up first. Each person’s row has a 🖨 Sheet button that prints a hand-out card of their numbers — give it to them like an old speed-dial card.

One button, on and off. A light usually needs two commands — one to turn it on, one to turn it off. Rather than spend two numbers on it, give a single number a second OFF command (the optional field beside the main one when you expand a row). That number becomes a toggle: press it to turn the device on, press it again to turn it off, and so on. Fanad remembers which way it’s set, so the number behaves the same everywhere — the Telegram digit, the tappable pad, and a shared remote-control link all flip the same light. Leave the OFF field blank and the number stays a plain one-shot. The Test off button beside Test lets you try the off command before you save, and a toggle is marked on / off on the printable sheet so the guest knows one button does both. (Fanad can’t read the device back from Home Assistant, so a toggle button never shows a live on/off state — it just alternates each press.)

Share a remote-control link (no Telegram needed). Speed dial is really for your guests, and a guest shouldn’t have to install Telegram to flip a light. In a person’s row, under Share a remote-control link, pick how long it should last (1, 7, or 30 days), optionally note who it’s for, and Generate link. You get a plain web link like https://your-fanad/r/… — text it to the guest and they open a simple page of just their buttons. No login, no account, no app. Tapping a button runs that same owner-authored command, so the link can only ever do what the pad can do — nothing else in Fanad, and still no free text to the house. The link expires on its own and you can Revoke it any time from the same row. (Copy the link when it’s shown — for your security it isn’t stored and can’t be shown again; generate a fresh one if you lose it. For a link to work away from your home network, set a Site URL in Settings → Security.)

Web login must be on. A share link lives at your Fanad address, and the promise is “only these buttons”. That only holds if everything else at that address is locked, so Fanad won’t generate a link until you’ve turned on web login (Settings → Security) — and a link stops working the moment login is turned back off, so a guest can never reach the buttons while the rest of the app is open.

Local accounts: house buttons for family without Telegram. Grandma isn’t installing Telegram, and she shouldn’t have to. In Settings → Access, switch the add-account row to Local (no Telegram) and type a name — grandma, not an @handle. That makes an account that is only a pad: fill her numbers like any other row, then generate her remote-control link and send it to her (or bookmark it on her phone’s home screen) — that link is how she uses it. Because the link is her whole way in, a local account is the one place you may pick Never expires when generating it; you can still revoke it from her row any moment, and removing the account kills the pad and every link with it. A local name never opens your Telegram bot to anyone — even a Telegram user with the very same @username stays a stranger — and the 🖨 Sheet card adapts its instructions for her (“open your link”, not “message the bot”).

Notebooks

Step into an isolated sub-space with its own tasks, notes, and lists — separate from your main one. Like a fresh account you can walk into and back out of. (Opt-in.)

Vouching people in

Fanad is invite-only by endorsement: anyone already in can vouch a friend in, and the record remembers who let in whom. (Opt-in — already on for the owner.)

Check-ins

Ask for a gentle, once-a-day nudge at a time that suits you — a check-in, never a stream of pings.

How the suggestions think

/whatdo isn't random. Fanad retrieves your own tasks, scores them on real signals, then lets the model pick one with an honest reason — and a "no" just reshapes the offer.

Mood, brain-state & sizing

Your mood steers how big a suggestion is, so a hard day gets an easier ask.

Reactions & the honest-by-design behavior

Fanad acks your message with a quick two-step reaction, and holds two promises: it never invents, and it lets stale tasks rest.

How do I get a chart or graph of a metric?

Turn Metrics on (optin metrics), log a few values with track or measure, then send chart <name> — the bot replies with a chart image of the last 30 days. Add one word for another range: chart water 7d, 90d, ytd, this_week, this_month. Tracked metrics draw a bar per day; measured ones a line of readings. See Metrics.

How do I put a task on my calendar?

Any dated task shows a 📅 /cal_N link — tap it (or send /cal 3) and Fanad hands you an .ics file that drops the task into your own calendar app. See Deadlines, reminders & calendar.

Can Fanad make a task repeat every week?

No — on purpose. There are no recurring tasks: recurrence is nagging, and nagging is stress. Instead, export the dated task with /cal and set the repeat in your own calendar, on your terms. See Routines without recurrence. If you make the same thing over and over (a bread, a brew) and want to track each run, that’s Batches — still no reminders, just a record per run.

How do I set a quick kitchen timer?

Turn the Timer module on (optin timer) and send timer 12 min pasta — a one-shot ding that never lands on your task list. Bare timer lists what's running; timer off 1 cancels.

Can I use Fanad in a web browser?

Yes — send /web to the bot and it mints a one-time link that opens the web UI already signed in as you. The host has to have web login and a Site URL configured; see Web login.

On a wide screen the web chat floats two quiet side panels in the space beside the column: a shortcut legend on the left (the single-letter commands plus the one-tap commands — tapping a letter drops it into the message box) and a status panel on the right with your module toggles, the task you’re working on, upcoming timers & reminders, and today’s notebook / mood / date. Both show only the modules you’ve opted into, and a single » button at the top right hides or shows the whole layer.

How do I let a friend or my partner use the bot?

Send vouch @their_username (turn the module on with optin vouch first). They get their own private account the moment they message the bot — your tasks stay yours. See Vouching people in.

Why do task numbers change between listings?

Numbers are just positions in the listing you're looking at — every fresh listing renumbers from 1. Act on the numbers (or buttons) of the latest listing rather than one from earlier in the chat.

Why did starting a task pause my other one?

Deliberate: one thing at a time. Starting a task automatically pauses whatever else was started, so "started" always means the thing you're doing now, not a pile of half-open threads. Changed your mind? unstart puts the started task back without finishing it.

Where did my old tasks go?

Anything untouched for about three weeks quietly goes to sleep — out of your listings and your suggestions, but never deleted. /sleeping shows them; /revive 1 brings one back. Snoozed something and want it back early? /snoozed shows what's tucked away; /unsnooze 1 wakes it. See Snoozing, sleeping & reviving.

How do I keep work and home separate?

Notebooks: notebook work switches you into a separate space with its own tasks, notes, and lists; notebook main takes you home. (Opt-in: optin notebook.) See Notebooks.

What's the fastest way to log what I ate?

With Diet on (optin diet): eat skyr 140cal logs it and teaches Fanad that a typical serving of skyr is 140 — from then on plain eat skyr is enough. Whole meals work too: save meal / eat meal breakfast. See Diet & foods.

How do I delete everything I've ever told it?

Send /requestdeletion — after a confirmation, your account and everything in it is erased. See Deletion, retention & data.

How can I see what the AI is actually doing?

Turn on the AI activity log (web Settings → AI connection) — it records every model call's purpose, prompt, raw reply, and timing so you can watch the thinking. Off by default; see Diagnostics & logs.

How do I ask the manual a question from chat?

Send /manual <your question> (or lead with the single letter h) and Fanad answers strictly from this book — if the answer isn't in here, it says so instead of guessing.