What shipped, and when
Each entry groups the commits behind one change you would notice. Newest first. The full history is in the commit log.
AI App Sign-Ins Name Only Kamari
When an AI app signs in to Kamari and says which service its access is for, Kamari now refuses any service other than its own AI connection, instead of quietly issuing access anyway. Apps that do not say, and apps that name Kamari, sign in as before.
Other Sites Cannot Reach Your AI Connection
Kamari now refuses any request to its AI app connection that a web page on another site started, so a page you visit cannot use it through your browser. AI apps that connect directly, such as Claude Code, work as before.
AI Apps See New Tools Without Reconnecting
When you give a key or app another tool, or an update changes a tool, Kamari now tells a connected AI app that its tool list changed, so an app that listens can fetch the new list without you reconnecting it. The notice names no tools and reaches only that key or app.
Agents Keep Their Name After Reconnecting
An AI agent that comes back with a new sign-in, such as Claude on your phone, can move its name and inbox to the new sign-in with agent_manage, so it no longer needs a new name. Only names under your own account can be moved. When a key is deleted, its agent name is freed, without its old mail.
Outside Messages Cannot Make Automations Act
A syslog line, a webhook call or a Telegram message from a stranger can still start an automation, but that run may only use read-only tools unless you allow it on the automation. Syslog now accepts messages from this machine only, until you set its listen address and allowed networks.
Forgery Cookie Stays on HTTPS
The cookie that stops other sites from forging dashboard changes is now marked HTTPS-only whenever you reach Kamari over HTTPS, so it is never sent in the clear. The check also covers a few more addresses that only looked like the sign-in pages.
Narrow Keys Cannot Read Other Results
A tool's result now goes back to the key, app or session that started it. A key you limited to a few tools can no longer read, or use up, the one-time secret in a result your full session or another key started, unless that key may run the same tool itself.
Automation Tools Cannot Be Taken Over
Each automation is also a tool an AI app can start. Another user can no longer take over your automation's tool by giving their own automation nearly the same name: a name that differs only in case or punctuation is refused, so a call meant for your automation always runs yours.
Older AI Apps Keep Their Connection Private
AI apps that use the older streaming connection to Kamari now get a private one. Only the key or app that opened it can send requests into it, so another user can no longer slip answers into your assistant. The audit log no longer shows the connection's secret name.
Automations Cannot Be Planted Through Settings
The general settings editor can no longer read or change the stored list of automations or their run history. Automations are created and changed only on the Pipelines page or through its own tools, which always record you as the owner, so permission to edit settings no longer lets anyone add an automation that runs tools.
Limits On Apps Registering Themselves
AI apps can still register themselves with Kamari, but now only 10 times a minute from one address, with small registrations, and at most 100 waiting to be used. A registration nobody signs in with for 7 days is removed. Apps you already connected are not affected.
Limited Keys Stay Limited Inside Plugins
An API key or sign-in token with limited permissions is now held to those limits inside plugins too. It no longer borrows its owner's extra rights to see other users' work items, memories, mail settings or automations, or to run Review tests. An automation saved with a limited key never runs more than that key allowed.
Live Streams Need The Same Permissions
The live log, message and metric streams now need the same permission as their pages, and the audio bridge has its own permission. A signed-in browser can only open them from Kamari's own address, so another site cannot listen in. Oversized audio frames are refused.
Add A Passkey On Your Phone
My account and the passkey invite page now have a second button for adding a passkey on your phone. Your browser shows a QR code; scan it with the phone, with Bluetooth on for both devices, and the passkey is saved on the phone. The usual button still lets your browser offer every choice.
Logs, Metrics And Plugin Lists Follow Permissions
Reading plugin logs now needs the logs query permission and reading raw metrics needs the metrics query permission, the same ones their tools use. The Review page needs permission to list test cases. The plugin list and the About page show only plugins you have permission to use, and the built-in API documentation pages are switched off.
See Where Each Passkey Lives
My account and the admin Users page now show, for each new passkey, whether it is built into a device or on a security key or phone, how it connects, and whether it can sign in without a username. You can also name a passkey when you add it. Older passkeys show these details as not recorded.
Passkey Sign-In Keeps Accounts Private
Signing in with a passkey no longer uses a typed username, and starting a sign-in answers the same for everyone, so nobody can use it to find out which accounts exist or have passkeys. An old passkey that only worked after typing your username must be added again from My account.
My Account Page For Every User
Every signed-in user now has a My account page. You can see, add and remove your own passkeys, turn phone sign-in on or off, and see how this session signed in. Removing a passkey needs a passkey sign-in, and your last passkey cannot be removed.
Phone Page Explains A Missing Passkey
When you scan a sign-in QR code with a phone that has no Kamari passkey, the approval page now says so plainly instead of leaving only the phone's own message. It tells you how to add a passkey saved to the phone, or to use a security key, and links to where passkeys are added.
Web Endpoints Closed By Default
A sign-in, API key or token now reaches only public pages, endpoints needing a permission it holds, and endpoints that answer only about its own records; other web requests are refused. Live update streams still check only the sign-in and come next. The admin account's dashboard keeps working meanwhile, and each such use is audited.
New Passkeys Stay On Your Device
Every passkey you add is now stored on the device or security key itself, so it works for sign-in without a username and for phone sign-in. A security key with no free passkey slot is refused when you add it, with a message saying why and what to do.
Reading Config Needs The Config Read Permission
Reading a plugin's settings through the web API now needs the config.get_config permission, the same one the config_get tool needs. Before, any API key or token holding one unrelated permission could read every plugin's settings. Refusals are written to the audit trail.
Audit And Message History Need Permission
Reading the audit trail, the message history or a job trace now needs the observe:read permission. Before, any API key or token holding one unrelated permission could read them. A refused read is written to the audit trail. The message history now returns at most 500 entries per request.
Agents Hear About New Mail Right Away
An AI agent can now wait for mail instead of checking again and again: Kamari answers the moment a message reaches its inbox. Optional Claude Code hook scripts use this to show new mail in a session without being asked. A key revoked while waiting gets nothing.
Review Page Test Runs Run As You
Running a test case from the Review page now runs the capability as you, with the same limits as any other call: an API key narrowed to a few capabilities can only run those, a tool blocked for your account stays blocked, and every refusal is written to the audit trail.
Quests Gain A For Me Tab
The Quests page has a new first tab, For me, with a count of everything waiting on you. It lists every task handed to you, including ones on quests that are already closed, newest first, with the quest status beside each. Ticking a task done on a closed quest does not reopen it.
Ownerless Pipelines No Longer Call Tools
Every tool call inside Kamari now passes one checkpoint that knows who is calling. A pipeline with no recorded owner, usually a very old rule, can no longer call tools: its tool steps fail and the refusal is logged in the audit trail. An admin can give the rule an owner to make it work again.
Quests Can Hand A Task To You
Quests can now hand a task to you, and show everything waiting on you in one place. A checklist item can be marked for a human, with the steps to follow, and a quest waiting on you gets a Needs human status and a notification. A new Needs you view lists every such task with its age.
Backup Download Needs The Backup Permission
Downloading a full backup now needs the backup.export permission, judged against the key, token or session actually used, so a key limited to other tools can no longer fetch it. Refusals are logged in the audit trail. Checking LLM tool support and the memory report also need their own permissions now.
Saving Settings Needs The Config Permission
Saving plugin settings through the web API now needs the same config.update permission that the AI tool for it needs. A key, token or user without it is refused, the refusal is logged in the audit trail, and nothing is saved. Grant config.update to anyone who should still change settings.
Review Cases Can Expect A Refusal
A Review test case can now be marked as meant to be refused. It passes only when the call fails with the error text you named, and fails on a different error or if the call unexpectedly succeeds, so correct refusals no longer show as failures.
Price Tracker Follows Products By Name
Price Tracker can now follow a product by name across a list of shops. Each daily check looks through the shop's own search and sitemap, finds every listing including relisted and bundle ones, keeps price history, and shows the cheapest in-stock price per shop. It obeys robots.txt, goes slowly, and says plainly when a shop blocks it.
Agents Can Message Each Other
AI agents, such as Claude Code sessions, the cloud briefing agent and Claude on your phone, can now leave each other messages in Kamari. Each agent picks a name tied to its own key and gets its own inbox; nobody can send as another agent, and every message is recorded in the audit log without its text.
Sign In By Scanning A QR Code
A browser that cannot use your phone's passkey, such as Firefox on Linux, can now show a QR code and a code. Scan it, sign in on your phone with your passkey and type the code; that browser is signed in. It is off until you turn it on from a passkey sign-in, and an admin can block it.
Passkeys Now Always Ask For Your PIN
Signing in or adding a passkey now always asks for your PIN, fingerprint or face, not just a touch. A passkey that cannot check one, such as a security key with no PIN set, is refused: set a PIN on it, or sign in with a full-access API key and add a passkey that can.
Saved Memories Have A Size Limit
A saved memory can now hold up to 8000 characters by default; longer text is refused with a request to split it. Admins can change the limit in the Memory settings, down to 1024. Memories saved earlier stay fully readable.
Edit Saved Memories In Place
An AI assistant can now change a saved memory's text or label directly, instead of deleting it and saving a new one. The memory keeps its identity, so notes that point to it stay valid. Only the memory's owner or an admin can edit it, and other people's memories stay invisible.
Claude Can Ask For Tools It Lacks
A connected app such as Claude now also sees the tools your account holds but you have not given it yet, marked as needing approval. When it tries one, Kamari asks it to re-authorize, so you can approve that tool without reconnecting. Nothing runs until you approve it.
Save Your Own Permission Sets
On the new Permission sets page you can save named lists of tools, such as one for Claude. When an app asks for access, or you edit a key or a user, pick a set to tick exactly those tools, then adjust. Only you see your sets. Editing a set never changes access you already gave.
Faster Choices On The Consent Page
When an AI app such as Claude asks for access, the consent page now offers presets: full access, read-only access, or only what the app asked for. A filter box finds a single tool fast. The page uses the same tool picker as the Internal page, in light and dark mode.
Choose The Order Quests Are Worked In
Each project now has a work queue that is separate from priority. Drag quests into the order you want, or use the Move up and Move down buttons, in the new Queue view on the Quests page. Queued quests are worked first, in that order. Finished quests leave the queue on their own.
Limit What Connected AI Apps Can Do
On the Internal page you can now take tools away from a connected app such as Claude, and it applies on the app's next call. To give it more, the app asks again and you approve the extra tools on the Kamari consent page, with the requested tools already ticked.
Safer Dashboard Sign-In
Your dashboard session now lives in a cookie that page scripts cannot read and other sites cannot send. Signing out ends that session on the server, so a copied session stops working. Signing in with an API key refuses requests started by another site, and the session keeps that key's limits.
Removing A User Removes Their Access
Deleting a user removes their passkeys, API keys, invite links and the apps they registered. It also ends their sessions and connected-app access. An account past its expiry date is refused on every request, not only at sign-in. A task resumed after a restart is refused once the credential that started it is gone.
Correct Or Settle A Held Payment
On the Payments page you can change a held payment's amount. The original amount and who changed it are kept. Approving sends the amount you saw, and sends nothing if it changed meanwhile. An admin can settle a payment stuck mid-send by recording whether it left the bank.
Keep The Local AI Chat Read-Only
When the local AI chat may call tools, it now uses only tools that you hold yourself. A new setting on the Config page goes further and lets it use only tools marked read-only.
Pipelines Catch Broken Step References
Kamari refuses to save a pipeline whose step refers to a missing or later step. Before, the run quietly read nothing. Condition checks can now compare against references too, such as an earlier step's result.
Private Text Stays Out Of History
The subject and body of emails Kamari sends, and private keys it issues, now reach only the caller. Task history, pipeline run records and logs keep a placeholder, and stores from older versions are cleaned at startup. Plugin log lines have secrets removed before the dashboard shows them.
More Tools For Movies, Shows And Email
The Radarr and Sonarr plugins now show download history, the queue, wanted lists and the full movie library. A new email tool fetches older mail by date range, sender and subject. A new mailbox's first check now starts a week back instead of reading the whole mailbox.
Secrets Stay Where They Belong
The general settings screen and API can no longer read or change the vault, sign-in secrets, API keys or OAuth signing keys. Email passwords now live in the vault too, and a mail setup can only use its own passwords, never another stored secret.
Recovers On Its Own From A Freeze
If the web server stops responding for two minutes (configurable), Kamari records what every thread was doing and exits, so Docker or a service manager can restart it instead of leaving it hung.
Certificate And DNS Record In One Call
Another service on your network can ask Kamari for its own TLS certificate by name and get it back directly, and the same call can point that name's Route 53 DNS record at the service's address.
Fine-Grained Access For Apps And Services
Admins can create, re-scope and revoke API keys and app logins from an MCP client. Unattended services get tool-only tokens of their own, and an app that signs you in can act for you only within what you tick on the consent page.
Signing Out Really Cuts Access
Tokens can be revoked, signing out ends connected apps' sessions, and disabling or deleting a user revokes all of their tokens at once. Credentials and consent are tied to the account itself, so a new user reusing an old name inherits nothing.
Infrastructure Plugins Refuse Unsafe Input
Terraform and Ansible reject values that could be mistaken for command-line options, Proxmox settings are checked against strict rules, and the Proxmox API token is no longer written into generated configuration files.
Read-Only Really Means Read-Only
A capability marked read now changes nothing. Analysing a photo no longer saves a sighting unless you use the separate record action, and listing conversations no longer quietly fetches new email.
Edge-Case Tests Written For You
The Review page can generate test cases for each capability - missing fields, wrong types, boundary values - labelled so you can tell them from your own. Secrets inside saved cases are stored encrypted and only decrypted when a case runs.
Logs And Diagnostics Your Assistant Can Use
An MCP client can read Kamari's own logs with secrets redacted, run fixed host checks such as disk usage and uptime, and make web requests only to domains you allow. Logs and the audit trail are pruned after a retention period you set.
Debug And Rerun Pipelines
Step through a pipeline action by action with breakpoints, watching its live data and messages as it goes, and replay any past run with one click to check a fix.
Sign In To Other Apps With Kamari
Kamari is now a standard OpenID Connect provider, so your other self-hosted apps can use your Kamari account for sign-in. Login apps are created by an admin, never self-registered.
Payments Wait For Your Approval
Payments are held on a Payments page where you approve or reject each one, with a full decision history. A payment short of funds waits and rechecks itself instead of failing, and a sandbox switch lets you rehearse with test credentials.
Several Mailboxes, Attachments Both Ways
Set up several named email accounts, each with its own list of who may use it. Incoming attachments are saved for pipelines to work with, and outgoing mail can carry attachments.
Publish Blog Articles By Pull Request
Write Markdown articles and have Kamari open a pull request against your site's Bitbucket repository, authenticating with an SSH deploy key it generates for you.
Pull Text And Fields From PDFs
Extract text and form fields from PDFs along with where they sit on the page, and fall back to reading the page image when a PDF is only a scan.
Nested Conditions And Calculations In Pipelines
Build conditions from nested and/or groups in a visual builder, reach into list items such as the first attachment, and compute exact decimal values in a pipeline step.
Host And Per-Plugin Resource Use
The dashboard breaks RAM, CPU and disk down per plugin with an honest unattributed remainder, and host CPU, memory, disk and load are sampled on a schedule into metrics you can chart and alarm on.
Every Outbound Call Is Audited
Every web request and DNS lookup a plugin makes goes through one gateway and is written to the audit trail under that plugin's name, with query strings and embedded credentials stripped from the record.
A Faster Dashboard That Times Everything
Pages are compressed, tool lists load on demand and finished jobs are pushed instead of polled. Every capability, and the network, disk and subprocess calls inside it, is timed automatically, including time spent waiting in the queue.
A Device Register That Understands Every Address
Track the devices on your network by name and by MAC. A TV with ethernet and wifi, or a phone that also has bluetooth, is one device with several interfaces, and a single search box finds it from any of its addresses in any format.
Plugins Have To Earn Production
Every plugin now ships as Dev. Save a test case per capability on the Review page, run it for real, and record the verdict; a plugin only becomes Prod once every capability passes. Only capabilities marked read are ever run automatically.
Backups That Finish On Large Libraries
Export streams to disk, stops re-compressing files that are already compressed, no longer walks the folders it excludes and reports progress as it runs, so exports that used to run out of time on a large data directory now complete.
Tool Descriptions Written For Smaller Models
Every tool and every one of its parameters now carries a real description with meaning, format and an example, so a smaller local model picks the right tool and fills it in correctly.
Faster Vision, Careful With Close Calls
A near-miss face or object match is no longer handed to an automation as a real match - seeing close calls needs its own permission. Enrolled people and objects are cached in memory, so each analysis no longer re-reads your whole gallery.
Barcode Price History
Scan a barcode and track what retailers charge for it over time, with live scraping progress and a stop button while a search runs.
Bank Data Behind A Payment-Safety Gate
Read accounts, balances, transactions and beneficiaries through Investec's Open Banking API, wired to a pipeline that gates anything capable of moving money.
Read Text And Barcodes From Photos
Vision reads text from labels, receipts and signs, and decodes QR, Data Matrix, Aztec, PDF417, UPC, EAN, Code 128, Code 39, Code 93 and ITF codes, alongside the faces and objects it already finds.
Install Only The Plugins You Run
Heavy dependencies moved behind per-plugin extras, so a plain install can no longer be blocked by one plugin's package being unavailable on your platform.
Connect Any MCP Client Over OAuth 2.1
An embedded authorization server with discovery, dynamic client registration and PKCE lets an MCP client enrol itself. Older clients can use the legacy SSE transport, and you can review and change what each connected client may do after consent.
Every Call Takes One Audited Path
Every call now travels the message bus. The direct in-process shortcut is gone, so authorization, auditing and tracing apply to everything without exception.
A Rebuilt Dashboard At /web
The dashboard became a multi-page app at /web with dark mode, a signed-in user badge and a public how-it-works page.
Responsive Under Load, Safe Across Restarts
Each plugin gets its own job queue, heavy inference is capped and network calls carry timeouts, so one slow plugin no longer stalls the rest. In-flight work is recorded ahead, drained on shutdown and safely resumed at the next boot.
Webhooks And Home Assistant
Named inbound webhook endpoints feed pipelines directly, and entity state streams live from Home Assistant over its websocket API.
Scoped Keys And Server-Enforced Identity
An API key can be scoped strictly below its owner and pinned to a single project, and a caller can no longer claim to be someone else - identity always comes from the authenticated session.
Metrics You Can Query And Alarm On
A metrics plugin records values from across the runtime and its plugins, streams them live to the dashboard, and raises alarms on thresholds you set.
Conversations Grouped By Person And Company
Email and phone communications are indexed against your contacts, so you can list everything exchanged with one person, one company or one domain.
Trace One Job All The Way Through
Search a run or message id in the Job Tracker and see everything correlated to it, and filter the audit log by user, IP, tool call and allowed or denied.
Guided First Run
A first-boot notification and an in-dashboard tour walk you through setup instead of leaving you in front of an empty configuration page.
Your Obsidian Vault, Read And Written
Read and write notes and their properties in a configured vault folder, get real-time change events rather than polling, and keep the vault in step through Obsidian Sync.
Persistent And Temporary Memory
Your assistant can remember things across sessions, with per-item read permissions and temporary items that expire on their own.
Loops And Variables In Pipelines
A pipeline can iterate over a list, run nested steps for each item, and store values that later steps read back.
Vision: Recognise People, Teach New Objects
Enrol faces and re-identify them across photos, teach a new object class from a handful of examples, and screen images for explicit content.
Datastores, Planning And Chat Channels
Time-series, document and graph stores ship as plugins, alongside task capture and daily planning, local and Google calendars, a syslog listener, a Telegram bot and backup export and import.
Provision And Configure Machines
Terraform and Ansible plugins provision and configure machines, down to a one-call Proxmox VM sized by disk and RAM, a hard-sandboxed file manager guards every path it touches, and network tools ping over ICMP and TCP.
Kamari's First Release
The plugin runtime, the message bus, permission checks on every call, passkey sign-in, a secrets vault and the MCP tool bridge, with first plugins for speech, email, SMS, SMB file shares, push notifications, certificates and media downloads.