Overview
The Exec capability lets CORE run shell commands on your machine. This is powerful but requires careful configuration - you control exactly which commands are allowed through allow/deny patterns.Security Model
Commands are validated against configurable patterns before execution:- Deny patterns are checked first - if a command matches any deny pattern, it’s blocked
- Allow patterns are checked next - if configured, commands must match at least one
- If no allow patterns are configured, all non-denied commands are allowed
Configuration
Configure exec patterns through the CLI:Pattern Format
Patterns use the formatBash(<glob>):
Example Configuration
Gateway Tool
exec_command
Execute a shell command:| Parameter | Required | Description |
|---|---|---|
command | Yes | The command to execute |
dir | No | Working directory (defaults to ~/.corebrain) |
timeout | No | Timeout in milliseconds (default: 30000) |
Response
Use Cases
Git operations: CORE checks branch status, creates commits, pushes changes:Recommended Patterns
Development Workflow
Read-Only Access
Always Deny
Notes
- Commands run with your user permissions
- Output is captured and returned (stdout and stderr)
- Long-running commands should use the timeout parameter
- Commands that require user input will hang - avoid interactive commands
- Working directory defaults to
~/.corebrainif not specified
