Autonomous IT Response Intelligence Agent

Your AI IT department. Any incident. Any machine. Minutes — not days.

ARIA is a voice-first desktop agent that investigates and fixes laptop problems locally. Describe an issue by voice or text — slow performance, popups, suspicious network activity — and ARIA scans your machine, verifies threats with Browserbase, plans fixes with Claude, and remediates approved actions. Nothing destructive runs without your approval on each action.

1. Report — Speak or type the problem (Deepgram Voice Agent).
2. Investigate — Collect processes, network, startup items, and recent files locally (psutil).
3. Verify — Check suspicious indicators via Browserbase Search + Fetch.
4. Diagnose & plan — Claude analyzes findings and builds an evidence-backed fix plan.
5. Approve — Review each kill / quarantine / block decision in the UI or by voice.
6. Remediate — Execute approved actions via native Python and Simulang.
7. Close — Spoken summary + incident saved to local history.

API keys (required):

• Anthropic — Claude orchestrator
• Deepgram — voice STT, TTS, and Voice Agent
• Browserbase — threat verification and fix research

Global tool (recommended for GUI remediation):

• Simulang @6.0.0 — OS automation for complex fixes

Platforms: macOS and Windows.

git clone https://github.com/AarabhiRK/aria.git
cd aria

pip install -r requirements.txt
npm install
npm install -g @simular-ai/simulang@6.0.0

macOS only — grant Simulang permissions once:

simulang setup

Windows — no setup command needed. If simulang run fails with a load error, unblock the native binary:

Get-ChildItem -Recurse (npm root -g) | Unblock-File

Copy the example env file and add your API keys:

cp .env.example .env

On Windows PowerShell:

Copy-Item .env.example .env

Edit .env and replace the placeholder values:

• DEEPGRAM_API_KEY
• ANTHROPIC_API_KEY
• BROWSER_BASE_API_KEY

.env is gitignored — never commit real keys.

Open two terminals from the repo root:

# Terminal 1 — FastAPI backend (port 8787)
npm run backend

# Terminal 2 — Electron desktop UI
npm run dev

The ARIA window opens automatically. The sidebar shows Systems online when the backend is reachable.

1. Click Start session on the welcome screen.
2. Type or speak a problem (e.g. "My laptop is slow" or "I keep getting popups").
3. Wait for the scan (~1 minute). Review the diagnosis and proposed fixes.
4. Approve or Skip each fix. When all are reviewed, approved fixes apply automatically.
5. Open History for past incidents or Quarantine for moved files.

Plant harmless fake problems for a repeatable demo, then clean up afterward.

# Plant a scenario (popup | miner | startup | duplicates | all)
python scripts/demo_break.py popup

# Remove all demo artifacts when done
python scripts/demo_cleanup.py

Example prompts after running a scenario:

• popup: "I keep getting suspicious popups"
• miner: "My laptop is running hot and slow"
• startup: "Something launches at startup that I don't recognize"
• duplicates: "My Downloads folder is full of duplicate files"

Verify demo fixes end-to-end:

python scripts/verify_demos.py

aria/
├── backend/          FastAPI server, orchestrator, voice agent, decisions
├── electron/           Electron main process
├── sick_machine/       Local collection (psutil) + remediation execution
├── src/                React + TypeScript desktop UI
├── scripts/            Demo break / cleanup / verify
├── tests/              Python test suite
└── docs/               Architecture diagram and API contract

npm run typecheck          # TypeScript check
python -m pytest tests/  # Backend tests (82 tests)
npm run build              # Production Electron build

Backend health check: http://localhost:8787/health

All incident data is stored locally under ~/.aria/incidents/. Nothing is synced to the cloud except API calls to Anthropic, Deepgram, and Browserbase during an active session.