Merge pull request #2 from HacktronAI/chore/workbench-removal

chore: list workbench as deprecated + remove related docs files

Author: zeyu2001

docs.json

@@ -48,37 +48,6 @@
             ]
           }
         ]
-      },
-      {
-        "tab": "Workbench",
-        "groups": [
-          {
-            "group": "Overview",
-            "pages": ["workbench/overview", "workbench/skills"]
-          },
-          {
-            "group": "CLI",
-            "pages": [
-              "workbench/cli/quickstart",
-              "workbench/cli/agents",
-              "workbench/cli/sessions",
-              "workbench/cli/shell"
-            ]
-          },
-          {
-            "group": "IDE Extensions",
-            "pages": [
-              "workbench/ide-extensions/quickstart",
-              "workbench/ide-extensions/background-sessions",
-              "workbench/ide-extensions/byok",
-              "workbench/ide-extensions/personal-agents"
-            ]
-          },
-          {
-            "group": "Resources",
-            "pages": ["workbench/changelog"]
-          }
-        ]
       }
     ],
     "global": {

index.mdx

@@ -45,23 +45,8 @@ Meet the next generation of AI-native tools built for developers, security engin
   </Card>
 </Columns>
 
-## Hacktron Workbench
+## Hacktron Workbench (Deprecated)
 
-<Columns cols={2}>
-  <Card
-    title="CLI Quickstart"
-    icon="terminal"
-    href="/workbench/cli/quickstart"
-    horizontal
-  >
-    Get started with the Hacktron CLI in under 5 minutes.
-  </Card>
-  <Card
-    title="IDE Extensions"
-    icon="code"
-    href="/workbench/ide-extensions/quickstart"
-    horizontal
-  >
-    Install Hacktron in VS Code, Cursor, and Windsurf.
-  </Card>
-</Columns>
+<Warning>
+  Hacktron Workbench has been deprecated. The CLI and IDE extensions are no longer available.
+</Warning>

platform/billing-access.mdx

@@ -42,13 +42,12 @@ Roles control what someone can do in the Platform.
 Seats are separate from roles.
 
 - A **Dev seat** covers pull request reviews.
-- A **Sec seat** is assigned in the Platform and gives access to Workbench.
 
 In short, a **Role** controls Platform permissions, while a **Seat** controls paid product access. A person can have a seat without Platform access, and a person can also have Platform access without a seat.
 
 If someone has no Platform role assigned, they appear as **Unassigned** in **People**.
 
-Someone with Platform access only is not charged unless they also have a Dev seat or Sec seat.
+Someone with Platform access only is not charged unless they also have a Dev seat.
 
 ## Example scenarios
 
@@ -61,11 +60,10 @@ Someone with Platform access only is not charged unless they also have a Dev sea
 | Email | `john@hacktron.ai` |
 | Role | **Unassigned** |
 | Dev seat | Yes |
-| Sec seat | Yes |
 
-Transition: An owner invites the person by email and assigns seats.
+Transition: An owner invites the person by email and assigns a seat.
 
-Access: Workbench only. No Platform access until an admin assigns a role.
+Access: No Platform access until an admin assigns a role.
 
 #### State 2: signed in with GitHub, still no role
 
@@ -75,11 +73,10 @@ Access: Workbench only. No Platform access until an admin assigns a role.
 | Email | `john@hacktron.ai` |
 | Role | **Unassigned** |
 | Dev seat | Yes |
-| Sec seat | Yes |
 
 Transition: The person signs in and their identity is linked to the existing record.
 
-Access: Workbench only. They still do not have Platform access.
+Access: They still do not have Platform access.
 
 #### State 3: role assigned
 
@@ -88,11 +85,10 @@ Access: Workbench only. They still do not have Platform access.
 | Email | `john@hacktron.ai` |
 | Role | **Viewer** |
 | Dev seat | Yes |
-| Sec seat | Yes |
 
 Transition: An admin assigns a Platform role such as **Viewer**.
 
-Access: Viewer access in the Platform, plus Workbench access.
+Access: Viewer access in the Platform.
 
 ### Existing GitHub developer
 
@@ -104,7 +100,6 @@ Access: Viewer access in the Platform, plus Workbench access.
 | Email | `-` |
 | Role | **Unassigned** |
 | Dev seat | Yes |
-| Sec seat | No |
 
 Transition: A developer opens a PR and is added to **People** with a Dev seat.
 
@@ -118,37 +113,33 @@ Access: No Platform access. PR reviews are covered because the person has a Dev
 | Email | `john@hacktron.ai` |
 | Role | **Unassigned** |
 | Dev seat | Yes |
-| Sec seat | No |
 
 Transition: The person signs in and their email is linked to the existing record.
 
 Access: Still no Platform access.
 
-#### State 3: role and Sec seat assigned
+#### State 3: role assigned
 
 | State | Value |
 | --- | --- |
 | Email | `john@hacktron.ai` |
 | Role | **Viewer** |
 | Dev seat | Yes |
-| Sec seat | Yes |
 
-Transition: An admin assigns a Platform role and optionally adds a Sec seat.
+Transition: An admin assigns a Platform role.
 
-Access: Viewer access in the Platform, plus Workbench access.
+Access: Viewer access in the Platform.
 
 ## Billing
 
 The Billing page is split into:
 
 - **Seats plan**
 - **Pentest credits**
-- **CLI credits**
 
 Billing is driven by product entitlements:
 
 - **Dev seats** affect code review billing
-- **Sec seats** affect Workbench entitlement, including the credits available there
 - **Pentest credits** are shared across the organization
 - **Roles** do not create charges by themselves
 
@@ -162,9 +153,6 @@ During the trial:
 
 - Dev seats auto-assign as PR activity comes in
 - There is no hard seat cap, but usage is limited to **200 PRs per seat**
-- The organization creator starts with **200 free Workbench credits**
-
-Once a paid Sec seat is assigned, that free 200-credit Workbench allowance is removed.
 
 ## Seat changes
 

platform/quickstart.mdx

@@ -28,16 +28,11 @@ If you choose **With my team**, GitHub is usually the main setup step. Slack is
 
 ## Who the Platform is for
 
-The Platform is for shared, organization-level work. It also connects directly to Workbench, because this is where seats and access are managed for the organization.
+The Platform is for shared, organization-level work. This is where seats and access are managed for the organization.
 
-<Columns cols={2}>
-  <Card img="/images/platform-persona-team-reference.png">
-    Use the Platform for shared setup across the organization, including continuous code reviews across repositories, pentests, teammates, and centralised billing.
-  </Card>
-  <Card img="/images/platform-persona-individual-reference.png">
-    Use Workbench for work that happens directly in code. The CLI and the IDE extensions work alongside the Platform to provide security workflows in your terminal and editor.
-  </Card>
-</Columns>
+<Card img="/images/platform-persona-team-reference.png">
+  Use the Platform for shared setup across the organization, including continuous code reviews across repositories, pentests, teammates, and centralised billing.
+</Card>
 
 ## Initial setup
 
@@ -59,21 +54,6 @@ The Platform is split into a few key pages:
 - **Billing** manages seats, credits, and shared budgets
 - **Pentests** is for larger, scoped assessments beyond day-to-day review
 
-## Platform vs Workbench
-
-Workbench is an integral part of the Platform, built for individual usage.
-
-Apart from providing access to Workbench, the Platform is used to manage:
-
-- repository coverage
-- people and roles
-- billing, seats, and credits
-- pentests and other org-level activity
-
-Use Workbench when you are doing the work itself in code through the CLI or IDE.
-
-For example, someone might be invited through the Platform, assigned a Sec seat there, and then use that access and those credits in Workbench.
-
 <Columns cols={2}>
   <Card title="Code Reviews" icon="code-pull-request" href="/platform/code-reviews">
     Learn how to connect repos and get PR reviews running.
@@ -84,7 +64,4 @@ For example, someone might be invited through the Platform, assigned a Sec seat
   <Card title="Pentests" icon="shield-halved" href="/platform/pentests">
     Run scoped pentests with shared organization credits.
   </Card>
-  <Card title="Workbench" icon="terminal" href="/workbench/cli/quickstart">
-    Use the CLI and IDE extension alongside the Platform.
-  </Card>
 </Columns>