Agentforce Vibes Is No Longer Free: The Complete Developer’s Guide to Pricing, Flex Credits, and What Comes Next

Agentforce Vibes Is No Longer Free: The Complete Developer’s Guide to Pricing, Flex Credits, and What Comes Next

The free ride is over. Since June 1, 2026, Agentforce Vibes requires Flex Credits or a paid license on all non-Developer Edition orgs. Here is everything you need to know — pricing breakdown, free tier limits, migration strategies, and how alternatives like Claude Code with Hosted MCP Servers stack up.

When Salesforce launched Agentforce Vibes at Dreamforce 2025, it arrived as a gift to the developer community: a fully AI-powered, enterprise-grade vibe coding environment — completely free. Within months, adoption exploded. By TDX 2026, Salesforce reported a 22x surge in monthly usage and over 100 million lines of code accepted through the platform. Developers built Apex triggers, LWC components, and entire Agentforce agents by describing intent in natural language.

Then the notification appeared.

A pop-up inside the Agentforce Vibes interface began warning users: “Starting June 1, agentic chat will require the use of Flex Credits or a paid user license.” The era of unrestricted free access to Salesforce’s flagship AI coding tool was ending.

If you have been relying on Agentforce Vibes for your daily development workflow, this guide breaks down exactly what changed, what it costs, what you still get for free, and how to make the right strategic decision for your team.

What Changed on June 1, 2026

The change is straightforward but significant. Before June 1, any Salesforce org — sandbox, scratch, or production — could use Agentforce Vibes at no cost, with a generous allocation of AI-powered coding assistance. After June 1, the economics split into two tiers:

Paid Orgs (Production, Sandbox, Scratch)

Any non-Developer Edition org must now pay to use Agentforce Vibes. You have two options:

• Flex Credits: Consumption-based pricing at $500 per 100,000 credits. Each coding interaction consumes credits based on token usage and model complexity. GPT-5 interactions cost more per request than Claude Sonnet 4.5 interactions.
• Unmetered Platform Developer and Admin AI User Permission Set License: A flat per-user license that provides unmetered access to Agentforce Vibes for licensed users. Pricing is $125 per user per month.

Developer Edition Orgs

Free access continues, but with significant constraints:

• 110 requests per month with Claude Sonnet 4.5
• 1.5 million tokens per month
• No fallback model: Previously, when you exhausted your “Premium” GPT-5 allocation, GPT-5 mini served as a fallback. That fallback no longer exists. When your tokens are depleted, you wait for the next refresh cycle.
• Monthly refresh through May 31, 2026 — after that date, you receive a one-time final allocation of 110 requests / 1.5M tokens with no further refresh.

Understanding Flex Credits: The Consumption Model

Flex Credits are Salesforce’s universal consumption currency for AI features across the platform, not just Agentforce Vibes. Understanding how they work is essential for budgeting.

How Credits Are Consumed

Every interaction with Agentforce Vibes — whether you are generating an Apex class, refactoring a trigger, or asking it to explain a governor limit violation — consumes tokens. The credit cost depends on:

• Model selected: Claude Sonnet 4.5 is the default and most cost-efficient. GPT-5 is available as an alternative but consumes more credits per interaction.
• Context size: Larger metadata context (complex orgs with hundreds of objects and fields) means more tokens per request.
• Interaction complexity: A simple “create a test class for this trigger” costs less than “refactor this entire service layer to follow the separation of concerns pattern.”

Real-World Cost Estimation

Based on community reporting and Salesforce documentation:

• A typical coding session generating an Apex class with tests: ~500-1,500 credits
• A complex refactoring session across multiple files: ~2,000-5,000 credits
• Plan mode analysis of a medium-sized org: ~1,000-3,000 credits

At $500 per 100,000 credits ($0.005 per credit), a moderate developer using ~50,000 credits per month would spend approximately $250/month. A heavy user at 200,000 credits would reach $1,000/month. The flat $125/user/month license becomes cost-effective for heavy users who exceed ~25,000 credits monthly.

Sharing Credits Across the Org

Flex Credits purchased at the org level are shared across all users. This means your admin testing a Flow and your developer generating Apex draw from the same pool. For teams, this requires coordination — or a clear budget allocation per role.

What You Still Get for Free in Developer Edition

If you are building components, learning Salesforce development, or prototyping solutions that do not require your production org’s metadata context, the Developer Edition remains viable:

• Agentforce Vibes IDE: The browser-based VS Code environment is still free and launches directly from Setup.
• Claude Sonnet 4.5: Available as the default model with 110 requests and 1.5M tokens.
• Salesforce Hosted MCP Servers: Now available in Developer Edition, connecting Claude Desktop, Cursor, or ChatGPT to your org’s data via the open MCP standard.
• Full CLI access: The 220+ Salesforce CLI commands remain free and unrestricted.

The limitation is clear: if your work depends on your production org’s metadata — custom objects, fields, validation rules, flows, Apex classes — the free Developer Edition cannot provide that context. You would need to replicate your org structure in a scratch org or Developer Edition, which is impractical for ongoing professional work.

The Strategic Question: Agentforce Vibes vs. Claude Code with Hosted MCP

This pricing change forces a decision that many Salesforce developers have been deferring. With Salesforce Headless 360 making every capability available via API, MCP, and CLI, you now have genuine alternatives to Agentforce Vibes for AI-assisted Salesforce development.

Option A: Agentforce Vibes (Paid)

Strengths:

• Deep org metadata awareness — reads your actual objects, fields, and patterns
• Integrated Plan and Act modes for structured development
• Native Salesforce ALM integration (Code Analyzer, DevOps Center)
• Agentforce Vibes 2.0 preview with Multi-Agent Swarms and Multi-framework React support
• 30+ pre-packaged Salesforce development skills

Weaknesses:

• Now requires payment for production use
• Credit consumption can be unpredictable with complex orgs
• Vendor lock-in to Salesforce’s AI ecosystem

Option B: Claude Code + Salesforce Hosted MCP Servers

Strengths:

• Use your existing Anthropic subscription or API key
• Same org access via Hosted MCP Servers (SObject CRUD, SOQL, invocable actions, flows)
• Works with any MCP-compatible client: Claude Desktop, Cursor, VS Code
• No per-org credit consumption — you control costs through your own API billing
• Can leverage the open-source Salesforce Skills library via npx skills add forcedotcom/sf-skills

Weaknesses:

• Less native Salesforce ALM integration
• Requires separate MCP server configuration per org
• No built-in Plan/Act mode workflow

Option C: Salesforce CLI + GitHub Copilot + DX MCP Server

For developers who prefer maximum control:

• Use Salesforce DX MCP Server locally with 60+ development tools
• Pair with GitHub Copilot or Cursor for code generation
• Access Salesforce CLI’s 220+ commands for deployment and testing
• Total cost control: you pay for your IDE AI subscription, not Salesforce credits

Impact on Different Stakeholder Profiles

Independent Developers and Consultants

This is the hardest-hit group. Consultants working across multiple client orgs now face a fundamental question: who pays for the credits? If every client org requires its own Flex Credit allocation, the cost multiplies rapidly. Community feedback on SalesforceBen captured this precisely: consultants may need to ask clients to sign up and allow credit consumption, which adds friction to engagements.

Recommendation: Evaluate Claude Code with Hosted MCP Servers for org-specific work. Use Agentforce Vibes Developer Edition for prototyping and learning.

Enterprise Development Teams

For organizations with dedicated Salesforce development teams, the $125/user/month flat license may be the cleanest option. Predictable costs, unmetered access, and native integration with existing Salesforce governance workflows. The alternative — managing API keys and MCP configurations across a team — introduces operational overhead.

Recommendation: Calculate your team’s expected monthly usage. If any developer exceeds ~25,000 credits/month regularly, the flat license is more cost-effective than Flex Credits.

Admins and Citizen Developers

Admins who used Agentforce Vibes occasionally to generate simple Flows or understand Apex code are the most likely to drop off. The free Developer Edition tier with 110 requests/month is sufficient for occasional use, but the lack of production org context limits its value for day-to-day admin work.

Recommendation: Use Developer Edition for learning and experimentation. For production admin work, invest in understanding Salesforce’s native automation tools (Flow Builder, Einstein for Flows) that do not require Agentforce Vibes.

Practical Steps to Transition

If You’re Staying with Agentforce Vibes

1. Audit your current usage: Check your org’s Agentforce Vibes usage reports to understand your monthly credit consumption pattern.
2. Choose your pricing model: Under ~25,000 credits/month → Flex Credits. Above that → flat license.
3. Optimize your prompts: Use Plan mode before Act mode. Be specific in your requests. Retrieve only relevant metadata.
4. Set up credit alerts: Monitor your Flex Credit balance to avoid unexpected depletion mid-sprint.

If You’re Moving to Claude Code + Hosted MCP

1. Set up a Hosted MCP Server: Navigate to Setup → Hosted MCP Servers in your Salesforce org. Configure OAuth authentication.
2. Install the Salesforce Skills library: Run npx skills add forcedotcom/sf-skills in your project directory to get pre-built Salesforce development skills.
3. Connect Claude Desktop or Cursor: Add the MCP server configuration to your client. The server exposes SObject CRUD, SOQL queries, invocable actions, and flows.
4. Test with a scratch org: Validate your new workflow against a scratch org before committing to production development.

If You’re Using the Hybrid Approach

The most pragmatic path for many teams will be a hybrid approach:

• Agentforce Vibes (free Developer Edition) for learning, experimentation, and prototyping
• Claude Code + Hosted MCP for daily development on production and sandbox orgs
• Salesforce CLI + DX MCP Server for deployment, testing, and CI/CD integration

The Bigger Picture: Headless 360 and the Future of Salesforce Development

Agentforce Vibes pricing is not happening in a vacuum. It is part of Salesforce’s broader Headless 360 strategy, which makes every platform capability available as an API, MCP tool, or CLI command. The implication is clear: Salesforce is building an ecosystem where you can use any coding agent with any tool to build on the platform.

The pricing change signals that Salesforce views Agentforce Vibes as a premium, differentiated product — not a commodity developer tool. The free tier served its purpose: it created adoption, generated 100 million lines of accepted code, and proved the value of AI-assisted Salesforce development. Now the business model needs to reflect that value.

For the ecosystem, this is arguably healthy. The availability of Hosted MCP Servers, the open-source Skills library, and the Headless 360 surface mean that developers are not locked into Agentforce Vibes. Competition between AI coding approaches — native Salesforce vs. third-party — will drive innovation and keep pricing in check.

Conclusion: Choose Deliberately, Not Reactively

The end of free Agentforce Vibes access is a significant moment for the Salesforce developer community. It forces a deliberate evaluation of how you build, what tools you depend on, and what you are willing to pay for AI-assisted development.

Do not panic-migrate to an alternative without understanding your actual usage patterns. Do not absorb the cost without evaluating whether the flat license or Flex Credits model fits your workflow. And do not overlook the powerful free alternatives that Salesforce itself now provides through Hosted MCP Servers and the open-source Skills library.

The developers who will navigate this transition most successfully are those who treat it as an architectural decision, not a billing surprise.

What is your team’s plan for the Agentforce Vibes pricing change? Are you staying, switching to Claude Code with MCP, or going hybrid? Share your strategy in the comments below.