Stop clicking through Setup menus. With an LLM copilot (GitHub Copilot, Agentforce Vibes, Cursor, Windsurf, or similar) you can install and configure AddressTools Premium — create address blocks, assign permissions, tune settings, and manage reference data — just by describing what you need in plain English.
Early access: This capability is under active development — it covers a focused set of configuration tasks and has been tested with a small pool of models, so results may vary. We’re expanding coverage and improving reliability with each release. If you hit a gap or something doesn’t work as expected, let us know.
Documentation Map
These guides are for you (the human). The Headless Setup Guide is for your copilot — you don’t need to read it, just paste the link.
| Guide | Audience | What it covers |
|---|---|---|
| This page | You | How this works, prerequisites, tips, and FAQ |
| Install AddressTools Premium | You | Getting the package installed via your copilot |
| Example Prompts | You | Copy-paste prompts organised by task |
| Headless Setup Guide | Your copilot | Technical reference — paste this link into your copilot’s chat |
Prerequisites
- VS Code (or your editor of choice) with an LLM copilot installed
- Salesforce CLI (
sf) authenticated against the target org - System Administrator access on the target org
How It Works
- Open your copilot’s chat in VS Code (or your editor of choice)
- Paste this link into your prompt so the copilot has the technical context it needs:
https://provenworks.com/addresstools-premium-headless-setup-guide-for-llm-copilots/ - Describe what you want in plain English — for example:
“Use this guide — https://provenworks.com/addresstools-premium-headless-setup-guide-for-llm-copilots/ — I want to create a new address block on Contact for a Seasonal address with verification.”
- Review and approve the terminal commands your copilot proposes
- Done — no Setup menus, no manual metadata wrangling
Not sure what to ask? See the Example Prompts guide for ready-to-use prompts by task category.
Tips for Better Results
-
Be specific about your org. Include the org alias in your prompt if you have multiple orgs authenticated: “On
production-org, disable the Account trigger for the Data Migration profile.” -
State what capabilities you need. When creating an address block, say whether you want verification, lookup population, and/or geocoding. If you don’t specify, the copilot will ask.
-
Name the object and address type. For standard objects, mention “Mailing”, “Billing”, “Shipping”, or “Other”. For custom objects, mention the API name (e.g.
Property__c). -
Reference the guide URL. Paste the guide link in your first message so the copilot has the full context:
https://provenworks.com/addresstools-premium-headless-setup-guide-for-llm-copilots/ -
Let the copilot run commands. It will use
sfCLI commands and anonymous Apex — just approve the terminal commands when prompted. No manual Setup clicks required.
Frequently Asked Questions
Do I need to know Apex or the Salesforce CLI? Not strictly — the copilot writes and runs the commands for you. That said, we recommend having at least a basic familiarity with the Salesforce CLI and Apex so you can follow along with what the copilot is doing, understand the changes being made, and catch anything that doesn’t look right.
Will this work with any LLM, or just GitHub Copilot? The Headless Setup Guide is designed for any LLM copilot that can execute CLI commands — including GitHub Copilot, Cursor, Windsurf, and Salesforce’s own Agentforce Vibes (in Act mode). If your tool can run terminal commands and read web content, it should work.
Is this safe for production? The guide enforces safe practices: it checks before creating, uses anonymous Apex (which leaves no code behind), and creates dedicated permission sets rather than modifying managed-package metadata. That said, we strongly recommend running these tasks in a sandbox first, verifying the results, and then promoting the metadata to production through your normal deployment process. Always review the commands proposed before approving them in your terminal.
Can I undo what the copilot creates? Yes. Custom fields, permission sets, and address block records are all standard Salesforce metadata and data — you can delete or modify them through Setup or the CLI at any time. You can also ask your copilot to roll back the changes it made in the same session.
Does the package require a license for production? For production orgs, the package starts a 14-day free trial. Contact sales@provenworks.com for licensing after the trial.
Where do I get help?
Glossary
| Term | Meaning |
|---|---|
| Address block | A record that tells AddressTools which fields on which object to validate, standardise, and geocode |
| Anonymous Apex | Apex code executed on-the-fly via the CLI — it runs and disappears, leaving no code in the org |
| FLS | Field-Level Security — controls which users can read/write specific fields |
| Geocoding | Converting an address into latitude/longitude coordinates |
| Hierarchy custom setting | A Salesforce setting with org-wide, profile, and user-level overrides |
Namespace (pw_ccpro) |
The managed package prefix — all AddressTools objects and fields start with this |
| Permission set | A Salesforce construct that grants users access to specific fields and features |
| PLAV | Premise-Level Address Verification — validates addresses down to the building number |
sf CLI |
The Salesforce CLI — command-line tool for interacting with Salesforce orgs |