MyIntern VSCode Extension

Compliance-first AI coding agent that fixes production errors while you sleep. Self-hosted, BYOK, with audit trails and guardrails. Built for teams with HIPAA/PCI-DSS compliance requirements.

Security First: This extension has undergone comprehensive security hardening including command injection prevention, path traversal protection, and safe YAML parsing.

Features

🚀 Spec-Driven Workflow

• Create specification files from code selections
• Track spec status in real-time (pending, running, completed, failed)
• Preview changes with interactive diff viewer
• Approval workflow: Accept, reject, or revert changes
• Integrated backup system for safe rollbacks

🛡️ Built-in Guardrails

• Real-time security scanning
• HIPAA/PCI-DSS compliance checks
• SQL injection detection
• Hardcoded secrets detection
• Unsafe deserialization warnings

📊 Visual Status Tracking

• Tree view of all specs in .myintern/specs/
• Status bar integration
• Execution logs and history
• Inline code decorations for violations

🤖 CLI Integration

• Start/stop MyIntern watcher from VSCode
• Real-time CLI output in integrated terminal
• Automatic file watching and recompilation

Installation

Prerequisites

⚠️ IMPORTANT: This extension requires the MyIntern CLI to be installed. The extension is a visual companion that provides UI for the CLI - it cannot function standalone.

1. Install MyIntern CLI (REQUIRED):

   npm install -g myintern
   myintern --version  # Verify: 1.2.3 or higher
   

2. Install VSCode Extension:

   • Open VSCode Extensions (Cmd+Shift+X)
   • Search "MyIntern"
   • Click "Install"

3. Initialize Your Project:

   cd your-spring-boot-project
   myintern init
   

Security Best Practices

This extension has been security-hardened to enterprise standards (Security Score: 9/10):

What's Protected:

• ✅ Command Injection Prevention: CLI path is validated and spawned without shell
• ✅ Path Traversal Protection: Spec names cannot escape .myintern/specs/ directory
• ✅ Safe YAML Parsing: Uses FAILSAFE_SCHEMA to prevent code execution
• ✅ Async File Operations: No blocking I/O, with atomic write operations
• ✅ Input Validation: All user inputs are strictly validated before use

Your Responsibilities:

• ✅ Only use the official MyIntern CLI from npm (npm install -g myintern)
• ✅ Verify CLI path in settings (default: myintern resolves from PATH)
• ✅ Never set myintern.cliPath to untrusted executables or shell scripts
• ✅ Keep both CLI and extension updated to latest versions
• ✅ Review diff preview before accepting changes

Security Features:

• Real-time guardrails for HIPAA/PCI-DSS compliance
• Approval workflow with diff preview before applying changes
• Health monitoring of CLI process
• Comprehensive error handling without information disclosure

Quick Start

1. Create Your First Spec

1. Select code in your editor
2. Right-click → MyIntern: Create Spec from Selection
3. Enter a spec name (e.g., FEATURE_001)
4. Edit the generated spec file

2. Start the Watcher

• Click the MyIntern icon in the Activity Bar
• Click the Play button in the Specs view
• Or run: MyIntern: Start Watching from Command Palette

3. Monitor Progress

• Watch spec status in the tree view
• Check execution logs in the Output panel
• Preview changes with the diff viewer

Commands

Configuration

Settings

{
  "myintern.cliPath": "myintern",
  "myintern.autoStart": false,
  "myintern.showStatusBar": true
}

agent.yml

MyIntern reads configuration from .myintern/agent.yml:

agent:
  name: "MyIntern"
  version: "1.0"

llm:
  provider: "openai"
  model: "gpt-4"
  temperature: 0.2

tech_stack:
  language: "Java"
  framework: "Spring Boot 3.x"
  build_tool: "Maven"

guardrails:
  require_tests: true
  min_coverage: 80
  security_scan: true
  compliance:
    - "HIPAA"
    - "PCI-DSS"

paths:
  source: "src/main/java"
  tests: "src/test/java"
  specs: ".myintern/specs"
  logs: ".myintern/logs"

Guardrails

MyIntern enforces compliance through real-time guardrails:

Security Rules

• NO_HARDCODED_SECRETS: Detects passwords, API keys in code
• PREVENT_SQL_INJECTION: Ensures parameterized queries
• SAFE_DESERIALIZATION: Validates object deserialization

Compliance Rules

• HIPAA_AUDIT_LOGGING: Enforces audit trails
• HIPAA_ENCRYPTION: Requires encryption for PHI
• PCI_DATA_MASKING: Masks credit card numbers

Violations appear as inline warnings in your editor.

Spec File Format

# FEATURE: FEATURE_001

**Type:** feature
**Priority:** high

## Description
Add user authentication with JWT tokens

## Acceptance Criteria
- Implement JWT token generation
- Add login/logout endpoints
- Secure endpoints with @PreAuthorize
- Add unit tests with 80%+ coverage

## Files Likely Affected
- src/main/java/com/example/auth/

## Notes
Follow Spring Security 6.x best practices

Tree View

The extension provides a tree view showing:

• 📝 Pending specs (blue circle)
• 🔄 Running specs (yellow spinner)
• ✅ Completed specs (green check)
• ❌ Failed specs (red error)

Output Channels

MyIntern creates two output channels:

1. MyIntern - CLI watcher output
2. MyIntern Extension - Extension logs

Troubleshooting

CLI Not Found

Error: myintern command not found

Solution: Install MyIntern CLI globally:

npm install -g myintern-cli

No Specs Appearing

Solution: Ensure .myintern/specs/ directory exists with .md files

Guardrail Decorations Not Showing

Solution: Enable in settings:

{
  "myintern.showStatusBar": true
}

Requirements

• VSCode: 1.80.0 or higher
• MyIntern CLI: 1.2.3 or higher (REQUIRED - install from npm)
• Node.js: 20+ (for MyIntern CLI)
• Java: 17+ (for Spring Boot projects)
• Build Tool: Maven or Gradle

License

BSD-3-Clause

Support

• GitHub Issues: myintern-vscode/issues
• Documentation: myintern.dev/docs

Changelog

See CHANGELOG.md for version history.