Changelog

This release made vooy faster and broader.

New

• Realtime streaming responses — the agent's reply now flows token by token instead of waiting until it's complete. Long answers feel dramatically faster.
• Connector marketplace — admins can browse and enable connectors directly from the workspace. 32 connectors are supported at launch.

Improved

• Tool selection accuracy is up: active connectors are now pre-narrowed by intent before tools are exposed to the model.
• Fixed messenger edit rate-limit issues with a coalescing buffer that caps edits at ≤12 per second.

Streaming turns on automatically in your workspace settings — no action needed.

New

• Agent memory — the agent remembers context from earlier conversations and preferences you've shared. "That project I mentioned last time" now just works.
• Multilingual support — Korean, English, and Japanese are supported. The agent detects your language and replies in kind.

Improved

• In long conversations, older history collapses into summaries, reducing how often you hit the context limit.
• Reworded the messages shown to users when a tool fails so they're clearer.

Fixed

• Resolved duplicate responses caused by the same turn running twice on worker restart, using idempotency keys.
• Removed a race where connector tokens expired moments before refresh, causing intermittent 401s.
• Fixed an edge case where the agent stalled when sent an empty message.

Improved

• Session recovery now commits partial progress first, so a restart never redoes work that already happened.

New

• Connector SDK v2 — a new SDK that implements every connector as an MCP server. Auth isolation and schema normalization come built in.

export default defineConnector({
  id: "linear",
  auth: oauth2({ scopes: ["read", "write"] }),
  tools: [createIssue, listIssues],
});

Breaking

• Existing v1 custom connectors no longer work. You must migrate to the v2 SDK.
• Tool input validation is unified on Zod schemas; some loosely defined inputs may now be rejected.

The migration guide is in the docs. If you get stuck, let us know.