Launch Strategy Team
Campaign, release notes, release evidence
Verzeta™ · local-first AI team workspace
Verzeta Studio is the host app. Create a project room, add named members, give each member its own model and tools, then watch the team hand off work, produce artifacts, vote on decisions, and leave an audit trail. Verzeta for Android and Verzeta for VS Code pair in as wire clients.
Verzeta Studio · Project Rooms
Project Rooms turn setup into a guided workflow. Choose a room, start from a curated template, edit the goal and teammates, then launch a project with roster, tasks, artifacts, and tools ready.
Campaign, release notes, release evidence
Opening hook, objections, customer stories
A researcher gathers material from multiple sources, an analyst structures the findings, and a reviewer checks the claim trail.
A researcher reads through every transcript and pulls out direct quotes. An analyst clusters the quotes into themes.
An engineer reads the diff deeply and identifies bugs. A reviewer applies senior-engineer judgement on risk.
An engineer drafts the proposed design. A designer makes sure the user-facing surfaces and trade-offs are clear.
A writer drafts every variant with a clear voice. A critic flags weak claims, vague benefits, and tone drift.
A writer owns the launch narrative across surfaces. A designer makes sure landing-page and email visuals align.
Local first
Many agent workspaces need a separate server before the app can do anything. In Verzeta the app is the server: install it, add a model provider, and your team is ready. Want it always on? Run the same app headless on a home server or spare machine and pair your devices to it. Nothing leaves your machines unless you use a cloud model or web search.
| Requirement | Verzeta Studio | Server-based agent workspaces |
|---|---|---|
| What you install | One app, nothing else | An app, plus a server or a hosted account |
| Separate server required | No, the app is the server | Yes: your own, or the vendor's hosted one |
| Where it runs | Your own machine | Your server or the vendor's cloud |
| Database and storage | A local file, built in | Run by whoever hosts the server |
| Account or identity | None | Needed to join the workspace |
| Where conversations live | On your own machine | On the server |
| Working with local models | Anywhere, even offline | While the server is reachable |
| Always-on server (optional) | The same app, run headless | A separate server, yours or the vendor's |
Turn limits, rounds, polls and task plans coordinate your agents, so a conversation always moves forward and always ends.
Agent commands go through an allow-list and safety checks, with optional write protection on Linux.
Built with Qt 6 and KDE libraries, not a browser in a window, and follows your desktop theme.
Provider routing
Verzeta supports cloud APIs, remote servers, local GGUF models, and any OpenAI-compatible server. Provider choice happens per member, not only per app.
Tool whitelists
The app can expose tools globally while each member sees only the tools allowed for that member. This lets one agent review, one write, one search, and one coordinate.
Cascade chat
One message can trigger a structured chain: mention routing, intent checks, per-member model dispatch, and a bounded cascade that stays inspectable.
Artifacts, polls, timeline
Verzeta is strongest when a team produces something concrete and you can inspect what happened afterwards.
# Launch plan - Position Verzeta as a local-first AI team workspace. - Lead with privacy: no telemetry, no cloud sync, no accounts. - Show Android and VS Code as wire clients of the desktop host.
Skills
Skills extend what the team can do, under your review. Install a domain workflow, read what it instructs, approve it, then expose it only where that project or conversation needs it.
Skills are reusable instruction bundles that agents can follow. They never grant tools and never run scripts on their own. Every install stays Blocked until you review and approve it.
Search the skill catalog. Every install lands as Blocked until you review and approve it. Agents can only use a skill once you approve it.
--- id: release-notes-from-repo description: Extract user-facing release notes from repository evidence. tags: [release, changelog, writing] --- When the user asks for release notes: 1. Inspect the changed files and docs. 2. Separate user-visible changes from internal work. 3. Call out risks, setup steps, and upgrade notes.
Find a skill in the skill catalog or drop a local skill folder into the app data skills directory.
Read the instructions, tags, declared workflow, and supporting files before the model can use it.
New installs stay Blocked until you review and approve them. Agents cannot use a skill until it is Approved.
Make the approved skill global, project-only, or conversation-only so the right agents see it.
The prompt layer marks skills READY or BLOCKED, then agents read and apply them when relevant.
Host and wire clients
Verzeta Studio runs the tools, agents, and conversation state on your machine and sends every model request. Verzeta for Android and Verzeta for VS Code pair in over a WebSocket on your network, with optional TLS, and show the same team. No Verzeta cloud service sits in between, and the clients never talk to a model provider directly.
Verzeta for VS Code
Verzeta for VS Code pairs with the host app and shows your conversations and project rooms in the sidebar. Register a workspace as a virtual mount on any conversation, group or 1:1, and the team can read, edit, and create files as if the project were local. Editor actions route a selection straight to a member, and the extension can generate commit messages and send terminal output into the chat. No model runs inside VS Code; the host does the work.
ws://localhost:9180/RECENT · WORKSTATION
int main(int argc, char** argv) {
Host host = Host::open(argv[1]);
while (host.running()) {
auto turn = host.next();
route(turn); // hand off by @alias
}
return 0;
}Select code and route it to an agent from the lightbulb menu.
Register a VS Code workspace as a virtual mount on a chat, group or 1:1. The team works on the real project files under your control. Writes follow a permission tier, with a built-in secret blocklist and an optional path allowlist.
Shell commands follow a per-conversation policy and run sandboxed where the platform supports it.
Verzeta for Android
Verzeta for Android pairs with Verzeta Studio over a WebSocket, with TLS for remote access. It runs on phone, tablet, desktop, and TV, streaming conversations and project rooms so you can send messages, manage members, vote in polls, and review activity. The device never runs models or tools. The host does that.
ws://192.168.1.20:9180/wsRECENT · WORKSTATION
@Maya@ClarkSystem design
Aliases, projects, providers, tools, skills, polls, artifacts, wire clients, and timeline evidence work together as one local-first system.
Verzeta models the team directly: named aliases, reusable templates, coordinator behavior, member routing, and visible handoffs.
One project can mix local Ollama, cloud APIs, remote servers, local GGUF models, and any OpenAI-compatible server instead of forcing one model across the workspace.
Tool whitelists let one member search, another write, another review, and another coordinate without giving every agent every capability.
Canvas artifacts, plans, polls, files, and activity timeline entries turn a chat into a traceable project run.
No telemetry, no cloud sync, no accounts. The desktop stays the control plane and the clients are paired surfaces.
Skills are reviewed before use and only exposed where they belong, so repeatable workflows never run unseen.
Capability map
Aliases like @Alice and @Robin are the routing handles, not fixed job titles.
Product Manager, Researcher, Writer, Reviewer, or your own, used more than once.
Each member can use a different provider and model in one chat.
Allow tools per member instead of opening every capability to everyone.
Goals, shared documents, and rosters travel with the room.
Approve an instruction bundle, then scope it to a project or conversation.
Members and you vote when the team needs a decision on the record.
Replay turns, tool calls, votes, file writes, and member changes.
Chat, editor actions, and a permissioned workspace mount inside the editor.
The same team on phone, tablet, desktop, and TV while the host does the work.
Members delegate self-contained side tasks to private background workers that report back.
Schedule background agent runs so the team keeps working on a cadence you set.
Long group chats stay coherent through automatic compaction. Nothing you see is deleted.
Run the host without the desktop UI on an always-on machine and pair clients to it.
Documentation
The guide is synced from each product repository. Pick a surface, then read setup, providers, teams, projects, editor integration, pairing, and troubleshooting in one place. Search spans every surface at once.
Verzeta Studio is a local-first AI chat workspace where several AI agents work together as a team in one conversation. Each agent has its own model, role, system prompt and tool list.
The app is open source under a triple-license arrangement (GPL-3.0-or-later for the differentiated components, LGPL-3.0-or-later for the supporting infrastructure, and a commercial license for organisations that want neither copyleft variant). It runs on Linux and Windows, and pairs with two wire clients, Verzeta for Android and Verzeta for VS Code, over a connection you can encrypt with TLS.
Multi-agent group chat. Run multiple AI agents in one conversation. Each agent can use a different provider (e.g. Alice on Ollama locally, Bob on Claude, Carol on Gemini) and a different tool whitelist. They route work to each other with an @mention.
Local-first. Your conversations, attachments, and skills are stored on your own machine in a SQLite database. API keys stay in your local settings in obfuscated form (see how keys are stored). Local models via Ollama and llama.cpp run on your hardware without sending data to anyone.
Eight providers supported out of the box. Cloud: OpenAI, Anthropic, Gemini, OpenRouter, DeepSeek. Self-hosted servers: Ollama, llama.cpp (HTTP). Built-in: a local llama.cpp engine in the Local AI edition. Any OpenAI-compatible server can be added as well.
Real agent capabilities. Agents can read and write files, run allowed shell commands, search the web, edit code in a side canvas, run multi-step tasks, use the skills you approve, and vote in polls. Every action is recorded in the activity log.
Skills. Installable instruction packs (a SKILL.md file with frontmatter, plus optional supporting files). Agents discover them and apply them when relevant. Each skill is approved by you before any agent can use it.
Polls. When the team needs a decision, they open a poll instead of looping in discussion. Votes are recorded, and the chat keeps moving.
Activity timeline. Every agent turn, tool call, file write, member change, and poll vote is recorded. Open the timeline for a project or a single conversation to see what happened.
Mobile companion. Pair an Android device with your desktop using a one-time code. Continue chats on your phone over a WebSocket connection, encrypted with TLS when you turn it on.
Drafting a document. A writer agent drafts, a reviewer agent critiques, and a researcher agent fact-checks. Each step lands as a real file in the project's artifact folder.
Code review. A coder agent edits a file in the canvas, and a reviewer agent runs it and writes a feedback note. The plan tracks unfinished steps.
Research with audit trail. A search agent uses the web and a summariser agent writes notes. Every search query, every file read, and every conclusion is logged.
Team decisions. When two agents disagree, the coordinator opens a poll. The team votes. The decision is recorded on the chat timeline.
| Attribute | Value |
|---|---|
| License | GPL-3.0-or-later, LGPL-3.0-or-later, or commercial, declared per file. See LICENSING.md |
| Source code | Open source. Browse and modify under GPL or LGPL, per the SPDX header on each file |
| Platforms | Linux and Windows |
| Wire clients | Verzeta for Android and Verzeta for VS Code |
| Telemetry | None. The app never sends usage data anywhere. |
| Data location | ~/.local/share/Verzeta/verzeta-studio/ on Linux, %APPDATA%\Verzeta\verzeta-studio\ on Windows |
| Connectivity | Required only for cloud providers, web search, downloads and remote pairing |
Every dialog has the same layout: a title with an icon and a close button, an optional search box or subheading, and action buttons along the bottom.
On large screens dialogs open as centred cards. On small or touch screens they expand to fill the window, and you can drag a dialog down from its title strip to dismiss it.
Get Verzeta
Download a release or build from source. The fastest first run is Ollama locally or one configured cloud provider, then a group chat with named members. Pair Verzeta for Android or Verzeta for VS Code once the host is running.
The primary host build. Use GitHub release artifacts or build from source.
View releasesThe Windows host build, from the same source and release channel.
View releasesPair the wire client with the host on a phone, tablet, desktop, or TV.
See Verzeta for AndroidInstall the extension and pair it with the running host to work inside the editor.
See Verzeta for VS Code