Changelog
The changes that matter — newest first.
Hosting
Apps you deploy through Cohesivity now get their canonical URL on cohesivity.app. New deployments advertise the new domain end-to-end — provisioning, deploy responses, status, claim emails, and social-login callbacks — while existing projects are migrated without downtime.
Agent skill
The Cohesivity skill is now served at a stable /skill.md URL and installs with a single curl — no MCP server or SDK required. Once installed at personal scope, your coding agent loads it automatically in every project on the machine.
Postgres
A net-new /postgres backend on managed Neon brings real Postgres to your agent: pgvector retrieval, tsvector full-text search, materialized views, partial indexes, and true BEGIN/COMMIT transactions. It runs alongside the existing SQLite database — both coexist on the same tenant.
AI Gateway
Call approved OpenAI, Anthropic, Google, and xAI models through one governed Cohesivity endpoint, with provider keys kept server-side. Tier gates, quota reservation, and wallet guards apply automatically — and you're never billed when a successful response carries no usage.
Custom domains
Agents can now purchase a domain for the user — .com, .ai, .io, .uk and 300+ TLDs — or attach a domain you already own at any registrar to your project. All of it happens through Cohesivity, with no registrar or hosting dashboard to click through.
Dashboard
A new Insights tab in the dashboard shows project owners who signed up and signed in through the social-login offering. It surfaces owner-safe identity and coarse auth activity only — no IPs, tokens, or raw metadata are exposed.
Runtime
Tenants pinned to an older runtime can now move forward on their own. /api/status flags when an upgrade is available, and your agent applies the tenant-facing changes from a structured release-notes feed and commits the bump — no manual intervention needed.
Speech
Speech-to-text and text-to-speech are now available through an approved deepgram-api provider. Cohesivity injects the credentials server-side, so there's no upstream key for your app to hold or manage.