01 — UPDATES
What changed
Every line below resolves to a real commit or a real row in the task tracker. If there is no evidence behind it, it is not here.
2026 — AUGUST
- coref7ee578 · ARCH-3
NORD answers sooner because a per-turn round-trip is gone
On every turn the agent fetched your settings through an extra network hop back to the website. That hop is gone: the agent now reads them directly.
- core064bd6b · GB-2
Scheduled tasks never run twice
When several copies of the agent are running, exactly one picks up the schedule. Previously the same scheduled task could start twice — and cost you twice.
- core0283751 · ARCH-4
Proof that your stored keys decrypt identically everywhere
The two languages NORD is written in now provably encrypt your stored keys identically, pinned by fixed test vectors — a mismatch there would have made your keys unreadable.
- core0332e1b · ARCH-6
The engine under NORD is split into readable parts
One very large file was pulled apart along its natural seams. Nothing visible changes for you; what changes is how fast a fault gets found and fixed.
2026 — JULY
- core9c78b7e · ARCH-1
The server now has a backup, and it has been restored
The machine NORD runs on had no backup at all. It has one now, and the restore was actually performed rather than merely documented.
- core33a50fb
The agent is pinned to a tested version
The agent core was loosely attached to the rest of the platform. It is now pinned to one specific tested version, so a different one can never go live unnoticed.
- coreeb9dcf9
A restart no longer interrupts your running work
If the server restarted mid-task your progress was lost. Progress is now recorded and the screen picks the thread back up.
- coreb814161
Approvals are matched precisely
Approving one action could previously cover a similar one. The check now also matches the action's arguments, not just its kind.
- core7433c2d
Charges can never be applied twice
If a charge against your balance failed and was retried it could land twice. Every charge now carries a lease that rules that out.
2026 — JUNE
- corefb52296
NORD runs on Claude, and says so
The underlying model is Claude. That is now stated on the site and in the app rather than left unnamed.
- core3b49166
Updating the agent no longer cuts off a running conversation
Reloading the agent cut things off too quickly, killing long-running work. That window is now much wider.
- core6be4f06
Your balance stays correct, even when something fails
Failed charges used to get stuck. They are now replayed properly, and a shortfall cannot build up silently.
- core09c4119
If a model fails you see it, and you pay for the right one
If NORD falls back to another model mid-turn, that is shown in the conversation and billed against the model actually used.
- corebf020a2
A slow connection no longer holds up your conversation
If a connected service does not answer it is skipped and your turn continues — with a note saying which service was skipped.
- core1f3b503
Faults are observed instead of guessed at
Measurement and error reporting now cover the whole chain, so a problem gets found before you report it.
- core13edc16
Connected MCP servers genuinely work
You could add an MCP server, but its tools were never discovered. That now happens at the start of each turn.
2026 — MAY
- core5bdb60d
Every user gets their own separated agent
Conversations, knowledge and memory of different users are strictly separated — your agent cannot reach anybody else's.
- cored69deda
NORD runs on its own server and bills per use
The agent now runs on its own infrastructure, and every turn is billed against real usage rather than a subscription.
- corea461dbd
NORD exists
First version of the platform: the marketing site, the agent site, and the link to the agent core.
The code behind NORD lives in a private repository, so commit references are text rather than links.