Get started

NotesQ

NotesQ is where your team writes down what it knows, and every Quox agent can read it.

Overview

NotesQ is where your team writes down what it knows, and every Quox agent can read it. It is the notebook layer of Brain2, Quox's knowledge layer, and part of the AssistantQ suite (InboxQ, Calendar-Q, Action-Q and NotesQ).

Maturity: Beta. Attachments are labelled early access. Everything under "Planned" below is not built yet.

Pricing: $19, a one-time purchase in the Quox store. Each AssistantQ plugin is bought on its own today; a bundle is planned.

What ships today

The NotesQ notebook: filters and collections on the left, a notes list with a pinned launch plan, previews and tags, and the plan open on a dark editing surface with a colour-coded toolbar.

Writing

The NotesQ editor in focus mode: Rich, Markdown and Read modes, text size controls, a colour-coded formatting toolbar, linked notes and a checklist.

  • A rendered editor by default: bold, italic, strikethrough, headings, bullet and numbered lists, checklists, quotes, code and links, with a toolbar and keyboard shortcuts.
  • Switch to raw Markdown or a clean Read view at any time.
  • Notes are stored as plain Markdown, so they stay portable.
  • Focus mode and collapsible panes.

Linking and finding

  • Link notes to each other with [[double brackets]], with an autocomplete. Backlinks show what links to the note you are reading. A personal note can link to a team note; your private notes never appear in a teammate's backlinks.
  • Search across notes. Related notes suggests notes on the same topic.
  • Notes are indexed by Brain2, so Quox agents can find them when answering.
  • Open a note in the Brain2 knowledge graph (requires the Brain2 graph plugin).

Organising

  • Collections, tags, pinned and archived notes.
  • Custom properties, such as type and status.
  • Org settings (org admins): autosave delay, a default collection for new notes, whether agents may edit notes or only read them, and how many revisions to keep. quox notes settings, or Settings in the dashboard.

Personal and team notes

  • Personal notes and team (org) notes are kept separate. A colleague cannot see your personal notes, and another org can never see yours.
  • Any org member can edit team notes. Only the author or an admin can delete one.

History, safety and evidence

  • Full revision history: restore any earlier version, even after a delete.
  • Edit-conflict protection: two people, or a person and an agent, editing the same note never silently overwrite each other.
  • Every create, edit, restore and delete is recorded as evidence (Quox's audit trail) without copying the note's content into the log.

The Notes-Q assistant

  • An assistant in the sidebar and in chat: ask it to find, read, summarise, create, edit, tag, restore or delete notes. It acts when you ask, every write is a new revision you can undo, and it asks before deleting.
  • Tell it "jot this down" and it saves a note (shared with your team unless you say it is private).
  • Research into a note: ask it to research something and it hands the question to the research agent, which searches the web with the model's own web search; the note is written with a Sources section. Works on Claude and OpenAI models, and says so if search is unavailable rather than writing from memory.
  • quox chat --agent notesq gives the assistant its note tools on Claude. A change you ask for yourself in your own terminal counts as your approval; a change an attached agent session makes on its own goes to Approvals.
  • Org admins set the agent edit policy: direct (it edits when asked), propose (a change it makes on its own arrives in Approvals as a line diff and runs only when you approve; when you ask it directly, your request is the approval, and a delete always asks), or read_only.

Approvals for agent edits expire after one hour. Approving a late one tells you it expired and that nothing ran.

Agent edits: see them, undo them

When an agent edits a note, a bar above it reads "Edited by an agent" with the time, a View changes link (line diff) and an Undo button, with Redo after an undo. Revisions record that an agent wrote a change, not which agent. History also has Compare with previous.

Reading surface

The note body sits on a dark slate under every theme. A-, % and A+ in the editor header scale the note text from 80% to 170% (the % button resets). The size is remembered per device, not per account.

Import and export

  • Import an Evernote export (.enex, attachments included), an Obsidian vault (.zip), a Notion export (.zip) or Markdown: the Import dialog in NotesQ, or quox notes import <file> --dry-run, then without --dry-run.
  • A dry run shows how many notes, which collections and tags, and any warnings. Importing the same file again skips notes already there.
  • Export any scope, collection or tag as a zip of Markdown: quox notes export --out notes.zip [--with-attachments].

Save from the rest of Quox

  • Save to notes on an InboxQ email (saved to your personal notes with the sender and date) and on any chat answer (titled with your question).
  • quox notes from-email <messageId> does the same for an email from the terminal.
  • Send tasks to Action-Q and Add to QuoxPlan in a note's details panel, or from the terminal: quox notes actions <id> sends a note's open checklist items to Action-Q, each linking back to the note; running it again skips items already sent.
  • quox notes promote <id> --stream <streamId> adds the note (title, link, excerpt) to a QuoxPlan stream.

Templates and scheduled notes

  • Built-in templates: daily, weekly, meeting, decision. Any note with template: true in its front matter is a template too (optional title_pattern, e.g. "Standup {{date}}").
  • {{date}}, {{weekday}}, {{time}}, {{week}}, {{year}} and {{title}} are filled in.
  • quox notes new --template daily makes one now. quox notes schedule add --template daily --at 07:30 --tz Europe/London makes one every morning, server-side; add --weekly fri for weekly. schedule ls | pause | resume | rm manage them.
  • A schedule never makes two notes for the same day or week. After 10 failures in a row it pauses itself and shows why.

Writing many notes at once

For agents and scripts working in a terminal session:

  • quox notes batch <folder|file.jsonl|-> writes up to 200 notes as one job. Without --yes it only shows what it would write. Every note is tagged with its batch.
  • quox notes batch-undo <batchId> --yes removes exactly the notes that batch made (each stays restorable).
  • quox notes split <id> cuts a note at its headings into separate notes and turns the original into an index linking to them.
  • In the dashboard, a note with two or more headings shows a Split section in its details panel (confirm lists the new notes, Undo split puts it back), and a note made by a batch shows Undo batch.

Views

The notes list switches between List, Table, Cards and Timeline (deep links: /notes?view=table, cards, timeline). Table sorts by any column; Columns adds your own properties. Cards group by collection, type or status. Timeline groups by day, using the last update or any date property such as due. Every view shows the notes your filters pick. On the command line, quox notes ls --props status,due adds property columns.

Keeping the notebook tidy

  • Suggested links (details panel, quox notes suggest <id>): other notes whose title this note mentions in plain text, with a Link action that turns the first mention into [[Title]], and related notes not yet linked, with Add to See also. Suggestions stay inside one notebook (team or personal).
  • Notebook health (Health in the notes sidebar, /notes?health=1, quox notes health): duplicate notes (identical, same title or very similar), old notes that other notes still link to, and broken [[links]].
  • The Notes-Q assistant can run both for you ("check the health of our notebook").

Skills

  • Propose as skill (details panel, quox notes propose-skill <id>): turns a how-to note of 50 words or more into a Quox skill. It lands as an experimental skill, outside the stable library, tagged with a link back to the note, and an automated safety check reviews it.
  • Skills folder (early access): the notes sidebar lists your org's skills, which open in the NotesQ editor (Markdown and Read). Saving a change goes through the same checked, versioned path as the Skills library, with history and revert. Skills are never copied into notes.

Attachments (early access)

Paste a screenshot, drag and drop files, or use the attach button. Images show inline and other files appear as downloads. Attachments are stored per organisation, up to 25 MB per file.

Command line

quox notes ls | show | new | edit | append | tag | duplicate | attach | attachments | download
          | search | facets | history | restore | rm | related
          | import | import-status | export
          | batch | batch-undo | split | suggest | health | propose-skill
          | templates | schedule
          | from-email | actions | promote
          | settings | scorecard

Example output:

$ quox notes ls --scope org
 ID          Title                               Scope  Collection   Tags
 47947fe7…   Q4 launch plan                      org    Projects     launch,planning
 60afe344…   Supplier review: Northwind Hosting  org    Suppliers    hosting,review
 333c57ef…   SOP: onboarding a new client        org    SOPs         onboarding
  🌌 BRAIN2 │ notes ls │ 5 of 5

$ quox notes schedule add --template daily --at 07:30 --tz Europe/London --collection Daily
  🌌 BRAIN2 │ schedule │ daily 07:30 Europe/London, template daily
id: nqs_9de68f232d692a35c0
first run: 2026-10-09T06:30:00.000Z UTC

Limits

  • No real-time co-editing. Conflicts are detected, not merged live.
  • Tables and raw HTML open in Markdown mode, not the rendered editor.
  • Deleting keeps history, so a deleted note can be restored. Erasing a note and its history for good (quox notes rm --purge) is human-only.
  • Writing a batch of new notes is command-line only for now. Splitting a note and undoing a split or a batch also work from the note's details panel (Split and Batch sections). Templates and schedules are also in the dashboard (From template in the notes sidebar, Scheduled notes in Settings), and so are Send tasks to Action-Q and Add to QuoxPlan (the note's details panel).
  • Obsidian import has run against a real vault (Obsidian's own Help vault, 179 notes). Evernote and Notion imports were tested on exports built to each app's documented format, not yet a real account export.
  • Voice capture ("note this") does not work on a Quox call yet: the voice bridge does not pass the caller's identity to NotesQ. The MCP tools have not been driven end to end.
  • In terminal chat the OpenAI branch gives the assistant no note tools; research needs a model with web search (Claude or OpenAI), not Gemini.
  • The agent-edit Undo bar has been driven on a command-line edit, not yet on an edit made in chat. The text size control is tested but was not clicked in a live browser. Save to notes on a chat answer, Send tasks to Action-Q and Add to QuoxPlan are unit-tested in the dashboard; the command line versions were driven live.
  • Attachments are early access, up to 25 MB per file.
  • Editing skills from NotesQ is early access and has not yet been run by a customer. A skill proposed from a note is experimental and is not reviewed by a person before it can run.
  • Related notes improves once a new note has been indexed.

Planned

None of this is built yet. Listed in roadmap order.

Next

  • Voice capture ("note this") proven end to end on a Quox voice call.
  • MCP tools for outside agents, driven end to end.

Then

  • Meeting notes created from Calendar-Q events, and a morning brief that cites your notes.
  • "+ Note" on reports.
  • A dashboard screen for bulk writing.
  • An AssistantQ bundle price.

Later

  • Search inside attachments.
  • Editing skills from NotesQ out of early access.
  • The assistant learning which of its proposed edits people accept.