If you run Azynote on your own agent, you have been paying for it to wake up over and over. Every OnePager, every Smart Action, every one-liner starts your agent from scratch, waits for it to boot, asks one question, and throws the whole thing away. Do that six times after a morning of meetings and most of what you waited for was startup.
1.3.3 stops throwing it away.
Your agent, started once
There is a new ACP engine in Settings. It launches your agent a single time and keeps it running, so every request after the first skips the boot entirely and costs you only the model's own thinking time. The slower your agent is to wake up, the more obvious the difference.
It also unlocks something the CLI engine never could: the in-app chat panel, running on your own agent. With CLI, in-app chat is switched off and you talk to your workspace from your own terminal instead. With ACP you get the panel, with your agent behind it.
Setup is one field, and a shorter one than the CLI engine's. There are no placeholders to get right, because the protocol negotiates the prompt, the model and Azynote's tools between them. All you write is how to launch your agent: goose acp, cortex acp serve, gemini --acp, qwen --acp.
The honest caveat is that not every agent speaks the protocol. Claude Code does not, which is exactly why the CLI engine is staying rather than being replaced. If Claude Code is what you run, nothing here changes for you and nothing is being taken away.
Two things Azynote does not do over this connection: it never asks your agent for file or shell access, so it cannot read or write anything on its own, and it never touches your agent's sign-in. That stays between you and whoever you pay.
Tables that line up
A Markdown table is only readable if its columns line up, and that needs two things: a font where every character is the same width, and cells padded to match. Notes had neither.
Now they have both. Table rows render in a monospace font, so the pipes stack into columns, and when you paste a table its cells are padded for you. The header is bold, the dividing row reads as a rule under it, and the whole thing looks like a table instead of punctuation.
Old notes are not left behind. A note with a ragged table tidies itself the moment you open it. Opening a note still does not write to it, though, which matters more than it sounds: browsing your workspace does not quietly rewrite dozens of files behind you. The tidied version is saved along with your next real edit, and not before.
If a table is in the middle of being restructured, with a row that has more cells than its header, Azynote leaves it alone rather than guessing where your content should go. Tables inside code blocks are left alone too, because those are examples, not tables.
Lists that build themselves
Press Enter at the end of a list item and the next line already has its marker, at the same indentation. Bullets keep whichever character you chose, numbered items count up on their own, and a new checkbox always starts unchecked no matter how the one above it ended.
The part that makes it usable rather than maddening: Enter on an item you have not typed anything into ends the list instead of giving you another bullet. Two Enters and you are out, on a blank line, ready to write a paragraph.
Tab and Shift+Tab now indent and outdent, so nesting is something you press rather than something you count. They write spaces rather than a tab character, which is why indenting finally looks like it did something. Select several lines and Tab moves all of them.
Formatting that reaches your text
Cmd+1 through Cmd+4 turn a line into a heading. They were meant to before, and never once did, for two reasons stacked on top of each other. The app was claiming those keys for itself before the editor could see them. And on a French keyboard, where the digit row types & and é, they could not have matched even if they had arrived. Both are fixed, so they work now, on either layout.
While fixing that I found headings had a deeper problem: they were being treated like bold. Bold wraps a selection, which is right for bold and wrong for a heading, because a heading belongs to the line rather than to a run of characters. So you had to select the text first, and applying a heading to a line that already had one added a second marker instead of replacing it.
Headings, bullets, checklists and quotes now apply to the whole line. Put your cursor anywhere on it, mid-word if you like, and press the shortcut. Applying one replaces whatever the line already was, so Cmd+2 on an H1 gives you an H2 rather than a mess. Press the same one again to take it off. Quotes are independent of the rest, so a quoted list stays a quoted list.
Bold and italic got the fix everyone tries and nobody got: select the word and press Cmd+B again to unbold it. Before, you had to select the asterisks along with the word, and if you did not, you got ****hello****.
One last thing that looked much worse than it was. ***bold italic*** is valid Markdown, but the editor only recognised the first two asterisks and left the third looking like stray text. Your files were always fine. Now they look fine too.
Two shortcuts moved, and it is the same story behind both. The app was claiming Shift Tab and Cmd 1 through Cmd 5 globally, ahead of every text field, so nothing underneath could ever use them. Light and dark is now Ctrl+Tab, which frees Shift+Tab to outdent and to work as a backward tab everywhere in the app, which it never did. Navigation is now Ctrl+1 to Ctrl+5, which frees Cmd+1 to Cmd+4 for headings. The rule that falls out of it is worth remembering: Cmd acts on your document, Ctrl acts on the app.
A note can point at your media
Your session already holds the screenshots, audio and files you gathered during it. Until now they sat in the strip below the editor with nothing connecting them to the sentence they belonged to. You could say "see the screenshot" and hope future you knew which one.
Type @ in a note and the session's media appears in the same picker as your text snippets. It matches on any part of the filename, so you type screenshot rather than remembering that it is called Screenshot 2026-09-20 at 18.51.26.png. Pick one and you get a link to it.
Put your cursor inside that link and the media strip highlights the exact file it points at. The preview lives down there deliberately, rather than floating next to the reference, because a panel by the link covers the line you are trying to edit and renaming a link you cannot see is no fun at all.
If the file is gone, deleted or moved outside the app, the link is struck through in red right there in the note. You find out by reading, not by clicking and waiting for nothing to happen.
Two things this is not. It does not move or copy anything: the file stays where it is and the note points at it, so the same screenshot can be referenced from as many notes as you like. And it is scoped to the session the note lives in, so a note cannot yet reach into a different session's files.
Also in this release
- Your tasks are reachable from outside the app. Tasks live inside your OnePagers, and until now only the Tasks view could find one. Claude Desktop, Cursor and anything else connected to Azynote can now list your open tasks, tick them off and add notes to them, and the app updates as they do.
- The CLI engine is now just called CLI. It always ran whatever command you pointed it at, so calling it Claude CLI was misleading the moment you pointed it somewhere else. Your existing setup is migrated for you, nothing to redo.
- Names you paste keep their meaning. A line break or a quote pasted into a note title used to leave the file in a state where two parts of the app disagreed about what the note was called.
- Preset changes made from outside report what actually happened. Asking for a preset that does not exist no longer comes back as a success using the name you asked for.
- The Home screen loses its priority sort and its HIGH badge. Neither was ever filled in with anything, so neither ever changed what you saw. Better gone than pretending.
If you switch to ACP, I want to know which agent you pointed it at and whether the first request still feels slow or whether the wait really is gone. And if Ctrl+1 for navigation collides with something you use, tell me before it annoys you for a week. I read everything at support@azynote.com.