What changed in Zihin.
Product milestones, month by month — in human language, not endpoint language.
May 2026
- Feature
Session Control — pause, intervene and block without touching the agent
Five new levers to control attendance without editing the agent: suspend a specific conversation, take over manually replying through the agent's own channel, cancel an in-progress turn (loop or wrong answer), block a contact across all your tenant's agents, and view a contact's aggregated cross-session history. No quota cost when control blocks.
- Feature
Builder Agent — edit your agents by chatting with AI
Builder Chat is now an AI agent that understands your agents' configuration and proposes validated changes. You describe what you want to adjust — persona, tools, triggers, MCP servers, security policies, skills, workflow, database connections — and Builder creates proposals you approve with one click. Each proposal is validated before becoming a real change, and nothing applies without your confirmation.
- Feature
Long-term memory — agents remember contacts across sessions
Agent memory is now persistent and cross-session: what it learns about a contact in one conversation is available in the next, even days later. You choose which agents need long-term memory (continuous support, follow-up, customer profile) and which don't (one-shot tasks, public agents without a fixed identity) — per-agent control, without affecting the others.
April 2026
- ReleasePublic beta
Public site launched in beta
New routes (/sobre, /contato, /seguranca), LGPD consent banner, legal pages (terms, privacy, cookies) and SEO foundations (sitemap, JSON-LD). Ready for organic traffic.
- Feature
Workroom: live sessions and replay
Every execution event now streams tenant-wide via SSE. Full replay of past sessions, with phases, tool calls and per-call latencies.
- Feature
Zihin Tunnel in production
First pilot client connected via Tunnel. Outbound WebSocket, on-premise credentials, zero open ports on the client's firewall.
- Feature
Multi-agent with team memory
An agent can invoke another agent via the invoke_agent tool. Shared memory across agents in the same pipeline. Depth limit controlled by policy.
API changes, endpoint by endpoint, live in the technical changelog: docs.zihin.ai/reference/changelog
This site uses cookies.
Essential cookies are always on so the site works. Analytics cookies only activate with your consent. Learn more