OxideSens AI
OxideSens is OxideTerm’s built-in AI assistant that helps you work more efficiently in the terminal. It features 40+ autonomous tools, MCP server integration, RAG knowledge base, and supports both sidebar and inline chat modes.
Bring Your Own Key
Section titled “Bring Your Own Key”OxideSens follows a BYOK (Bring Your Own Key) model. You provide your own API key for any supported AI provider. Keys are securely stored in your OS keychain — never in config files.
Supported Providers
Section titled “Supported Providers”- OpenAI — GPT-5.4, GPT-5.4 mini, GPT-5.4 nano, etc.
- Anthropic — Claude Opus 4.6, Claude Sonnet 4.6, Claude Haiku 4.5, etc.
- Google — Gemini 3 Flash, Gemini 2.5 Pro, Gemini 2.5 Flash, etc.
- DeepSeek — V3.2, etc.
- Ollama — any local model (Llama, Mistral, Qwen, etc.)
- OneAPI — self-hosted API gateway
- Any
/v1/chat/completionscompatible endpoint
Models are fetched dynamically from provider APIs — new models are available automatically without app updates.
- Open Settings → AI tab
- Enable AI Capabilities
- Read and confirm the privacy statement
- Enter your API base URL (e.g.,
https://api.openai.com/v1) - Enter your API key — stored in OS keychain
Sidebar Chat
Section titled “Sidebar Chat”The sidebar chat panel provides a persistent conversational interface with full history:
- Ask questions about commands, scripts, or system administration
- Get explanations of error messages and log analysis
- Request command suggestions for specific tasks
- Multi-source context — IDE files, SFTP paths, Git status automatically available as context
- Full chat history with session persistence
Terminal Context
Section titled “Terminal Context”OxideSens captures terminal buffer from the active pane or all split panes simultaneously. It can analyze:
- Recent command output
- Error messages and stack traces
- Log files visible in the terminal
- Running process output
Context is injected into a structured prompt with environment information (local OS, remote OS if detected via SSH).
Inline Panel
Section titled “Inline Panel”Press ⌘I (macOS) or Ctrl+Shift+I (Windows/Linux) to open the inline panel — a lightweight, floating command assistant:
- VS Code-style floating panel — appears at the cursor position, 520px wide
- AI-suggested commands — inserted via bracketed paste (safe, no auto-execution)
- Output analysis — select error text, press
⌘I, ask “what went wrong?” - One-click actions: Insert (paste into terminal), Execute (run immediately), Copy, Regenerate
Inline Panel Shortcuts
Section titled “Inline Panel Shortcuts”| Key | Action |
|---|---|
Enter | Send question; with result: execute command |
Tab | Insert AI suggestion into terminal |
Esc | Close panel |
Smart Positioning
Section titled “Smart Positioning”The panel follows the terminal cursor position:
- Prefers display below the cursor
- Auto-switches to above when space is insufficient
- Horizontal auto-adjustment for screen edges
40+ Autonomous Tools
Section titled “40+ Autonomous Tools”OxideSens can autonomously invoke tools without manual triggering:
| Category | Examples |
|---|---|
| File Operations | Create, read, write, move, delete files and directories |
| Process Management | List processes, kill processes, check resource usage |
| Network Diagnostics | Check ports, DNS resolution, connectivity tests |
| TUI Interaction | Send keys to running TUI apps (vim, htop, yazi) |
| Text Processing | Search, replace, extract, transform text content |
| System Info | Disk usage, memory, uptime, OS details |
Tools are invoked through a structured function-calling interface with the AI model.
MCP Integration
Section titled “MCP Integration”Connect external Model Context Protocol servers for third-party tool integration:
- stdio transport — launch a local MCP server process
- SSE transport — connect to a remote MCP server via Server-Sent Events
- Configure MCP servers in OxideTerm settings
- MCP tools appear alongside built-in tools in the sidebar chat
This allows extending OxideSens with domain-specific capabilities — database queries, cloud infrastructure management, documentation search, and more.
RAG Knowledge Base
Section titled “RAG Knowledge Base”Import your own documents into scoped knowledge collections:
How It Works
Section titled “How It Works”- Import: Add Markdown (
.md) or plain text (.txt) files - Chunking: Markdown-aware chunking preserves heading hierarchy — sections stay semantically coherent
- Indexing: Dual index — BM25 keyword index + vector cosine similarity
- Search: Hybrid retrieval fuses both scores via Reciprocal Rank Fusion (RRF)
Collection Scoping
Section titled “Collection Scoping”- Global collections — available across all connections
- Per-connection collections — scoped to a specific SSH connection for project-specific documentation
CJK Support
Section titled “CJK Support”The tokenizer uses bigram segmentation for Chinese, Japanese, and Korean content, ensuring accurate search results without requiring a full NLP pipeline.
Use Cases
Section titled “Use Cases”- Import project documentation for context-aware code assistance
- Add runbooks for instant operational guidance
- Store internal API references for command generation
AI Agent Mode
Section titled “AI Agent Mode”OxideSens includes an Agent Mode that enables multi-round autonomous task execution — the AI plans a sequence of tool calls, executes them, observes results, and iterates until the goal is reached.
How It Works
Section titled “How It Works”- You give a high-level goal: “set up a Python virtual environment and install the requirements”
- The agent decomposes it into steps, choosing tools at each step
- After each tool call, the agent observes the result before deciding the next action
- The loop continues until the goal is complete or a blocking decision requires your input
Tool Approval Modes
Section titled “Tool Approval Modes”To maintain control over autonomous execution, OxideSens provides three approval stances:
| Mode | Behavior |
|---|---|
| Supervised | Confirm every tool call before execution |
| Balanced | Auto-approve low-risk tools (read-only); confirm writes and destructive actions |
| Autonomous | Auto-approve all tools; agent runs until completion |
Default is Balanced. Switch via the toolbar in the AI sidebar.
Per-Tool Auto-Approval
Section titled “Per-Tool Auto-Approval”For fine-grained control, you can whitelist specific tools for automatic approval while leaving others requiring confirmation. In Settings → AI → Tool Approvals, each tool can be individually toggled.
Tool Call Logging
Section titled “Tool Call Logging”Every tool call the agent makes is logged in the sidebar conversation with:
- Tool name and input parameters
- Result or error (collapsed by default, expandable)
- Elapsed time
This gives full auditability of what the agent did during a session.
Privacy & Security
Section titled “Privacy & Security”- All API keys stored in OS keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service)
- On macOS, key reads gated behind Touch ID via
LAContext— cached after first auth per session; no entitlements or code-signing required - Terminal buffer data is sent to the AI provider only when you explicitly request it (click the Context button and send a message)
- No telemetry or data collection — OxideTerm never phones home
- Local models via Ollama keep everything on your machine — zero network traffic for AI queries
- Streaming SSE for real-time responses — tokens appear as they’re generated