June 2026
June updates: the AI assistant now answers with live widgets, a beta of the new nullplatform UI, Kiro support for the nullplatform AI plugins, approvals for action items, and per-dimension access to secret parameter values.
✨ Try the new UI (beta)
We're rolling out a beta version of the nullplatform UI with a more modern, consistent look that's easier to navigate. This first release focuses on clearer information organization and a sharper visual hierarchy.
Turn it on from the user menu → Try new design. The setting is personal and only affects your view, so you can switch back to the classic design whenever you want.
Found something to improve? You can send us feedback or report bugs from that same menu.
The new UI is available as a beta while we keep adding improvements.
✨ Run into a problem? Just ask the AI assistant
When a deployment doesn't look right, the AI assistant is one click away in the platform. Open it and just ask. No IDs, no context to paste. It already knows what you're looking at, and returns a clear diagnosis, root cause, and next steps in seconds.
Answers come back as live widgets too. Instead of walls of text, you get tables, charts, and status cards you can read at a glance.
Investigate, debug, and troubleshoot, right where you work. 🚀
👉 See the AI assistant docs.
✨ Require approval before resolving action items
Now when a developer resolves, defers, or rejects an action item, that change can go through nullplatform's standard approvals engine, the same one you already use across the platform. Instead of a separate embedded flow, you can require a reviewer to sign off before the item's state changes.
For example, to require a reviewer before a critical item can be rejected, create the approval action:
curl -L -X POST 'https://api.nullplatform.com/approval/action' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <token>' \
-d '{
"nrn": "organization=1:account=2",
"entity": "action_item",
"action": "action_item:reject",
"on_policy_success": "approve",
"on_policy_fail": "manual"
}'
Then attach a policy that auto-approves every rejection except critical ones:
{
"nrn": "organization=1:account=2",
"name": "Manual review for rejecting critical items",
"conditions": {
"action_item.priority": { "$ne": "critical" }
}
}
👉 See the Action items docs and how to require approval.
✨ Control secret access by environment
Approvals and policies for reading secret parameter values can now be scoped to specific dimensions, like an environment. Instead of unlocking every value of a parameter at once, an approval scoped to environment: development reveals only the development value and keeps the rest — including production — hidden.
This makes secret access per-environment: developers get instant, audited access in lower environments, while production stays behind a manual review.
For example, create the approval action for parameter:read-secrets:
curl -L -X POST 'https://api.nullplatform.com/approval/action' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <token>' \
-d '{
"nrn": "organization=1:account=2",
"entity": "parameter",
"action": "parameter:read-secrets",
"dimensions": {},
"on_policy_success": "approve",
"on_policy_fail": "manual"
}'
Then attach a policy that auto-approves secret reads only in the lower environments, so production requests fall through to manual review:
{
"nrn": "organization=1:account=2",
"name": "Auto-approve secret access in lower environments",
"conditions": {
"dimensions.environment": { "$in": ["development", "staging"] }
}
}
👉 See Accessing secret values and the new tutorial Approve secret access by environment.
✨ Use nullplatform from Kiro
The nullplatform AI plugins now work with Kiro, so you can interact with nullplatform straight from Kiro the same way you already can from Claude Code, Factory AI, and Codex CLI. Describe what you need in plain language and the plugin queries entities and calls the right API endpoints for you.
👉 See the AI plugins setup guide.
That's all for June, from the nullplatform team! ❤️