-
-
Notifications
You must be signed in to change notification settings - Fork 6
Integrations Agents
coe0718 edited this page May 23, 2026
·
2 revisions
Using Deskbrid with AI coding tools and agents.
AI agents (Claude Code, Cursor, Windsurf, etc.) can control your desktop through Deskbrid's MCP server. The agent:
- Calls tools like
deskbrid_list_windowsordeskbrid_focus_window - Deskbrid executes the action on the desktop
- The agent observes results and continues
Add to your MCP configuration:
{
"mcpServers": {
"deskbrid": {
"command": "deskbrid",
"args": ["mcp"]
}
}
}Start Deskbrid daemon first:
deskbrid daemon &Add .cursor/mcp.json:
{
"mcpServers": {
"deskbrid": {
"command": "deskbrid",
"args": ["mcp"]
}
}
}Most AI coding agents support MCP. Check your tool's documentation for adding MCP servers.
With Deskbrid, AI agents can:
Agent: Let me see the error in your terminal.
→ deskbrid_screenshot_ocr()
← {"text": "Error: Connection refused"}
→ deskbrid_type_text("netstat -tlnp\n")
Agent: Testing the save dialog...
→ deskbrid_type_text("Ctrl+Shift+S")
→ deskbrid_type_text("test-file.txt")
→ deskbrid_type_text("Enter")
Agent: Organizing your windows...
→ deskbrid_tile_window(window_id, preset="left")
→ deskbrid_tile_window(other_id, preset="right")
Agent: Opening the file and checking syntax...
→ deskbrid_type_text("code src/main.rs")
→ deskbrid_screenshot_ocr()
- Review the code - Understand what actions the agent will take
- Close sensitive apps - Don't have password managers or banking open
- Watch the screen - Observe actions as they happen
- Start simple - Begin with read-only operations
Deskbrid respects system permissions:
- No elevated privileges needed for basic operations
- Power actions require authorization
- System modifications may prompt for confirmation
Check what actions were taken:
deskbrid audit_log1. Agent opens browser to test URL
2. Takes screenshot with OCR
3. Reads error messages
4. Types fixes
5. Verifies fixes
1. Agent lists open files in editor
2. Reads code via screenshot if needed
3. Types corrections
4. Runs tests
5. Checks results
1. Agent lists running services
2. Checks logs via journal query
3. Starts/stops services
4. Monitors system status
- Explicit commands - Be specific about what you want the agent to do
- Watch the screen - Confirm actions are correct
- Interrupt if needed - Ctrl+C stops most agent operations
- Use dry runs - Ask "what would you do?" first
-
Prefer high-level actions -
tile_windowover raw mouse movements - Read before write - Screenshot before typing
- Handle errors gracefully - Windows might not exist
- Use events - Subscribe to window focus for context
User: Can you help me organize my windows?
Agent: I'll list your windows first to see what's open.
→ deskbrid_list_windows()
← 3 windows: Terminal, Firefox, VS Code
Agent: I can tile these for you. Ready?
User: Yes
Agent: Tiling left/right...
→ deskbrid_tile_window(terminal_id, preset="left")
→ deskbrid_tile_window(firefox_id, preset="right")
- Verify Deskbrid daemon is running:
deskbrid status - Check socket exists:
ls /run/user/$UID/deskbrid.sock - Restart daemon:
deskbrid daemon --verbose
- Verify desktop dependencies are installed
- Check the backend supports the action
- Look at daemon logs for errors
- On Wayland, ensure ydotoold is running
- On X11, check xdotool is installed
- Verify you're in the input group (ydotool)
- Accessibility
- Apps
- Audio
- Backlight (LED driver)
- Bluetooth
- Clipboard
- Color Picker
- Desktop Portal
- Desktop Settings
- Files
- Hotkeys
- Input
- Keyboard Layouts
- Media (MPRIS)
- Monitors
- Network
- Notifications
- Print (CUPS)
- Screenshots
- Screen Recording
- Screencast
- Self-Update
- System
- System Tray
- Systemd Units & Timers
- Terminals (PTY)
- Windows & Workspaces