Changelog

Approving a paid step now continues the very conversation that asked, in the chat where you were asked. Say no, or let it expire, and you get one line back either way.

Ask about something from weeks back and Nova finds and quotes it, searching every conversation by meaning as well as by exact words. The search runs entirely inside your own agent.

On Telegram, replying to a message now continues the conversation that produced it, including a scheduled report. Use /new for a fresh conversation, /threads to list them, and /here to see where you are.

Your dashboard can now open the conversations that happened elsewhere, like Telegram chats and scheduled runs, and continuing one no longer splits it in two. Your conversation list is cleaner, and paid steps show their cost again.

Tools that could be found but not used now work, and when a tool needs a detail Nova doesn't have, it stops and asks instead of making a call that would fail.

Nova now searches the tool library in plain words and gets ranked matches with price and typical speed. Searching and reading a tool's details are free.

Nova now always knows today's date and time, and introduces itself properly.

When Nova uses a paid service, the trace now names the service and shows the price, so a charge on your bill is something you can recognise.

Every paid step now shows what it cost you, right in the trace.

Maintenance and reliability improvements.

Changing a setting or installing a skill restarts your agent to pick it up. The Logs view now shows that as a normal restart, so a real problem still stands out.

Fixes an issue where a freshly installed skill wasn't picked up until the agent restarted. New skills now work the moment they land.

Type / and pick the skill you want; Nova follows it from its first move. The same commands work on Telegram, in the chat on your agent, and in the dashboard.

Nova now reads a skill's full procedure only when it needs it, which makes messages cheaper and keeps it focused. It can also save a procedure you taught it as a skill of its own.

Skills you pick in the dashboard now land on your agent automatically. Install, update or remove one, and the agent always ends up matching exactly what you chose.

Skills you pick in the dashboard now land on your agent automatically. Install, update or remove one, and the agent always ends up matching exactly what you chose.

Skills you pick in the dashboard now land on your agent automatically. Install, update or remove one, and the agent always ends up matching exactly what you chose.

Skills you pick in the dashboard now land on your Nova automatically, and always end up matching exactly what you chose.

The Files area works again.

Every action in the chat's Files area — list, upload, rename, delete — was failing with a permission error, so the area was effectively dead. Signing in now covers your files too.

The create, rename and delete dialogs are also real dialogs now: the name is checked before anything happens, Enter confirms, a rename keeps the file extension, and a delete tells you exactly what it's about to remove.

Merged in #33. Three faults behind one symptom: Nova answering "I don't see an attachment yet" to
a message that visibly had one.

It was never sent

assistant-ui does not merge attachment parts into message.content. The composer builds
{ content: [text], attachments: [...] } and each attachment keeps its own content. The code that
collected files for the send scanned message.content, so it found nothing — every time, in both web
chats, for as long as attachments have existed. Only the Telegram file path ever worked.

It failed silently, which is why it lasted: the chip renders, the send succeeds, the model simply
never receives a file.

Only some files could be attached

The stock adapters took images plus a handful of text types, and turned the latter into an
<attachment name=…> blob of TEXT — which can never be written back to the drive as the file it came
from. One NovaAttachmentAdapter now accepts any file (4 MB each) and carries it through with its
real filename and MIME type.

A web upload never reached the drive

Telegram stashed uploads into inbox/; the web composers did not. A file sent from a browser lived
only inside one chat turn — Nova's own tools had nothing to open, and "save this in my files" had
nowhere to save to.

orchestrate now stashes for the owner and tells the model the path, exactly as the Telegram path
does. Two exclusions, both deliberate:

• Federated callers — a peer mesh's payload is not the user's drive.
• Telegram — it keeps doing its own, because it needs the "saved at inbox/…" note inside the
  text it persists before the run starts. It signals this with a {nova:"inbox"} data part rather
  than a flag on the call, so the fact travels with the message and a retry or replay cannot write
  the same file twice.

Also

Reloading a chat that had an attachment crashed the page (createObjectURL: Overload resolution failed) — a persisted transcript rehydrates file from JSON as a plain object, not a File.

Upgrade: no config or data changes. Web uploads begin appearing under files/inbox/.