Salesforce Agentforce Vibes Free Access Ends in June 2026

Introduction: Salesforce Agentforce Vibes

Developers who have grown accustomed to using Salesforce Agentforce Vibes at no cost are facing a significant deadline. As of June 1, 2026, the free tier of agentic chat within Agentforce Vibes will no longer be available for most organizations. This marks a pivotal moment for the Salesforce development community, as the company transitions from offering unlimited free access to a consumption-based pricing model. For organizations relying on Agentforce Vibes as their primary development tool, understanding this transition is critical to maintaining productivity and managing costs.

What is Salesforce Agentforce Vibes?

Before diving into the pricing changes, it’s important to understand what Agentforce Vibes is and why developers have embraced it so readily. Agentforce Vibes is Salesforce’s enterprise-grade, AI-powered coding assistant that enables developers to write code using natural language prompts—a concept often referred to as “vibe coding.” Rather than writing Apex, Lightning Web Components (LWCs), or Flows manually, developers can describe what they want in plain English, and the AI agent, known as “Vibe Codey”, generates the code automatically.

The standout feature of Agentforce Vibes is its deep integration with Salesforce metadata. Unlike general-purpose AI coding tools, Vibes understands your organisation’s schema, existing code patterns, and custom configurations. When you ask it to “create a trigger that prevents duplicate accounts based on email”, it first reads your actual org structure and follows your established coding guidelines. This org-aware capability significantly reduces development time and minimises the risk of introducing inconsistencies or security vulnerabilities.

Agentforce Vibes operates within an Agentforce Vibes IDE, a browser-based, cloud-hosted Visual Studio Code environment. No local installation is required; developers can launch it directly from their Salesforce setup menu, complete with preconfigured Salesforce extensions, Salesforce CLI, and GitHub integration.

The June 1, 2026 Transition

The news came as a pop-up notification within the AgentForce Vibes interface, alerting users that starting June 1, 2026, agentic chat will require either Flex Credits or a paid user licence. For organizations already leveraging this tool in production environments, the transition demands immediate planning and budgeting considerations.

This shift applies primarily to non-Developer Edition organizations. Any Salesforce org outside of the free Developer Edition tier will need to transition to a paid access model to continue using Agentforce Vibes’ agentic chat capabilities. Organizations that have been experimenting with or actively using Vibes in their paid environments will face the most significant impact, as they lose the fallback to free usage entirely.

Who Is Impacted

This change has a broad impact, but it varies by organization type:

Production and Paid Orgs:

Salesforce will hit the organisations that run it in production environments the hardest. If your team has been using Agentforce Vibes at no cost and sharing your organisation’s metadata to provide context for AI-driven decisions, you’re now required to pay. There’s no longer a safety net or fallback option once you’ve made the investment.

Active Teams:

Any team that has been actively using Agentforce Vibes in a paid environment for solutions that require org context will need to shift to a paid subscription. This includes teams using Vibes for Apex development, Lightning component creation, Flow automation, and org customisations.

Developer Edition Users:

Surprisingly, Developer Edition organizations will retain some free access, but with critical limitations. The free allocation for the Developer Edition is now a lifetime limit of 110 requests or 1.5 million tokens on the Pro model (Claude Sonnet 4.5). Once exhausted, there’s no monthly refresh and no fallback to the core model. The new model is dramatically different from the previous experience.

New Pricing and Licensing Models

Salesforce has introduced two primary pathways for paid access to Agentforce Vibes:

1. Flex Credits

Flex Credits represent Salesforce’s consumption-based purchasing model. Developers pay based on actual usage, making this option potentially suitable for teams with variable or unpredictable usage patterns. However, specific pricing details are noted as “coming soon”, so organizations should monitor Salesforce’s official documentation for updated rates.

2. Unmetered Platform Developer and Admin AI User Permission Set License

This licence removes metered limits on Vibes, making it ideal for teams using the tool daily or extensively. Organizations choosing this route can leverage Agentforce Vibes without worrying about hitting usage thresholds during the month. For teams committed to a vibe-coding workflow, this option may prove more cost-effective than pay-as-you-go Flex Credits.

The Two-Tier LLM Approach

Salesforce has structured Agentforce Vibes around a two-tier language model system designed to balance cost and quality.

Pro Model (Claude Sonnet 4.5):

This is the premium tier used for chat and interactive experiences. It’s automatically invoked first, with a limit of 110 requests or 1.5 million tokens per organization per month. Once these limits are exhausted, the system falls back to the core model.

Core Model (GPT-5 mini):

After Pro limits are reached, the Core model takes over, allowing 1,500 requests or 15 million tokens per organization each month. This provides extended functionality but at a potentially reduced quality level compared to the Pro model.

Inline Autocomplete (GPT-4.1):

A separate tier handles inline code completion, with 1,500 requests or 15,000 tokens per organization per day. This feature remains available separately and isn’t tied to the chat agentic limits.

An important nuance: all limits are calculated at the organization level, not the individual user level. This means that if your team of five developers all using Vibes shares a monthly allocation, your collective usage adds up quickly and can deplete limits faster than expected.

Developer Edition: A Limited Free Alternative

For organizations seeking to avoid paid subscriptions, Salesforce Developer Edition offers a path forward—though with significant constraints. Developer Edition orgs will retain free access to Agentforce Vibes, but with a critical difference: the 110 requests and 1.5 million tokens on Claude Sonnet 4.5 represent a lifetime limit for that organization, not a monthly renewal.

This approach is suitable for non-production experimentation, prototyping, or organizations building solutions that don’t require extensive org metadata context. However, for teams actively developing production applications or conducting deep investigations into complex implementations, the lifetime limit is likely insufficient.

Why Salesforce Made This Change

Salesforce positions this transition as necessary to meet enterprise-scale development demands. By shifting to a paid model, the company can allocate resources toward offering higher-quality language models and expanded capacity. Managing infrastructure costs while delivering premium models at scale requires moving away from unlimited free access.

Furthermore, GPT-5’s availability as a model option—launching on June 1 alongside the new pricing structure—signals Salesforce’s commitment to providing cutting-edge AI capabilities to paying customers. The company is investing in better models and more sophisticated features, and the paid model funds these improvements.

Competition and Alternatives

The timing of this transition is notable given the competitive landscape. Developers now have several compelling alternatives:

GitHub Copilot remains the most widely adopted AI coding assistant, with broad language and framework support. While not Salesforce-specific, it’s cheaper and integrates seamlessly into most development environments.

Claude Code offers deep agentic capabilities and codebase-wide analysis. Combined with appropriate Salesforce skills and Salesforce’s new Model Context Protocol (MCP) capabilities, it provides an alternative workflow for Salesforce development.

Cursor and other specialised editors also offer strong agentic coding features at lower price points than enterprise tools.

For Salesforce developers, the real question is whether Agentforce Vibes’ org-aware capabilities and native IDE integration justify the premium cost compared to general-purpose alternatives enhanced with Salesforce context via external tools.

Action Items for Developers and Orgs

Organizations should take the following steps before June 1, 2026:

1. Assess Current Usage: Evaluate how intensively your teams are using Agentforce Vibes and what level of usage you’ll need going forward.
2. Budget Planning: Obtain pricing details for Flex Credits and the Unmetered PSL, then calculate projected costs based on your usage assessment.
3. Licence Purchasing: Decide between Flex Credits or the unmetered platform developer and admin AI user licence, and initiate the procurement process if necessary.
4. Alternative Evaluation: Explore competitive options to ensure Salesforce Vibes remains the best choice for your use cases.
5. Developer Communication: Inform your development teams of the change and new constraints, particularly the org-level usage pooling model.
6. Optimiser Usage: For teams choosing to continue with paid access, learn strategies to optimize token usage—such as using Plan mode before Act mode, writing specific prompts, and retrieving only relevant metadata.

Conclusion

The June 1, 2026 transition marks the end of unlimited free access to AgentForce Vibes’ agentic chat capabilities for production environments. While this change may surprise developers accustomed to free access, it reflects Salesforce’s broader strategy to deliver enterprise-grade AI features backed by premium language models. Organizations must now make deliberate choices about whether to invest in paid access, optimize usage patterns, or explore alternative tooling.

For teams heavily invested in Salesforce development, Agentforce Vibes’ org-aware capabilities and seamless integration may justify the investment. For others, the competitive landscape offers viable alternatives at lower price points. Regardless, the time to plan and budget for this transition is now—before the June 1 deadline arrives.