Skip to content

docs(security): reflect Security Agent availability in docs - #10898

Merged
johnnyeric merged 3 commits into
Kilo-Org:mainfrom
IamCoder18:docs/security-agent-availability
Jun 5, 2026
Merged

docs(security): reflect Security Agent availability in docs#10898
johnnyeric merged 3 commits into
Kilo-Org:mainfrom
IamCoder18:docs/security-agent-availability

Conversation

@IamCoder18

Copy link
Copy Markdown
Contributor

Issue

Fixes #10897

Context

The docs for Security Agent (packages/kilo-docs/pages/deploy-secure/security-reviews.md) incorrectly claimed the feature was restricted to Teams and Enterprise plans. The actual frontend shows Security Agent is available unconditionally.This mismatch could confuse personal users into thinking they can't access Security Agent when they can.

Implementation

Updated one line in packages/kilo-docs/pages/deploy-secure/security-reviews.md, replacing the plan restriction with a statement that Security Agent is available for all users. No code refactoring or product changes were needed.

Screenshots / Video

before after
image image

How to Test

Manual/local verification

In packages/kilo-docs, run bun run test and visit /docs/deploy-secure/security-reviews.

Checklist

  • Issue linked above, or exception explained
  • Tests/verification described
  • Screenshots/video included for visual changes, or marked N/A
  • Changeset considered for user-facing changes
  • I personally reviewed the diff and can explain the changes, including any AI-assisted work.

Get in Touch

Discord: @IamCoder18

The previous docs stated Security Agent was restricted to Teams and
Enterprise plans, which no longer matches the product behavior.

The personal and organization sidebars both expose Security Agent
unconditionally, with no plan gate or feature flag. This keeps the
docs aligned with that behavior.

Reason for change: docs were out of sync with UI/backend access rules.
@vercel

vercel Bot commented Jun 4, 2026

Copy link
Copy Markdown

@IamCoder18 is attempting to deploy a commit to the Kilo Code Team on Vercel.

A member of the Team first needs to authorize it.

@kilo-code-bot

kilo-code-bot Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)
  • packages/kilo-docs/pages/deploy-secure/security-reviews.md

Reviewed by claude-4.6-sonnet-20260217 · 200,834 tokens

Review guidance: REVIEW.md from base branch main

@johnnyeric
johnnyeric requested a review from jeanduplessis June 4, 2026 12:27
@johnnyeric
johnnyeric merged commit e02efb5 into Kilo-Org:main Jun 5, 2026
17 of 18 checks passed
t7tran pushed a commit to t7tran/kilocode that referenced this pull request Aug 14, 2026
…#10898)

The previous docs stated Security Agent was restricted to Teams and
Enterprise plans, which no longer matches the product behavior.

The personal and organization sidebars both expose Security Agent
unconditionally, with no plan gate or feature flag. This keeps the
docs aligned with that behavior.

Reason for change: docs were out of sync with UI/backend access rules.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs(security-agent): reflect Security Agent availability in docs

3 participants