Skip to main content

Security Commands

NikCLI provides comprehensive security features to protect your development environment and control AI agent permissions. These commands help you manage security policies, approval workflows, and development modes.

Core Security Commands

/security [action]

Main security management command with multiple configuration options. Syntax:
Available Actions:
  • status - Show current security configuration
  • enable - Enable security features
  • disable - Disable security features
  • policy - Manage security policies
  • audit - Security audit and scan
  • permissions - Manage permissions
Examples:
Security Status Output:

/dev-mode [on|off]

Toggle development mode for enhanced AI agent capabilities. Syntax:
Options:
  • on - Enable development mode
  • off - Disable development mode
  • --temporary - Enable for current session only
  • --timeout <minutes> - Auto-disable after timeout
Features in Dev Mode:
  • Broader file system access
  • Network operations allowed
  • Reduced approval requirements
  • Enhanced debugging capabilities
  • Extended tool access
Examples:
Security Implications:
  • ⚠️ Reduced security restrictions
  • ⚠️ AI agents can modify more files
  • ⚠️ Network access enabled
  • ⚠️ Fewer approval prompts
  • βœ… Enhanced development capabilities

/safe-mode

Enable safe mode with maximum security restrictions. Syntax:
Options:
  • --level <level> - Safe mode level (basic, strict, paranoid)
  • --whitelist <files> - Allowed files/directories
  • --readonly - Read-only mode
Safe Mode Restrictions:
  • No file modifications without approval
  • No network access
  • Limited tool access
  • All operations require approval
  • Restricted system access
Examples:
Safe Mode Levels: Basic:
  • File modifications require approval
  • Network access blocked
  • System commands restricted
Strict:
  • All operations require approval
  • No file system modifications
  • No external tool access
Paranoid:
  • Read-only access only
  • No AI agent operations
  • Manual approval for everything

/clear-approvals

Clear pending approvals and reset approval state. Syntax:
Options:
  • --all - Clear all pending approvals
  • --type <type> - Clear specific approval types
  • --older-than <time> - Clear approvals older than specified time
Examples:
Approval Types:
  • file - File system operations
  • network - Network requests
  • system - System commands
  • agent - Agent operations
  • tool - Tool executions

Approval System

Approval Workflow

The approval system provides fine-grained control over AI agent operations: Automatic Approvals:
  • Safe read operations
  • Whitelisted files
  • Approved tools
  • Low-risk operations
Manual Approvals Required:
  • File modifications
  • Network requests
  • System commands
  • Sensitive operations
  • High-risk tools

Approval Configuration

Configure Approval Policies:
Approval Levels: Permissive:
  • Most operations auto-approved
  • Manual approval for destructive operations
  • Network access allowed
Balanced:
  • File modifications require approval
  • Network requests require approval
  • System commands restricted
Strict:
  • All operations require approval
  • Detailed operation descriptions
  • Risk assessment provided
Paranoid:
  • Everything requires approval
  • Multiple confirmation steps
  • Detailed audit logging

Interactive Approval

When an operation requires approval, you’ll see:

Security Policies

Policy Management

Predefined Policies: Development Policy:
  • Balanced security and productivity
  • File modifications allowed with approval
  • Network access for package management
  • Standard tool access
Production Policy:
  • High security restrictions
  • All modifications require approval
  • Limited network access
  • Restricted tool access
Audit Policy:
  • Maximum security
  • All operations logged
  • Multiple approvals required
  • Read-only by default

Custom Policies

Create Custom Policy:
Policy Configuration Options:
  • files - File access rules
  • network - Network access rules
  • tools - Tool access rules
  • agents - Agent permission rules
  • system - System command rules

File Protection

Protected Files

Certain files are automatically protected and require approval: System Files:
  • package.json
  • package-lock.json
  • .env files
  • Configuration files
  • Build scripts
Security Files:
  • SSH keys
  • Certificates
  • API keys
  • Secrets
Critical Project Files:
  • Main entry points
  • Database schemas
  • Deployment configs

File Protection Configuration

Configure Protected Files:
Protection Levels: Basic:
  • System files protected
  • Approval required for modifications
Standard:
  • System and configuration files protected
  • Backup created before modifications
Strict:
  • All important files protected
  • Multiple approvals required
  • Automatic versioning

Network Security

Network Access Control

Configure Network Policies:
Network Request Approval: When network access is restricted, requests require approval:

API Key Management

Secure API Key Handling:

Tool Security

Tool Access Control

Configure Tool Permissions:
Tool Risk Levels: Safe Tools:
  • File reading
  • Directory listing
  • Search operations
  • Information display
Medium Risk Tools:
  • File writing
  • File editing
  • Package installation
  • Git operations
High Risk Tools:
  • System commands
  • Network requests
  • File deletion
  • Process management

Tool Execution Monitoring

Monitor Tool Usage:

Security Auditing

Security Scans

Run Security Audits:
Audit Report Sections:
  • File system permissions
  • Network configuration
  • Tool access controls
  • API key security
  • Agent permissions
  • Policy compliance

Vulnerability Assessment

Assess Security Vulnerabilities:

Security Monitoring

Real-time Security Monitoring:

Integration Examples

Development Workflow Security

Production Deployment Security

Security Review Workflow

Troubleshooting

Common Security Issues

Approval System Not Working:
Dev Mode Issues:
File Protection Issues:

Debug Commands

Best Practices

Security Configuration

  • Start with strict policies and relax as needed
  • Regularly audit security settings
  • Use dev mode sparingly and temporarily
  • Monitor security events continuously
  • Keep security policies updated

Approval Management

  • Review approval requests carefully
  • Don’t auto-approve without understanding
  • Use approval policies to reduce manual work
  • Set appropriate approval timeouts
  • Document approval decisions

File Protection

  • Protect all sensitive files
  • Use version control for important changes
  • Regular backup of critical files
  • Monitor file access patterns
  • Implement proper access controls

Network Security

  • Whitelist only necessary domains
  • Monitor network requests
  • Use HTTPS whenever possible
  • Rotate API keys regularly
  • Audit network access logs

Development Security

  • Use secure development practices
  • Regular security training
  • Implement security reviews
  • Use automated security tools
  • Follow security guidelines