Beta Features

Beta means real and usable today, still growing. Each section says what's coming next so you know where it's headed — and what to ask for.

Usage (Beta) — Tools menu, ⇧⌘U

• What it shows — calls and tokens in/out across every conversation, by day and by model, plus the app's live memory footprint.
• Why Tokens in is so large — it adds up every call, and an agent re-sends the whole conversation on each call. A 20K-token chat over 300 calls is 6M tokens with nothing wrong. Look at Avg prompt (per call) and the counter in the composer — current prompt against the model's window — for the number that matters. Naseem keeps that small: finished tool work does not stay in the prompt, so a long task does not get heavier with every step. The total grows only with how many calls a task takes.
• Other agent tools consume the same way — they re-send the conversation on every turn too; most simply don't show the running total. From cache tells you how much of each prompt the provider served cheaply. High is good.
• Accuracy — token counts come from the provider wherever it reports them. Dollar estimates are switched off for now: subscriptions and cached tokens made them unreliable, and a wrong price is worse than none. They come back once they are right. Something look off? Tell us on the Naseem support page.

Rules (Beta) — Tools menu, ⇧⌘R · Pro

• What it does — runs a prompt on a schedule: on launch, hourly, daily, or weekly. Each rule keeps its own chat so you can read what it did. Plain-language prompts work: "Download the sales report to ~/Downloads; if it fails, tell me" or "Fetch today's top tech headlines and save them to ~/Naseem/Outputs/news".
• Approvals — anything that needs your OK waits in the approval sheet, and mirrors to your phone when the Telegram gateway is on. Run Now fires a rule immediately.
• From chat — ask the agent to "remind me every morning to…" and it drafts a rule; the editor opens pre-filled and saving is what arms it.
• Quiet unless it matters — turn on Only notify when something needs attention and the rule reaches you only on a finding: a backup that didn't appear, a job that produced nothing, a check that failed. All-clear runs stay in the rule's chat without a notification. A rule can't say "all clear" without actually running its check.
• Dry run — Explain, don't execute: Naseem inspects and describes what it would do but changes nothing, and approvals are forced on for that run. Use it once on a new rule to see what it will do, then turn it off.
• Weekly heartbeat — every Sunday at 9 Naseem sends one Telegram message for all quiet rules, numbers first: how many checks each actually ran, how many alerted, and whether any message failed to deliver. A rule that stopped shows ⚠️ did not run this week; if the heartbeat itself stops arriving, Naseem isn't running its rules. The counts come from each rule's run log over the last seven days — the same log the menu-bar popover and rules-status.json read, so the three can't disagree.
• Late, by the rule's own clock — the popover shows each rule's schedule next to its last run and tells three states apart: first run in 3h for a rule that hasn't had its first slot yet, catching up for a slot missed while the Mac was closed (the run fires at the next tick), and late, in orange, only for a slot missed while Naseem was running — overdue by half the interval, a daily rule at 36 hours. The menu-bar badge adds · late for that last case alone; the status file carries the state, the interval and the next slot.
• Status you can see — the menu-bar icon shows how long ago the last rule ran (⚠︎ when something needs attention); click it for each rule's last run, verdict and delivery. rules-status.json in your Outputs folder holds the same facts for scripts or a synced folder. No server involved — if the app is closed, the icon is gone, which is the honest signal.
• Example watchdog — daily at 9: "Check that ~/Backups has a file newer than 24 hours and not empty. If not, tell me which was the last one." With quiet mode on, you hear about it only on the morning something went wrong.
• Known limits — rules run only while Naseem is open; one due rule fires per minute, so a backlog after sleep drains gradually. Reacting to folder changes the moment they happen is what Kommanda's Rules do; Naseem's are scheduled checks.
• Coming next — run history per rule and background firing while the app is closed.