Six steps, one time, about ten minutes. No terminal if you do not want one.
Step six, the moment it works.
What changes is how much plumbing you touch. Every assistant below uses the same skills, the same server and the same Avonni components.
A normal desktop app, included with Claude Pro. Paste any command from this page into the chat and Claude runs it for you. You never open a terminal yourself.
The same skills and the same server, for people who already live in the terminal.
Skills install with one command. The server goes in as a small JSON entry in your editor config.
Salesforce's agent, in VS Code or in the browser from Setup. The server goes in from its Toolkit in a few clicks, the skills with one command.
A chat that runs in a terminal window. Daily use is plain language like the others, but setup and troubleshooting are manual. Follow the Gemini CLI tab in each step.
Do them in order. After the last one you never come back to this page.
Any package works, they all carry the same library. Ten free production licenses, sandboxes unlimited.
The install runs in your org and Salesforce emails you when it is done. Carry on with step 2 while it finishes.
Two installs power everything. Without them your assistant can read documentation, but it cannot build, save or deploy anything.
Install Node.js, version 18 or later. Download, run the installer, accept the defaults.
Install the Salesforce CLI, then connect it to your org:
This opens a browser window where you log in to Salesforce as usual. The CLI then acts on your behalf.
Both install like any other desktop app. And from here on you never need a terminal: paste any command on this page into the Claude desktop app chat and Claude runs it for you. You just approve.
Your assistant works inside a folder on your computer, where it saves what it creates. Any empty folder works. An Avonni AI folder on your Desktop is fine.
Claude desktop app or Claude Code: open the folder as your project.
File, then Open Folder.
In VS Code, open a Salesforce DX project with the Agentforce Vibes extension installed. Or open it in the browser from the Setup menu of your org, and pick Standard when it asks you to set up a project.
Install it, then run it from inside the folder.
One command installs all five skills into the folder you just opened. The installer detects your assistant and puts them in the right place.
Run it in the terminal, or paste it into the Claude chat and ask Claude to run it for you.
Run it in your editor integrated terminal, from the folder you opened in step 3.
The skills installer does not know Vibes yet. Vibes reads project skills from .vibes/skills, so this command copies all five there:
Run it in the Vibes terminal, or paste it into the Vibes chat and let the agent run it. Then open Toolkit, then Skills: the five Avonni skills appear under Project.
Run it from your project folder. Inside a Gemini session, check with /skills list, and run /skills reload if you just added them. If nothing appears, trust the folder with /trust and restart: Gemini only loads workspace skills from trusted folders.
The server is hosted by Avonni. Nothing to install and nothing to run: you just point your assistant at it.
Run it, or paste it into the chat the same way as step 4.
Add it as an MCP server in your editor JSON config, for example .cursor/mcp.json.
In the Agentforce Vibes panel, open Toolkit, then MCP Servers, and click + Add Server. Name it avonni and paste this URL:
Click Add Server. A green Connected status with a tool count means it worked.
Add the server to your project .gemini/settings.json, creating the file if needed. Restart Gemini, then run /mcp to confirm the server is connected and its tools are listed.
Ask your assistant:
A real list back, one catalog per Salesforce surface, means everything is connected. Now describe your first screen.
A connected assistant answers with the real catalogs, one per Salesforce surface.
Your assistant writes files on your computer. You review them and deploy with your usual process. Your org is never touched without you.
The reply describes components that do not exist, or it never mentions looking anything up. The MCP server is not connected: redo step 5. In Gemini, restart the session and run /mcp to confirm.
Skills install into the folder you opened, not globally. Check that you ran step 4 inside that folder. In Gemini: /skills list, then /skills reload, then /trust and restart.
Node.js or the Salesforce CLI is missing, or the CLI is not logged in. Run sf org login web again and approve in the browser.
Paste one as it is. None of them names a component: your assistant picks from the real catalog.
Create an Avonni Dynamic Component for the Account record page: a Data Table of the account open Cases with inline editing.
Create a screen flow where the user picks an appointment date on an Avonni Date Picker, then confirms on a summary screen.
Add an Avonni Kanban of Cases grouped by status to my customer portal page.
Add an Avonni Data Table of Cases to my component, with sorting and inline editing.
Tell us what you are building and we will show you the AI setup on a real org.
Request a Demo