Cohere North 2 keeps agent memory and caps token spend

Cohere North 2 adds cross-session agent memory and North Admin flow control, with request and token-rate tiers for users and groups.

On 2026-10-05, Cohere announced North 2, an enterprise agent platform with cross-session memory, a redesigned multi-step orchestration system, and North Admin controls for request and token rates. Flow control uses consumption tiers for users and groups, while the platform runs in cloud, on-premises, virtual private cloud, hybrid, or air-gapped deployments. Cohere's launch page gives no list price and directs prospective customers to contact sales for a demo.

Cohere North 2 key facts

  • Cohere's official X post on 2026-10-05 described North 2 as having more than 15 new features.
  • North 2 memory keeps agent context across sessions instead of starting cold each time.
  • North Admin flow control defines consumption tiers based on request and token rates for users and groups.
  • North Admin provides visibility down to the user and agent level, organization-wide caps, and alerts before limits are reached.
  • Cohere lists self-hosted, virtual private cloud, hybrid, on-premises, and fully air-gapped deployment options.
  • North 2 is model agnostic. Organizations can use Cohere models or bring existing models.
  • Listed connectors include Slack, SharePoint, OneDrive, Microsoft Outlook, Microsoft Exchange, Jira, Linear, Notion, and GitHub. Cohere lists PitchBook, Crunchbase, Daloopa, FiscalAI, S&P Global, and FactSet as planned financial data providers.

How Cohere North 2 orchestrates agents and retains memory

Cohere says North 2's orchestration system manages complex, multi-step processes independently while keeping humans in the loop where it matters. Users can build agents and automations with prompts, share reusable agents across the organization, and prototype documents or apps in chat.

North 2 groups these capabilities into named features:

  • Memory keeps context across sessions.
  • Skills are reusable capabilities that agents can call instead of rebuilding the same logic.
  • Libraries hold shared knowledge and assets for the organization.
  • Automations provide templates, a drag-and-drop workflow builder, real-time monitoring, and integrations.
  • Applications let users prototype and ship decks, dashboards, documents, and lightweight apps from natural-language prompts.

Cohere lists nine enterprise connectors for Slack, SharePoint, OneDrive, Microsoft Outlook, Microsoft Exchange, Jira, Linear, Notion, and GitHub. It lists planned financial data providers including PitchBook, Crunchbase, Daloopa, FiscalAI, S&P Global, and FactSet.

How North Admin controls token spend and access

North Admin is the governance console for usage, permissions, models, and agent guardrails. Cohere says administrators can inspect AI investment usage, including token spend and limits, with visibility down to the user and agent level.

Flow control defines consumption tiers based on two measures:

  • Request rates: The launch post says tiers can be based on requests for users and groups.
  • Token rates: The launch post says tiers can be based on token rates for users and groups.

The same post lists organization-wide caps and alert thresholds that warn teams before limits are reached. It does not specify the time window, token accounting dimensions, or enforcement order, so those details should not be inferred from the announcement.

North Admin capability

What the sources say

Flow control

Consumption tiers based on requests and token rates for users and groups

Usage visibility

Analytics and visibility down to users and agents

Caps and alerts

Organization-wide caps and warnings before limits

Data access

Access control lists for libraries and skills

Autonomy

Authorized actions and human oversight for critical decisions

Model choice

Control over which models are used where and by whom, with Cohere or existing customer models

The Register reports that administrators can assign ACLs to libraries and skills, limiting access to shared data and capabilities. SiliconANGLE reports that North Admin guardrails screen PII in prompts and responses and attempted prompt injection. Cohere says autonomy policies limit agents to authorized actions and seek human oversight for critical decisions.

Cohere North 2 deployment and model choices

Cohere describes North 2 as deployable in several environments:

  • Self-hosted or on-premises deployments.
  • Virtual private cloud (VPC) deployments.
  • Hybrid deployments.
  • Fully air-gapped deployments with no outside connection.

Cohere lists SOC 2 Type 2, ISO 27001, and ISO 42001 certifications. North is model agnostic, so an organization can use Cohere's generative models or bring existing models.

Cohere says its collaboration with NVIDIA produces more tokens per second per node when Cohere models run on NVIDIA Blackwell and Hopper hardware, which can reduce spend. That is a vendor-reported performance claim, not an independent cost benchmark.

What Cohere North 2 does not specify

The 2026-10-05 launch page says North 2 memory keeps context across sessions. It does not state a retention period, storage location, deletion mechanism, or memory-specific administrator control. A 2026-10-05 BERI analysis flags the same omissions. Treat memory scope and retention as open procurement questions, not documented North 2 behavior.

The launch page gives no list price and points prospective customers to contact sales for a demo.

Sources

Last verified: 2026-10-06.

Spotted an outdated or wrong claim? Agents can report it with evidence throughPOST /api/feedback; an editor checks every report. See llms.txt for the agent API.