Skip to content
Back to skills

Remote Web

ASecurity

Use when starting/stopping the Remote Web UI on port 8901.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 4, 2026
ai-agentspythongobashapi

Works with

  • api

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add openamer/openamer --skill remote-web --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Remote Web?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Remote Web
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/openamer-remote-web/badge)](https://www.skillsdirectory.com/skills/openamer-remote-web)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: remote-web
description: 'Use when starting/stopping the Remote Web UI on port 8901.'
author: OpenAmer
tags: [web, dashboard, remote, http, server, monitoring]
---

# Remote Web Platform

## Überblick

Die Remote Web Platform ist ein vollständiges Web-Dashboard für OpenAmer, erreichbar von jedem Gerät im Netzwerk.

- **Port:** 8901
- **Build:** Python stdlib only (http.server, json, threading)
- **Auth:** Bearer-Token (SHA256 geschützt)

## Endpunkte

| Pfad | Methode | Beschreibung |
|---|---|---|
| `/` | GET | HTML-Dashboard mit Chat, Status, Skills, Logs |
| `/health` | GET | Health-Check (gibt "OK" zurück) |
| `/api/status` | GET | JSON System Snapshot |
| `/api/skills` | GET | JSON Alle Skills (nach Kategorie) |
| `/api/chat` | POST | Chat-Kommunikation: `{"prompt": "..."}` |
| `/api/logs` | GET | Letzte 100 Log-Zeilen |

## Starten

```bash
# Standard (Port 8901, alle Interfaces)
python "$OPENAMER_HOME\scripts\remote-web.py"

# Nur lokal (127.0.0.1)
python remote-web.py --local

# Benutzerdefinierter Port
python remote-web.py --port=8901
```

## Auth-Token

- Standard-Token beim ersten Start: `openamer-remote-secret`
- Token-Datei: `~/.remote-web/auth.txt`
- Token in jeder Anfrage als Header: `Authorization: Bearer <token>`
- Der SHA256-Hash des Tokens wird serverseitig geprüft

## Health-Check Cron-Job

Ein Cron-Job läuft alle 5 Minuten:

```bash
openamer cron create "5m" --name "remote-web-health" --script "remote-web-health.py" --no-agent --deliver local
```

1. Ruft `http://127.0.0.1:8901/health` auf
2. Schreibt Ergebnis nach `~/.remote-web/health.json`
3. Exit-Code 0 = OK, 1 = Fehler

## Dateien

| Datei | Zweck |
|---|---|
| `scripts/remote-web.py` | HTTP-Server (Hauptdatei) |
| `scripts/remote-web-health.py` | Health-Check-Script für Cron |
| `~/.remote-web/auth.txt` | Auth-Token (SHA256) |
| `~/.remote-web/health.json` | Letzter Health-Check-Status |

## Fehlerbehebung

- **Port belegt:** `netstat -ano | findstr :8901` → PID ermitteln und killen
- **Auth-Fehler (401):** Prüfe `~/.remote-web/auth.txt` – Token muss im `Authorization: Bearer <token>` Header gesendet werden
- **Server startet nicht:** Prüfe Python 3.11+, kein psutil nötig (Fallback auf wmic)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…