| Who runs the work | VestraYou name your chief and tell it what you need in a sentence. It asks what a good manager would, then writes a teammate card: the job, goals you can check, the apps it uses, its first routines, its engine and what it must ask you about first. You read it, change anything and say yes. From then on your chief hands out the work, makes sure every result is checked before it reaches you, and brings you only real decisions. Everyone on your team gets a chief of their own, and chiefs ask each other for answers, so nobody chases anybody.[9][10][11] | Claude CodeYou run Claude Code yourself, in one session or several. Subagents take side tasks inside a session, agent view lets you send sessions to the background and check on them, and Projects (public beta on Pro and Max) run parallel threads for longer work. Agent teams, where a lead session assigns work to other sessions, are experimental and off by default. In every approach the workers are Claude sessions, run by one person.[2][12] |
|---|
| See your whole team | VestraYour office is a map you can walk around, like a game. Every person, chief and teammate has a desk, and each teammate’s tag shows the engine it runs on, so you can see at a glance that code is written on Claude Code and reviewed on Codex. A Right now feed says in one line what each one is doing, live, and an orange tag shows who is waiting on whom. Tap any desk to see its work, watch its computer live or take over. Nothing moves on the map unless real work is happening.[1][13] | Claude CodeAgent view, in research preview, shows your background sessions on one screen, with their state and which ones need your input. The desktop app runs several sessions side by side. Both show your own sessions.[2] |
|---|
| Plans | VestraLite $19 a month for up to 3 teammates and 2,000 credits. Pro $97 for 20 teammates, 10,000 credits and phone calls. Max $197 for 50 teammates and 20,000 credits. Ultra $497 for 150 teammates and 50,000 credits. Billed yearly, they are $17, $87, $177 and $447 a month. One credit is one cent, the same on every engine and for model time, the computer, searches and calls, and every plan includes your chief and the whole office.[3][13] | Claude CodeIncluded in every paid Claude plan and shares its usage with chat: Pro $20 a month ($17 billed yearly), Max $100 and Ultra $200. Team seats are $25 a month ($20 yearly), or $125 for Premium ($100 yearly), for 2 to 150 seats. Enterprise is $20 a seat billed yearly plus usage at API rates, from 20 seats. The free plan doesn’t include Claude Code, and usage resets in five-hour and weekly windows.[4] |
|---|
| Getting started | VestraSign up directly, on any plan, with nothing to install. Every new office starts with 1,000 free credits, enough to hand over real work before you pick a plan. Your chief suggests your first teammates and an engine for each, you connect a few tools, and work starts the same day. Your team’s memory fills from your tools’ history on day one, so it already knows your customers.[3][14][15] | Claude CodeInstall it with one command in your terminal, or use the desktop app, the web at claude.ai/code, VS Code or JetBrains. Most surfaces need a paid Claude plan or a Claude Console account, and you start it inside a project folder.[16] |
|---|
| Where you use it | VestraTalk to your chief in the Vestra app on the web and the desktop app for Mac, in Slack (by direct message or a mention in any channel), in Telegram, or by email: forward anything, or copy it in on a thread. Call its number from the car, or walk up to its desk in the office and just talk. It’s the same chief everywhere, so a conversation started in Slack can finish in the app, and replying “1” takes the suggested option on any decision.[5][9] | Claude CodeIn the terminal, VS Code and Cursor, JetBrains, the desktop app for macOS, Windows and Linux, the web, and the Claude app for iPhone and Android. Mention @Claude in a Slack channel to turn a bug report into a pull request. Channels can push events from Telegram, Discord or iMessage into a session.[17][16] |
|---|
| Calls and email | VestraYour chief has its own phone number and email address, so it calls and writes from its own line and inbox, not yours. It writes first, replies and follows up until there’s an answer. Before a call it reads what the team knows about the person, and afterwards the notes and next steps go where they belong. The first call or email to anyone new waits for your yes. Phone calls start on Pro.[5][3][18] | Claude CodeClaude Code’s docs don’t describe phone calls or an email address of its own. Work it does through your connectors, such as Slack messages or tickets, uses your linked accounts and appears as you.[7] |
|---|
| App connections | VestraMore than 2,000 apps connect in a click, including Gmail, Slack, HubSpot, Notion, Shopify and Stripe, and engineers’ teammates work in GitHub and Linear. Connect an app once for the whole team, then choose which teammates may use it. Logins stay sealed: agents use them without ever seeing the password, and you can take access back in one tap. Where there’s no connector, a teammate uses the website on its own computer.[18][6] | Claude CodeConnects tools through MCP, such as Google Drive, Jira and Slack, and works directly with git, GitHub and GitLab. Hooks run your own commands before or after its actions, and plugins bundle skills, subagents and hooks.[16] |
|---|
| Model and engine choice | VestraMore than a model: pick the engine that does each teammate’s work, Vestra’s own, Claude Code or Codex. If your engineers already work with Claude Code, their teammates can run on it too. Your chief suggests one and says why, or picks job by job. Mix them in one team, so code written on Claude Code is reviewed on Codex with fresh eyes. Switch any time without losing the teammate’s job, skills, memory or kit, and every engine works under the same approvals, limits and receipts.[13][5] | Claude CodeRuns on Anthropic’s Claude models, Fable, Opus, Sonnet and Haiku, switched with /model. You can host them on Amazon Bedrock, Google Cloud or Microsoft Foundry, but the docs name no models from other makers, and every parallel worker is a Claude session. Other tools join only as MCP servers.[19][2] |
|---|
| Its own cloud computer | VestraYour team works on a cloud computer with a real browser, files and a terminal. It uses any website the way you do, including ones with no connector, like supplier portals, booking pages and government forms. Watch it live, take over with one click when a site needs you, and hand it back to carry on where you left off. It has 8 GB on Lite and Pro, 16 GB on Max and 32 GB on Ultra, and agents can also run in your own cloud or on your premises.[18][3][13] | Claude CodeRuns on your own machine with your files and terminal, or in Anthropic-managed cloud sessions that keep working when your laptop is closed. A Chrome integration lets it debug live web apps.[16] |
|---|
| Approvals | VestraSpending over your limit, contacting someone new and deleting anything always come to you, on every engine, and no setting turns that off. Everything else you tune teammate by teammate and task by task: ask first, suggest, or act and tell you afterwards. New teammates start by asking, and get more freedom only when you move the setting. Each decision arrives in one line with the facts and a suggestion, so you can answer from your lock screen.[6][9] | Claude CodePermission modes set what asks first: Manual asks on first use of each tool, Accept edits allows file edits, Plan only reads, and Auto has a classifier check actions instead of you. Allow, ask and deny rules can be shared in the repo, and admins can lock them with managed settings.[20] |
|---|
| Spending limits and receipts | VestraCap any single task and the whole day, up to $100 a day. Anything unusually big, over 50 credits by default, waits for your okay with the cost shown. When a cap is reached, work stops at a sensible point and says what’s left. Every receipt splits the cost into model time, actions and computer time, and shows which teammate spent it on which job and engine. Unused credits roll over, and you can top up any time.[6][3] | Claude Code/usage shows your plan usage and what used it. On Team and Enterprise, admins set spend limits on usage credits for the organization, a group or a member, with a spend report updated daily. Anthropic puts the average enterprise cost at about $13 per developer per active day, or $150 to $250 a month. The docs don’t describe a per-task cap on a subscription.[8] |
|---|
| Memory | VestraOne shared wiki for the whole team, people and agents on every engine: your people, customers, decisions, numbers and what went wrong last time, with a source for every line. It fills from your tools’ history on day one, then from every task, email and correction. Open any line’s source or edit any page, and the fix reaches every teammate’s next piece of work: correct one teammate once, and they all learn. Export it all as Markdown any time.[15][5] | Claude CodeCLAUDE.md files hold instructions you write, and a project CLAUDE.md is shared with your team through git. Auto memory saves what Claude learns from your corrections, but it stays on your machine and isn’t shared with teammates, other machines or cloud sessions.[21] |
|---|
| Schedules and proactive work | VestraEach teammate owns a goal and does three kinds of work: one-off asks, routines that run on a schedule (a market note every Monday at 9) or the moment something happens (a rival changing its prices), and the goal it holds for months. When it spots something worth doing, it brings you a proposal to approve, and on quiet days it says nothing. Your chief sends a morning brief at the time and place you choose.[10][9][10] | Claude CodeCloud scheduled tasks, in research preview, run on a schedule, an API call or a GitHub event, even when your computer is off, up to 100 scheduled runs an hour. They belong to your individual account, aren’t shared with teammates and act as you.[7] |
|---|
| Skills | VestraReady-made skills for Sales, Bookkeeping, Content, Customer care and Research, added to any teammate in a click. Custom skills are built around your own playbooks, data and standards, like your code style or release checklist, usually during onboarding, and read like a short plain-language checklist you can edit when your business changes.[10][13] | Claude CodeSkills package repeatable workflows your team can share, like /review-pr or /deploy-staging, and plugins bundle skills, subagents and hooks.[16] |
|---|
| Research | VestraHire a Research teammate in a sentence to watch markets, rivals and people, with sources. Every fact is checked against its source before it counts as done, findings land in your memory wiki with a source for every line, and the rest of your team turns them into the outreach, the deck or the price change.[10][15][11] | Claude CodeMaps large codebases with agentic search and can search and fetch the web. Dynamic workflows run many subagents and cross-check their findings, for jobs like a codebase-wide audit or cross-checked research.[17][2] |
|---|
