Skip to content

Code mode: plan/edition gating and Cloud runner operations #1365

Closed

Description

@helpcodeai

Summary

Plan/edition gating and Cloud operations for code mode. Depends on #1361–#1363 and the inline-tools issue.

Gating (no separate SKU; gate by capability inside existing plans)

  • Saved code tools: capped per plan (Community 3 / Starter 5 / Team 20 / Enterprise unlimited) via license features.
  • Inline code_execute: Team+ , as the Role.capabilities.inlineCode capability (Team already sells custom roles; Starter is 1 user / card-less trial).
  • Writes in code tools, runAs: definer, code mode on the shared /mcp, dedicated runner, long audit retention: Enterprise only, via EditionService.assertEnterprise.
  • Cloud run quotas: monthly caps (Starter 500 / Team 5,000 / Enterprise volume), upgrade prompt via a new checkout source code_tool_limit; no metered overage in year one. Trial: code tools yes, inline only with a card.
  • Audit retention 7 / 30 / 90 days / 1y+.

Cloud operations (Phase 3)

  • Add the code-runner as a dedicated service in the Cloud deployment (blue/green release flow, its own CPU/memory limits), with CODE_RUNNER_URL set on the backend.
  • Gate rollout behind a pen test of the runner.

Notes

Runner + method: 'code' live in AGPL core; the gate lives in EditionService (ee/), like SSO, so "AnythingMCP has an open-source code mode" stays an adoption argument while the richer tiers are paid.

Activity

  1. helpcodeai commented on Oct 31, 2026

    @helpcodeai
    ContributorAuthor

    Gating mechanism implemented (commit 1a4bbc7 and earlier): LicenseGuardService.checkCanCreateCodeTool enforces features.maxCodeTools (hard on the Cloud trial, soft on paid tiers, like connectors/servers) so the per-plan number lives on the licensing site, not in code; write-capable code tools require Enterprise (assertEnterprise); definer rights require admin; inline code is gated by the inlineCode role capability. Still open and intentionally NOT in this repo (operational, per AGENTS.md 'no Cloud operator procedures'): wiring the code-runner into the Cloud blue/green deployment and the monthly run quotas. Those remain for the Cloud ops side.

  2. helpcodeai commented on Oct 31, 2026

    @helpcodeai
    ContributorAuthor

    Delivered in PR #1366 (merged into main as be4742a). Code mode ships off by default; the agent-proposal follow-up is tracked in #1369, and the Cloud runner operations in this issue remain operational/out-of-repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions