- Windows 11 x64 or ARM64.
- A Rust toolchain with the native target (
x86_64-pc-windows-msvcoraarch64-pc-windows-msvc). - Visual Studio Build Tools with the matching x64 or ARM64 C++ linker and Windows 11 SDK to build the native executable.
- Microsoft Scout, only when meeting context is wanted.
- For the optional on-device AI Tidy up: a Copilot+ PC or a supported GPU, the Windows App Runtime 2, and Developer Mode to register a local build.
Meeting context is optional. NoteIQ remains usable when Scout or WorkIQ is missing, unavailable, signed out, or unable to reach the WorkIQ service.
From an ordinary PowerShell window, this dependency-free helper detects native x64/ARM64, locates Visual Studio C++ tools, builds a locked release, verifies its architecture and GUI subsystem, and starts the executable:
.\scripts\rebuild.ps1When your current directory differs from the checkout containing the script, the helper asks whether to build the current directory, the script's checkout, or another directory. A blank answer cancels. The chosen directory must be a NoteIQ checkout root; its path is printed before updating, building, or launching. For an explicit choice without a prompt:
.\scripts\rebuild.ps1 -BuildDirectory D:\projects\note-iqQuit NoteIQ from its tray menu first. The helper refuses to build while NoteIQ
is running, never force-kills it, and does not launch after a failed build.
Windows cannot replace a running executable (Access is denied, OS error 5).
Closing the capture window only hides the process.
To fast-forward a clean main checkout before rebuilding and launching:
.\scripts\rebuild.ps1 -Update-Update refuses a dirty checkout or another branch; it never switches branches,
stashes, resets, or resolves conflicts. Without it, the selected checkout is built
without pulling. Use -NoLaunch to build only. The output stays in that checkout's
target\<native-target>\release\noteiq.exe; startup paths are not changed.
Run the helper from the checkout that your startup launcher uses to update that
executable.
From the repository root in a Windows developer shell with the matching architecture's C++ tools installed:
cargo build --release --features desktop -p noteiq-windows --target x86_64-pc-windows-msvc
& .\target\x86_64-pc-windows-msvc\release\noteiq.exeFor a native ARM64 build, substitute
aarch64-pc-windows-msvc in both commands. The Windows build runners used by
CI are windows-2025 for x64 and windows-11-arm for ARM64; each build must
verify that the produced executable matches its requested architecture.
When NoteIQ is running, press Win+Shift+N to show its capture window.
The toolbar next to the meeting list has three icon buttons: New note
(+, or Ctrl+N) safely finishes the current capture and begins a new one,
Open note (shown once the note is saved) opens its Markdown file, and
Settings (⚙) opens the settings panel. Hover over a button for its name.
Notes save automatically; Ctrl+S saves at once. The tray
menu provides Show, New note, and Quit actions. The app registers
noteiq://new for the current Windows user; a PowerToys Command Palette
command can invoke noteiq.exe new or the registered URI.
The equivalent noteiq://new/ form added by the Windows shell is also supported;
additional paths, query parameters, and fragments are rejected.
Closing the window with the Windows title-bar close button (×) finishes the
capture and hides the window; NoteIQ has no separate Close button. It keeps
running in the tray so the shortcut stays available. Use Quit in the tray
menu to exit. Tray actions wake the UI event loop directly, including while
the capture is hidden. Quit saves the capture first; if saving fails, the
window is shown with the error rather than discarding the note.
Running noteiq new (or opening noteiq://new) while a capture
is open brings that capture to the front without discarding its text; after
the capture is closed, it starts a fresh one.
After rebuilding or updating NoteIQ, use tray Quit and confirm the old process has exited before launching the new executable. Starting a second executable only forwards to the running instance; it does not replace it. If a terminal still opens during meeting lookup or an already-fixed tray action still fails, check the running process's executable path before rebuilding again.
The capture window uses a consistent light Fluent theme, including buttons, the meeting picker, and the editor, even when Windows uses dark app mode. Settings replaces the capture panel rather than taking space away from the note; at smaller window sizes its contents scroll while Done stays visible.
The window, taskbar, tray, executable, and noteiq:// links use the same
embedded NoteIQ icon. The build generates 16-256px Windows icon sizes from
apps/noteiq-windows/assets/noteiq.svg; no loose image files are needed at
runtime. If an older pinned shortcut still shows a generic icon after an update,
unpin it and pin the rebuilt executable again.
The window has no header or Save button. A single line under the note shows
the save status, such as Saved · 14:41, and turns red only for problems. The
meeting list shows the selected meeting or No meeting, with a green Now
tag while that meeting is in progress and a purple Transcribed tag when
Teams reports a transcript for it. A hint below it appears only when meeting
lookup has a problem; while a lookup runs, the list itself says Checking your
calendar….
Selecting a meeting opens its existing saved NoteIQ capture, if one exists in
the selected destination's captures/YYYY/MM history. The current draft is saved
under its original meeting before switching; a failed save leaves it open.
Without an existing capture, selecting a meeting attaches it to the current note
as before. When a saved note is already connected to a meeting, selecting a
different meeting asks whether to change the meeting on the current note or save
it and create a blank note for the selected meeting. Cancel keeps the current
note unchanged. Automatic attachment does not reopen files over your text.
Recurring meetings are matched by calendar identity and occurrence start, not by title or series identity alone. When several captures exist for the same occurrence, the most recently updated one opens; the other files remain intact. Occurrence timestamps retain fractional seconds so precise calendar starts match their saved captures. The currently open saved occurrence is never reloaded over unsaved text.
Reopening supports schema-4 captures with an editable ## Notes section.
Earlier literal-wrapper layouts report an error rather than being migrated
silently. Notes continues to the end of the file. Summary, Follow-ups, custom
properties and other content before Notes are preserved, and reopened notes keep
their original filename. External changes after reopening block save instead of
being overwritten. Reopened notes with erased text are retained on close to
avoid deleting refinements; newly created empty notes still delete on close.
A saved-note lookup failure stays visible through typing and autosave until you retry the meeting selection, choose No meeting, or close the capture.
Another app may already own Win+Shift+N. NoteIQ then shows "Win+Shift+N is
already used by another app" and keeps working without a shortcut. Open
Settings, type another shortcut such as Ctrl+Alt+N, and press Enter
or Done to apply it. NoteIQ accepts a letter, digit, or F-key combined
with Ctrl, Alt, or Win (optionally also Shift). F-keys can be used alone or
with Shift; Shift-only typing keys are rejected so normal typing keeps working.
If the new shortcut is also taken, the previous one stays active.
OneNote conflict. Desktop OneNote's "Send to OneNote" tray helper
(ONENOTEM.EXE) registers Win+Shift+N (new side note) and Win+Alt+N
(open OneNote). To release them, open OneNote, choose File > Options >
Display, and clear Place OneNote icon in the notification area of the
taskbar (stored as
HKCU\Software\Microsoft\Office\16.0\OneNote\Options\Other\RunSystemTrayApp = 0).
Then end ONENOTEM.EXE or sign out and back in, and restart NoteIQ. You lose
OneNote's side-note and open-OneNote shortcuts and its tray icon; select the
option again to get them back.
Portable tests and formatting can run in WSL:
cargo test -p noteiq-core
cargo fmt --all -- --checkThe Windows UI acceptance tests run natively on Windows. They use Slint's
testing backend, which needs the debug information that build.rs enables
only for debug builds:
cargo test -p noteiq-windows --features desktopBy default, NoteIQ writes Markdown under:
%USERPROFILE%\OneDrive - Microsoft\projects\personal-assistants\notes\captures\YYYY\MM\
Settings lets you select another single destination folder; NoteIQ
never writes to both. An alternate OneDrive Notes folder can be selected
when it exists.
Ctrl+S saves without closing; autosave runs after an 800 ms pause and at
least every 10 seconds during continuous typing. An empty saved note is
retained while editing and deleted when the capture is closed.
If the destination folder is unavailable, NoteIQ keeps your text and shows
Choose folder. It retries automatically after 5 seconds, doubling the pause
up to one minute, so the log is not flooded; Ctrl+S retries at once.
The Note filename setting names each note. The default,
{date}_{time}_{title}, gives names such as 2026-11-03_1415_project-review.md.
| Placeholder | Becomes |
|---|---|
{date} |
The capture's local date, YYYY-MM-DD |
{time} |
The capture's local time, HHmm |
{title} |
A safe slug of the attached meeting's name, else of the note's first non-empty line |
The .md extension is added automatically. Use {date}-{title} to match the
naming used by the vault's own captures. Settings shows an example name while you type;
press Enter or Done to apply it. A template is rejected, with an
explanation and the previous setting kept, if it is empty or contains a folder
separator, an unknown placeholder, unbalanced braces, a control character, a
character that Windows or Obsidian links cannot use (< > : " | ? * # ^ [ ]),
a leading or trailing dot, a reserved Windows name such as con, or could
produce a name longer than 120 characters. A template without {time} or
{title} is allowed: another note with the same name in that folder gets a
numeric suffix such as -2. A title that would form a reserved Windows name
gets a note- prefix.
A changed template applies to new notes, and to the open note if it has not been
saved yet. A saved note keeps the template it was first saved with, and notes
always stay in captures\YYYY\MM. When that template uses {title}, connecting,
switching, or disconnecting a meeting renames the open note, even if autosave ran
before WorkIQ found the meeting. The original date, time, folder, and note ID are
kept, and a collision gets a numeric suffix instead of replacing another note.
Typing alone does not rename a saved file. Obsidian links to a renamed file may
need updating; NoteIQ does not rewrite vault links or rename closed notes.
Meeting templates give meeting notes a starting structure. They are off by default; turn on Insert a template into new meeting notes under Meeting templates in Settings and choose the Default template. When a note is connected to a meeting, by choosing it or automatically, and the note is empty, the default template is inserted. Text you typed is never replaced. A template you have not changed counts as an empty note: it is not saved on its own, it moves with the note to another meeting, and choosing No meeting removes it. Once you edit it, it stays.
| Template | Sections |
|---|---|
| General meeting | Agenda, Notes, Decisions, Action items |
| 1:1 | Updates, Discussion, Feedback, Follow-ups |
| Customer call | Attendees, Context, Asks, Next steps |
| Stand-up | Yesterday, Today, Blockers |
While templates are on, the capture window shows a Note template list and Insert template below the note. Inserting replaces an empty note, or a template you have not changed, and adds the template after any text you wrote.
The built-in templates are read-only. Under Edit, choose New for a blank
template or Duplicate to start from a copy of the one shown, then name it and
choose Save template. Your templates can be renamed, edited, and deleted.
Use ### headings so the sections nest under the note's Notes heading: a
template with a # or ## heading, such as ## Notes, is rejected because it
would clash with the note's own sections and stop the note from being reopened. In
a template file edited outside NoteIQ, such headings are inserted as ###.
These placeholders are filled in from the meeting:
| Placeholder | Becomes |
|---|---|
{title} |
The meeting name |
{date} |
The meeting's local start date, YYYY-MM-DD (else today) |
{time} |
The meeting's local start time, HH:MM (else now) |
{organizer} |
The organizer's name |
{attendees} |
The invitees' names, comma-separated, without rooms or organizer |
Placeholders ignore case and spaces inside the braces. Saving a template with an
unknown placeholder such as {owner} is rejected with an explanation; other
braces, such as {} in code, are kept as typed.
User templates are Markdown files in the templates folder beside the settings
file, named after the template, such as Weekly sync.md. You can edit them in any
editor; changes apply to the next meeting note. A file whose name is not a valid
template name, or matches a built-in template, is ignored. If the default template
is deleted or cannot be read, new meeting notes use General meeting and the log
records why.
New notes use the vault's capture properties with an editable Notes section and are
marked noteiq_schema: 4. Notes written by earlier versions are never migrated
or rewritten.
The front matter starts with the vault's properties: kind: capture,
source: manual, from (a [[Name]] link to you, when known), date,
captured (with milliseconds and UTC offset), processing: raw,
ai_refined: false, status: inbox, and tags (capture, note, plus any of
yours). ai_tidied: on-device follows ai_refined while the Notes text holds an
accepted Tidy up. With a meeting attached, meeting, meeting_start, meeting_end,
organizer, your_rsvp, the invitee lists, and calendar_event_id follow.
NoteIQ's bookkeeping comes last: id, updated, timezone, captured_via
(shortcut, tray, cli, uri, or new_note), and noteiq_schema.
The body starts with a # Title (the meeting name, else the note's first line,
else "Quick note"), a From and Captured line, and a comment explaining
how to refine the note. With a meeting attached, Meeting details lists the
time and duration, organizer, your RSVP, and invitees. Empty Summary and
Follow-ups sections are left for later refinement, and your text is kept
verbatim under Notes as ordinary Markdown, with no collapsed HTML wrapper or
generated code fence. Lists, checkboxes, links, and formatting remain editable in
Obsidian's Live Preview. Finish the capture in NoteIQ before editing its file in
Obsidian, since NoteIQ continues autosaving an open capture.
Titles and calendar text are escaped so they display literally.
from uses your Windows display name, looked up in the background when NoteIQ
starts. To use another name, set author_name in the settings file. If the
lookup finishes after the open note was saved, that note is updated; closed
notes are not, so later vault edits are never overwritten.
Invitees are flat quoted "Name <email>" strings in required_invitees and
optional_invitees, which are written as [] when empty; resource_invitees
and other_invitees appear only when needed. Missing names or addresses are
not invented. Meeting times use your Windows time zone, including the correct
offset when a meeting spans a daylight-saving change.
your_rsvp is accepted, tentative, declined, not_responded, or
organizer, and is omitted when unknown. Under Meeting details, each invitee
shows their RSVP and, when WorkIQ reports it, "attended" or "did not attend",
based only on WorkIQ's explicit hasAttended field. This is a snapshot of
reported attendance, not a live indication that someone is currently in the
call; accepting an invitation does not prove attendance. Some meetings omit
attendance or RSVP details.
Settings are kept in %APPDATA%\DevSecNinja\NoteIQ\config\settings.toml, which
is created the first time you change a setting. If its TOML cannot be parsed,
NoteIQ first preserves the original in a unique settings-*.toml.bak file
beside it, then shows a recovery message and uses defaults. A backup or read
failure stops startup rather than allowing defaults to overwrite unreadable settings.
Besides the options in
Settings, it accepts author_name and meeting_reminder_delay_minutes (see
Note reminders after meetings). A hand-edited note_filename that is not
valid falls back to the default, and the log records why without the template
text.
Tidy up rewrites a short note more concisely with the language model built into Windows. It runs on this PC, using the NPU on Copilot+ PCs, so the note is never sent anywhere. It is off until you turn on Offer Tidy up for short notes in Settings, which also shows whether this PC can run the model.
Selecting the Tidy up toolbar button never changes the note directly:
- While the model runs (about 5 seconds), the note is read-only and Cancel stops it.
- A review panel shows every change: removed text struck through in red, added
text underlined in green. Changed spaces, tabs, and line breaks show as
·,→, and¶. Check before applying lists changes that may alter facts: numbers or names that were added or removed, a lost or added "not", hedges such as "??" or "maybe" that now read as certain, a lost "me" or "I", added symbols such as "$", or a much shorter result. These checks do not catch every change in meaning; read the highlighted text too. - Apply replaces the Notes text and adds
ai_tidied: on-deviceto the front matter. Discard or Esc keeps the note as it was. - After applying, Undo tidy-up or Ctrl+Z restores the note and removes
ai_tidied. Once you edit the tidied text, the link becomes Restore note from before tidy-up, which also discards those edits, and Ctrl+Z returns to undoing your typing. Undo lasts while the note is open; after that, use OneDrive version history.
Only notes up to 700 characters can be tidied: in testing, longer notes were
more likely to have facts merged or changed. Windows detects the note's language
itself and can reject very short lowercase notes full of abbreviations, such as
"deal alm closed", even when they are English; capitalizing names and acronyms or
writing a full sentence usually helps. Windows may add an invisible
AI-generated text marker (U+200B U+034F U+2060 U+200B) to the result; NoteIQ
keeps it and ignores it when comparing.
Windows only lets apps with a package identity use its on-device model, and the model needs a Copilot+ PC NPU or a supported NVIDIA or AMD GPU. Release ZIPs are not yet signed, so give a local build its identity:
-
Turn on Developer Mode in Settings > System > For developers.
-
Install the Windows App Runtime 2 if needed:
winget install Microsoft.WindowsAppRuntime.2. -
Build NoteIQ, then register its folder:
.\scripts\rebuild.ps1 -NoLaunch .\scripts\register-package.ps1
-
Quit NoteIQ from the tray menu and start it again.
The registration covers the build folder, so rebuilding in place keeps it.
cargo clean deletes the package files under target; rerun the script
afterwards. Run .\scripts\register-package.ps1 -Unregister to remove it.
NoteIQ works as before without a registration; only Tidy up is unavailable.
NoteIQ checks Scout's bundled WorkIQ executable for the native Windows
architecture first (win-x64 or win-arm64), then tries the other bundled
architecture if needed. A configured executable path takes precedence. The
corresponding native ARM64 path is:
%LOCALAPPDATA%\Programs\Microsoft Scout\resources\app.asar.unpacked\node_modules\@microsoft\workiq\bin\win-arm64\workiq.exe
The corresponding x64 path is:
%LOCALAPPDATA%\Programs\Microsoft Scout\resources\app.asar.unpacked\node_modules\@microsoft\workiq\bin\win-x64\workiq.exe
It invokes that executable in the background without opening a terminal window, using the MCP stdio interface. NoteIQ does not install, download, or copy WorkIQ. If no compatible executable is found, or its MCP schema does not expose a compatible Meetings search, the meeting hint explains that context is unavailable; note editing and saving continue to work. Meeting retrieval also needs the connectivity and authentication required by Scout/WorkIQ.
Repository-local .github/workflows/ci.yml runs portable formatting, strict
Clippy (-D warnings), and core tests on both
ubuntu-24.04 and ubuntu-24.04-arm. Desktop Clippy and tests run on
windows-2025 (x64) and windows-11-arm (ARM64). A separate build job calls
the repository's reusable build-windows.yml for both targets and verifies
each executable's architecture. Shared lint, configuration-sync,
Release Please, labeler, label-sync, and assign-issue-to-codeowners automation
must reuse workflows from DevSecNinja/.github, referenced by immutable,
pinned commit SHA. The shared lint workflow retains its default non-blocking
behavior; the Rust checks in local CI are strict gates. There is no suitable
central Rust workflow, so the repository-local CI and Windows build workflows
provide the Rust-specific jobs.
release-please-config.json manages a virtual workspace release using the
simple release type, initially 0.1.0. Its configuration updates the root
Cargo.toml and workspace package versions in
Cargo.lock as extra files, creates a draft GitHub release, and enables
force-tag-creation. The local .github/workflows/release.yml runs on v*
tags or by manual tag retry, builds both architectures from that exact tagged
commit through the local reusable build-windows.yml, verifies each
executable's architecture, and packages each ZIP with noteiq.exe,
README.md, and LICENSE. It also publishes a CycloneDX SBOM per architecture,
a .sha256 checksum file per asset, and GitHub attestations, and adds a
Download section to the release notes with direct links to both ZIPs. The
section starts with a <!-- noteiq-downloads --> marker, so a retry replaces it
instead of adding a second copy. Publishing may only
complete an existing draft created by Release Please; it must not create a
separate release. The central release-publish workflow is not suitable because
it creates a release with gh release create instead of uploading assets to
and finalizing the existing Release Please draft.
Setting skip-github-release: true would skip the Release Please release/tag
creation rather than make the draft available for this publisher, so keep it
false.
For a manual retry, dispatch the workflow on the existing release tag, not on
main. The requested tag must already have an unpublished Release Please
draft:
gh workflow run release.yml --ref v0.1.0 -f tag=v0.1.0The tag-bound dispatch is required by the workflow's provenance guard, which checks that the workflow ref is the same tag as the requested release source. The workflow also checks the tag version and ancestry before building.
Before enabling Release Please automation, install the GitHub App
(App ID 3563533) for this repository. Set the repository variable
RELEASE_PLEASE_APP_ID and repository secret
RELEASE_PLEASE_APP_PRIVATE_KEY, and enable Settings > Actions > General >
Workflow permissions > Allow GitHub Actions to create and approve pull
requests. Confirm Renovate covers the newly referenced reusable workflows.
These are required operator setup steps and must be completed by a repository
administrator before the Release Please workflow can run. They have not been
configured or validated here.
Local validation completed for the implemented workflows: x64 Clippy, full
tests, and release build passed under emulation; ARM64 Clippy, full tests, and
release build passed; WSL Clippy and full tests passed. The produced Windows
executables were verified as PE machine 8664 (x64) and AA64 (ARM64).
yamlfmt -lint, yamllint, actionlint, and zizmor --offline passed.
A source-only Gitleaks scan found no leaks. The release packaging script was
exercised offline with both real executables: ZIP contents, PE machine IDs, and
SHA-256 checksums all passed. Release guard checks rejected malformed tags,
workflow-ref/provenance mismatches, and attempts to edit a published release.
The ZIP packaging uses Python's standard library and does not require an
external ZIP utility. PR #5 has also passed hosted Linux x64/ARM64 checks,
Windows x64/ARM64 tests and both release artifact builds. Release publication
has not been exercised; the app credentials and repository setup below remain required.
After downloading a release archive, compare its hash with the matching
.sha256 file:
Get-FileHash .\noteiq-v0.2.0-windows-x64.zip -Algorithm SHA256
Get-Content .\noteiq-v0.2.0-windows-x64.zip.sha256GitHub CLI can verify the artifact's provenance attestation (replace the archive name with the ARM64 package when appropriate):
$repo = gh repo view --json nameWithOwner --jq .nameWithOwner
gh attestation verify .\noteiq-v0.2.0-windows-x64.zip --repo $repoEach ZIP also has a CycloneDX 1.5 SBOM, such as
noteiq-v0.2.0-windows-x64.cdx.json, listing the Rust crates compiled into that
noteiq.exe with their versions, licenses, and package URLs.
scripts/release_sbom.py generates it with cargo-cyclonedx and keeps only the
crates that cargo tree -e normal,no-proc-macro reports for the release target,
so crates used only by tests, build scripts, or proc-macros are left out. The
release workflow attests each
SBOM against its ZIP:
gh attestation verify .\noteiq-v0.2.0-windows-x64.zip --repo $repo --predicate-type https://cyclonedx.org/bomTo generate the SBOMs locally, install the version pinned in release.yml
(cargo install --locked cargo-cyclonedx --version 0.5.10) and run
python scripts/release_sbom.py --tag v0.2.0 --output sbom.
The checksums detect accidental corruption, attestations verify provenance, and the SBOM lists the components; none of them is code signing. Releases are not Authenticode-signed, so Windows SmartScreen may still show an unknown-publisher warning.
The Meeting list at the top of the note shows which meeting is attached. Its
first entry is always No meeting; the others are retrieved meetings, each
on two lines. The start time sits in a column on the left, the title on the
first line is shortened with "…" when it does not fit, and the second line adds
details such as Now, Transcribed, ends 15:00, In 1 h 20 min, Ended 10:00, or the
day for other dates, followed by the length, Tentative when you replied
tentatively, the organizer, and the number of people invited. Earlier meetings are
shown in grey. Screen readers hear the title, date, and time, for example
Project review · 04 Nov · 14:00–14:30, followed by the details. Meetings in
progress come first, then earlier meetings (most recent first), then upcoming
ones. Declined and cancelled meetings are not listed, although a meeting already
attached to the note stays listed even if a later lookup no longer returns it.
Refresh meetings is always the last entry, pinned below the meetings.
Choosing an entry attaches it at once unless a saved note is already connected to another meeting, in which case NoteIQ asks whether to change the meeting on the existing note or create a blank note for the selected meeting. Choosing No meeting removes all meeting and invitee fields from the saved note without changing its text or ID. With the picker focused, Enter, Space, or an arrow key opens the list. In the list, the arrow keys move between entries, Enter chooses one, and Escape closes it without a change. Each change is saved after the usual 800 ms autosave pause.
NoteIQ attaches a meeting automatically only when exactly one timed meeting is in progress and Connect to my current meeting automatically is on. All-day events are never attached automatically, and an RSVP is not treated as proof of attendance: if meetings overlap, the note stays on No meeting until you choose one. Your own choice, including No meeting, always wins for that note; neither Refresh meetings nor a later lookup replaces it. Choosing the meeting that was attached automatically confirms it in the same way. New note starts again with automatic selection.
While the window is open, NoteIQ re-checks the cached list every minute without contacting WorkIQ, so a note can pick up a meeting that starts while you write:
- An empty note attaches to the meeting in progress, and an empty note that was never saved moves on to the next meeting.
- A note with text attaches only to a meeting that started no later than 15 minutes after you opened the note, so earlier writing is not filed under a later meeting.
- Once a note has text or a file, an automatically attached meeting stays, even after it ends or another meeting begins.
Nothing is attached automatically while the last lookup has failed. Turning automatic connection off keeps the meeting that is already attached.
While a lookup runs, the closed list shows Checking your calendar… when no meeting is selected, and Refresh meetings shows the same text and waits; cached meetings stay usable. A hint below the list appears only for problems:
| Hint | Meaning |
|---|---|
| Meeting lookup unavailable. WorkIQ comes with Scout. | Scout's WorkIQ executable was not found |
| Couldn't refresh meetings. Showing earlier results. | The lookup failed; earlier results remain |
Other lookup problems, such as needing to sign in to Scout, are explained in the same place. Save progress and save errors appear in the status line under the note instead.
WorkIQ returns a limited number of results per search, so NoteIQ asks for meetings happening now, starting in the next hour, and today in one lookup and merges the results. WorkIQ reports clock times in UTC; NoteIQ converts them to your Windows time zone.
The meeting list is cached in memory for the life of the tray process. New note, Ctrl+N, and reopening a closed capture reuse it immediately and re-evaluate which meeting is current. WorkIQ is asked again when NoteIQ starts and when you choose Refresh meetings. Opening a capture or changing the automatic connection setting also asks again when the list is more than five minutes old or the last lookup failed. A lookup that is already running is reused, meetings missing from a newer result stay in the list, and a failed refresh leaves the list usable with an explanation. No calendar cache is written to disk.
When the installed WorkIQ exposes a compatible fetch tool, NoteIQ also retrieves
calendar invitee RSVP details. This optional step has a shared 15-second timeout.
If it fails, the note still uses the available retrieval data and unknown statuses;
diagnostics record the failure without names or email addresses.
Markdown files are saved in OneDrive or an Obsidian vault, but that alone does not guarantee immediate indexing by WorkIQ. Indexing and query availability depend on the user's Microsoft 365 and WorkIQ configuration.
When Suggest a note after untranscribed meetings is on (the default), NoteIQ shows a Windows notification a few minutes after a meeting ends without a Teams transcript: Write a quick note for {meeting}?, with the time and organizer, and Write note and Dismiss buttons. Write note, or clicking the notification, opens a note connected to that meeting, or the meeting's saved note if it already has one. A note you are writing is saved and closed first unless it is empty. Notifications follow Windows settings such as Do not disturb, and stay in Notification Center until dismissed.
- The delay is 5 minutes, set by
meeting_reminder_delay_minutesin the settings file (at most 60). The transcript status is checked with a WorkIQ lookup that starts after the delay, so a transcript that appears shortly after the meeting ends still counts. - WorkIQ reports
isTranscriptAvailablefor Teams meetings. When it does not say, NoteIQ still suggests a note. - Only meetings you were in a Teams call for on this PC are suggested. While a
meeting is in progress, NoteIQ checks every 30 seconds whether Teams is using
a microphone; Teams keeps it open for the whole call, even while you are
muted or joined with Don't use audio, as in a meeting room. Calls joined
in a browser or on another device, and in-person meetings, are not detected.
When meetings overlap, all of them count as joined. Reminders wait until you
leave the call, for example when a meeting runs over, and while NoteIQ cannot
tell whether you are in one. The two-hour limit then counts from the end of
the call. Calls are kept for a day in
meeting-reminders.json, so a restart does not lose them. - There is no reminder for cancelled, declined, or all-day meetings; for calendar blocks you organized with nobody invited, such as lunch; for the meeting connected to the open note; for meetings that already have a saved note; or for meetings that ended more than two hours ago, for example before NoteIQ started.
- Each meeting is suggested once. Shown reminders are remembered for seven days
in
meeting-reminders.jsonbesidesettings.toml, so restarting NoteIQ does not repeat them. A reminder Windows could not show is tried up to three times.
While reminders are on, NoteIQ looks up meetings in the background every 30 minutes, and every 2 minutes while a reminder waits for a fresh transcript status. Turning the setting off stops reminders and these lookups at once. Separately, while a meeting is in progress and the capture window is open, NoteIQ looks up meetings so the Transcribed tag follows the call. Choose how often with Check meetings during calls in Settings: every 5, 10 (the default), 15, or 30 minutes, or Off. Each check starts WorkIQ and searches your calendar, so shorter intervals cost more lookups.
Remind me when a call I joined isn't transcribed controls a reminder during calls. It is saved now and takes effect once that reminder ships (#26).
NoteIQ is not a packaged app, so it registers the notification sender under
HKCU\Software\Classes\AppUserModelId\DevSecNinja.NoteIQ with its name and
an icon copied to %LOCALAPPDATA%\DevSecNinja\NoteIQ\data. The buttons open
noteiq://reminder/<id> links, which reach the running NoteIQ, or start it.
Rolling logs are stored under:
%LOCALAPPDATA%\DevSecNinja\NoteIQ\data\logs\
They include operation type, elapsed time, failure class, and a correlation
ID. They intentionally exclude note text, meeting titles, invitee names and emails,
credentials, and raw WorkIQ responses. The app retains recent log files for up
to 14 days. For more detail, start NoteIQ with RUST_LOG=noteiq_core=debug
set in the environment.
Meeting searches share a 45-second limit, with up to 15 additional seconds for optional RSVP details. Each handshake request has its own 15-second limit.
If meeting lookup fails, open the meeting list and choose Refresh meetings to retry, confirm Scout is installed and signed in, and verify network access. If a folder is unavailable or unwritable, select another destination in Settings; NoteIQ does not silently switch folders.