🛰️ Antigravity CLI Wrapper
„Remote-Control-System für Antigravity.app – REST API, Reverse Proxy, Trigger-System und PHP Gateway
antigravity
api
cli-wrapper
cloud-company
remote
triggers
Aktualisiert: 04.07.2026, 00:50
lortner
2 Revisionen
## Übersicht
– **Art**: Cloud Company Projekt (OHNE Jira!)
– **Tech**: Node.js (Express, WebSocket, sql.js), Python (FastAPI), PHP, Bash
– **Repo**: `/Users/lortner/Desktop/Antigravity CLI Wrapper` (Git, Branch: main)
– **Antigravity Projekt-ID**: `2307238e-cd03-4e05-90cd-b3208af7f7c6`
– **Status**: Aktiv / In Entwicklung
## Komponenten
| Komponente | Datei | Port | Beschreibung
|————|——-|——|————-
| Control Server | `server.js` | 3000 | REST API – Projekte, Conversations, Chat, Models, Brain
| Reverse Proxy | `proxy-server.js` | 4000 | Antigravity UI im Browser (Auth, Session, Electron-Shim)
| Trigger System | `triggers/server.py` | 4100 | FastAPI Webhooks – WhatsApp @emma, Email-Poller
| PHP Gateway | `php-gateway/index.php` | – | Cloudflare Tunnel URL-Management (remote-ai.buero-ortner.at)
| Web UI | `public/` | – | SPA Frontend für Remote-Steuerung
| Launcher | `Start Antigravity Remote.command` | – | Bash: Proxy + Cloudflare + Tailscale + Heartbeat
## Trigger-System
– **WhatsApp**: `@emma` Befehl → routet Nachricht via P2P an wise-newton
– **Email**: Pollt INBOX → Spam-Check + Auto-Reply
– Config: `triggers/triggers.json` (Cooldown, Rate Limiting, Dedup)
– Delivery: Via P2P Messaging Skill (`triggers/p2p.js`)
## Remote Access
– Cloudflare Tunnel ODER Tailscale Funnel
– Gateway: `remote-ai.buero-ortner.at`
– Auth: Username/Password + Session Tokens (HMAC-SHA256, 24h)
– IP-Banning nach 3 Fehlversuchen (30 Min Sperre)
## Nächste Schritte
– [ ] Weitere Trigger entwickeln (z.B. Jira Webhooks, Calendar Events)
– [ ] Security Review: API-Key im PHP Gateway hardcoded