name: full-access
description: Full system access mode for solo developers. Browser automation, filesystem, desktop, and all Rube integrations. No restrictions, maximum capability.
license: MIT
metadata:
author: thesimpleapp
version: "1.0"

Full Access Mode

Maximum capability for solo developers. Full access to everything.

Philosophy

Enterprise Mode:          Solo Developer Mode:
├── Restricted access     ├── Full access
├── Approval workflows    ├── Just do it
├── Audit trails          ├── Git history enough
└── Principle of least    └── Principle of maximum
    privilege                 capability

Access Layers

Layer 1: Browser Automation

Full browser control via Claude in Chrome:

CAPABILITIES:
├── Navigate to any URL
├── Take screenshots
├── Fill forms
├── Click elements
├── Scrape content
├── Execute JavaScript
├── Capture network requests
├── Read console logs
└── Record GIFs of actions

USE CASES:
- Debug web apps visually
- Scrape documentation
- Test user flows
- Capture bug reproductions
- Automate repetitive web tasks

Layer 2: Filesystem

Full read/write access:

CAPABILITIES:
├── Read any file
├── Write any file
├── Create directories
├── Delete files (with caution)
├── Move/rename files
├── Search entire disk
└── Access system files

USE CASES:
- Edit config files anywhere
- Access logs in /var/log
- Modify system settings
- Batch file operations
- Cross-project file access

Layer 3: Desktop Automation

System-level control:

CAPABILITIES:
├── Launch applications
├── Window management
├── Screenshot desktop
├── Clipboard access
├── Keyboard/mouse simulation
└── Process management

USE CASES:
- Automate IDE actions
- Capture app state
- Cross-app workflows
- System diagnostics

Layer 4: Network

Full network access:

CAPABILITIES:
├── HTTP/HTTPS requests
├── WebSocket connections
├── API calls (authenticated)
├── Webhook handling
└── Database connections

USE CASES:
- Direct API integration
- Database queries
- External service calls
- Real-time data streams

Layer 5: Rube Integrations

500+ app integrations:

CONNECTED:
├── Supabase (12 projects)
├── GitHub (TheSimpleApp)
├── Notion (Simple. workspace)
├── Firecrawl (web scraping)
└── [500+ more available]

AVAILABLE VIA OAUTH:
├── Vercel (deployments)
├── Fireflies (meeting transcripts)
├── Slack (messaging)
├── Linear (project management)
├── Gmail (email)
└── Google Sheets (data)

Quick Commands

Browser

"Screenshot the current page"
→ mcp__claude-in-chrome__computer action="screenshot"

"Navigate to https://example.com"
→ mcp__claude-in-chrome__navigate url="..."

"Click the login button"
→ mcp__claude-in-chrome__computer action="click" coordinate=[x, y]

"Fill the email field with [email protected]"
→ mcp__claude-in-chrome__form_input

Filesystem

"Read the nginx config"
→ Read /etc/nginx/nginx.conf

"Find all .env files on my system"
→ Glob pattern="**/.env" path="~"

"Write this config to ~/.config/app/settings.json"
→ Write file_path="..." content="..."

Rube Services

"Query my Supabase users table"
→ SUPABASE_BETA_RUN_SQL_QUERY ref="..." query="SELECT * FROM users"

"Create a GitHub issue"
→ GITHUB_CREATE_AN_ISSUE owner="..." repo="..." title="..."

"Add notes to my Notion page"
→ NOTION_ADD_MULTIPLE_PAGE_CONTENT parent_block_id="..."

Power Workflows

Workflow 1: Debug with Screenshots

1. Browser: Navigate to app
2. Browser: Screenshot current state
3. Browser: Click problematic element
4. Browser: Screenshot error state
5. Browser: Capture console logs
6. Analyze all captures
7. Identify root cause

Workflow 2: Cross-App Automation

1. Fireflies: Get today's meeting transcript
2. Parse: Extract action items
3. GitHub: Create issues for each
4. Notion: Update project page
5. Slack: Notify team

Workflow 3: Full Stack Debug

1. Browser: Capture frontend error
2. Supabase: Query recent logs
3. Supabase: Check database state
4. GitHub: Find recent commits
5. Synthesize root cause
6. Fix code
7. Browser: Verify fix

Workflow 4: Deployment Pipeline

1. GitHub: Check latest commit
2. Run local tests
3. GitHub: Create PR
4. Vercel: Deploy preview
5. Browser: Screenshot preview
6. Verify: Test critical paths
7. Vercel: Deploy production

Safety Considerations

Even with full access, be mindful:

CAUTION:
├── Production database writes
├── Deleting system files
├── Sending emails/messages
├── Making purchases
├── Modifying credentials
└── Irreversible operations

ALWAYS SAFE:
├── Reading files
├── Screenshots
├── Analysis
├── Local development
├── Git operations (with commits)
└── Database reads

Confirmation Pattern

For destructive actions:

"I'm about to delete 50 files. Confirm?"
→ User confirms
→ Proceed

"This will send emails to 100 users. Confirm?"
→ User confirms
→ Proceed

Configuration

Enable Full Access

// ~/.config/claude-code/settings.json
{
  "permissions": {
    "filesystem": "full",
    "browser": "full",
    "network": "full",
    "desktop": "full"
  },
  "confirmDestructive": true,
  "autoApprove": ["read", "screenshot", "query"]
}

MCP Servers Required

// MCP configuration
{
  "mcpServers": {
    "claude-in-chrome": { ... },
    "rube": { ... },
    "filesystem": { ... }
  }
}

Integration

/full-access          → All permissions enabled
       ↓
/parallel-swarm       → Agents inherit permissions
       ↓
/rube-hub             → 500+ app integrations
       ↓
Maximum capability unlocked

Comparison

Regular Mode:           Full Access Mode:
├── Ask before write    ├── Write freely
├── Sandboxed browser   ├── Full browser control
├── Limited integrations├── 500+ integrations
├── Single project      ├── Cross-project access
└── Conservative        └── Aggressive efficiency