GitHub - rajibbora1965/WhatsAppCoding: Cosde base for wWhatsApp Coding · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
rajibbora1965
WhatsAppCoding
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>1 Commit<br>1 Commit
antigravity-proxy
antigravity-proxy
.gitignore
.gitignore
README.md
README.md
sync-token.sh
sync-token.sh
View all files
Repository files navigation
WhatsApp Coding: Coexistence Proxy & Mobile Agent Orchestration for AntiGravity 2.0
This repository details the high-level system architecture for WhatsApp Coding —a decentralized, mobile-first workflow designed to unbundle the traditional desktop IDE. By establishing a secure loopback and proxy chain between a local development environment, a cloud instance, and an instant messaging interface, this framework enables busy technical executives to act as a human-in-the-loop validation layer for autonomous multi-agent engineering directly from their pocket.
🏗️ Conceptual System Architecture
The ecosystem separates local workspace file manipulation from the user interface layer, dividing operations into four core components:
Nous Portal)">[ WhatsApp Mobile Client ]<br>│ (Prompts / Preview / Approvals)<br>[ GCP VM (Always-On) ] ──(24/7 OAuth Refresh)──┐<br>│ │<br>(Baileys Client) (Secure Sync)<br>│ │<br>▼ ▼<br>[ MacBook Local Environment ] Nous Portal)
1. The Pocket Interface (WhatsApp Mobile Mission Control)
Dedicated Communication Channel: The platform uses a dedicated Google Voice business line to keep mobile agent sessions entirely separated from personal messaging histories.
Anti-Spam Optimization: The messaging gateway utilizes a low-level Baileys bridge client on port 3000 that mimics a standard desktop Chrome browser to bypass automated numeric pairing blocks.
Real-Time Execution Spawning: Incoming text prompts hit a secure dashboard endpoint that triggers a background agent on the local MacBook via a child process spawn. File reading, code generation, and shell commands occur in real-time right inside the active local repository folder.
2. The Local Interceptor Proxy (antigravity-proxy)
Host-Level Loopback Routing: Because standalone developer environments like AntiGravity 2.0 restrict outbound inference to default internal models, a local Node.js proxy acts as a TLS-terminating server on ports 4000/443. It intercepts traffic bound for Google's generative language servers using a self-signed wildcard certificate.
Context Sifting & Sanitization: The proxy automatically strips out massive, repetitive inline system prompts, workspace configurations, and metadata blocks generated by the desktop client. This payload sanitization shaves off up to 4,000 tokens per message turn, drastically optimizing performance and context space.
Metadata Reconstruction: For inbound completion streams, the proxy dynamically rebuilds mock headers, including artificial safety ratings, structured index markers, and grounding metadata. This ensures the desktop application processes the tokens smoothly without throwing verification freezes.
3. The Financial Shield (Flat-Rate Gateway)
Predictable Cost Capping: To protect paid tokens from being consumed by complex multi-agent planning overhead, the proxy chains its converted OpenAI-compatible requests directly into a local Hermes Agent proxy on port 8645.
Subscription-Based Routing: The gateway automatically appends OAuth credentials to outbound request payloads. This routes heavy long-horizon reasoning blocks (like Claude Opus 4.8) directly to a predictable, flat-rate subscription catalog.
4. The 24/7 Token Sync Engine
Cloud-Primary Authentication: Because local laptops have sleep cycles that suspend background scripts, an always-on GCP VM container acts as the primary host to manage provider OAuth token refresh loops 24/7.
Decoupled Synchronization: A local macOS LaunchAgent script runs every 5 minutes on the MacBook to securely pull the updated authentication file from the cloud VM. It extracts the active...