M0X Docs
M0X Docs

Get Started

Quickstart GuideCore ConceptsAI ModelsPricing Plans

Core Features

Feature OverviewThe CoderX AgentOperating ModesReviewTerminal IntegrationBrowserSecurity

Customization

Lifecycle HooksContext ManagementRules & InstructionsCommandsSkills & Custom ToolsSub-Agents & Parallel OrchestrationSemantic Search@ Mentions

MCP

Model Context Protocol (MCP)MCP FeaturesMCP Tab

Tools

Cloud FeaturesCLIInline Edit (Ctrl+K)BugbotShared TranscriptsSlack IntegrationLinear IntegrationGitHub IntegrationGit SupportGitLab IntegrationDeep Links

Settings

ConfigurationIgnore FilesExtensionsKeyboard ShortcutsShell Commands

Advanced

Parallel AgentsBring Your Own Key (BYOK)Language SupportMigrations

Account

Account ManagementBilling & SubscriptionsUpdate AccessTeamsEnterprise

Guides

CookbookAgent WorkflowsWeb DevelopmentData ScienceLarge Codebases & MonoreposMermaid DiagramsBugbot Rules

Support

TroubleshootingCommon IssuesRequest IDTroubleshooting GuideDownload
Documentation

Terminal Integration

Execute shell commands, run diagnostics, and auto-fix compilation errors.

The integrated terminal in CoderX is not just a standard shell—it is fully context-aware and connected to the AI agent. The agent can construct command-line requests, check build tracebacks, install required dependencies, and suggest quick patches for compiler failures.


Interactive Command Execution

When you request terminal actions via chat (e.g. "set up this react app" or "start the docker container"), CoderX executes the request:

Command Generation

The agent detects your environment (operating system, shell type, project packages) and designs the correct shell syntax.

User Approval Gate

By default, generated terminal commands are presented in a confirmation card. You can review the command, edit it, or click Approve to run it.

Output Capture

The command runs in the integrated terminal panel, and its output is parsed in real time by the agent.


Auto-Diagnostic: "Fix with AI"

When a compilation, lint check, or unit test script fails in the terminal, CoderX flags the trace:

[!TIP] Click the Fix with AI button next to a failed terminal output. CoderX will read the traceback, search your workspace for the offending file, and recommend a code correction instantly.

Command Failure Resolution Lifecycle

  1. Exit Code Detection: The shell triggers a failure hook on non-zero exit codes.
  2. Traceback Parsing: The agent extracts files and line references from error headers (e.g. Node.js stack traces, Rust compile panics, Python index errors).
  3. File Retraction: CoderX opens the file context automatically and applies the fix via an inline diff proposal.

Security Boundaries & Sandboxing

Because executing shell commands is a high-risk operation, CoderX enforces strict security guidelines:

  • Network Protections: Command queries that fetch packages or download scripts (like curl, wget, npm install) are flagged for confirmation, giving you an opportunity to review urls.
  • Path Boundaries: The agent is restricted to executing commands within the bounds of your active workspace directory (Cwd), preventing accidental commands in your root folders or system files.

Review

AI-powered code review.

Browser

Built-in web browser for documentation.

On this page

Interactive Command ExecutionCommand GenerationUser Approval GateOutput CaptureAuto-Diagnostic: "Fix with AI"Command Failure Resolution LifecycleSecurity Boundaries & Sandboxing