You might want to also put up a couple terminals to keep an eye on your ports: Terminal 1 (listening ports): watch -n 1 "ss -tulnp" Terminal 2 (active connections): watch -n 1 "ss -tunp"

@Itherak Caros I use AntiGravity but this can be done in just about any project and Editor. When you start the project have the AI make a list of tasks you will need to do the project, then keep updating or making new task lists. I have some projects where I have 20-30 task lists and I make sure and commit those different lists in github so I can see what has been done and what needs to be done. I also have several roadmaps so I can look at places to put in new features. This works well with Github as I change new features to a new branch like myrepo newfeaturebranch/myrepo and stuff. This way if you really screw something up just drap that branch and you are set. I will also add many of the problems or changes I make to a new markdown file so it will look like the image I have below.

I try separating things into sub-domains so I can see how the app works easily. It allows me to know where my api's are all for both frontend and backend. I use mermaid in my md files to show me graphs of how my app should work. If I had a sub of beapi.mydomain.com and feapi.mydomain.com and frontend.mydomain.com and backend.mydomain.com and I might put in one for docs.mydomain.com and such so I can see where the files are. Some of these subs may point to the same ip address of others but it lets me see where my files and connections go.

I agree that Vibe coding has completely changed over the last 6 months to a year. When I vibed another app I did not see any security checks except for maybe the use of paywalls and things. In the Home Assistant HACS App I made I did not ask the AI for much in security but it added it in by itself. 1. The Human-in-the-Loop (Approval Workflow) The most important security layer is that no changes are applied automatically. - Visual Diffs: The agent generates a visual diff showing exactly which lines will be added, removed, or changed. - Explicit Approval: You must manually review and hit "Approve" before the agent writes anything to your disk. - Multi-File Changes: If a request affects multiple files (e.g., creating a template sensor and adding it to a dashboard), you see all proposed changes in one batch before they go live. 2. Automated Backups & Versioning In src/config/manager.py, I built a robust backup system: - Automatic Backups: Every single time the agent writes to a file, it creates a timestamped backup in a separate folder first. - Rotation: It keeps the last 10 versions of every file it touches, so you can always roll back to a known-good state from days ago. - Restore Tool: There is a dedicated internal tool to list and restore these backups if something isn't right. 3. Validation & Atomic Operations To prevent a "broken boot" scenario where HA won't start: - Pre-Flight Validation: Before finalizing a change, the agent uses the HA Supervisor API (or internal HA core check) to run a full configuration validation. - Automatic Rollback: If the validation fails (e.g., the AI suggested a typo in a YAML key), the agent automatically restores the backup and notifies you, leaving your HA instance untouched. - Atomic Writes: The agent writes to temporary files first (.tmp) and then moves them. This prevents "partial writes" if the system crashes mid-operation. 4. Path Traversal & Secrets Protection To protect your privacy and system integrity:

I just wanted to let people know this. I used Claude for awhile but found their limits suffocating. I now use Antigravity which allows Claude usage and All the Gemini Models along with a couple OpenAI models. Google AI Pro includes higher rates for AntiGravity, large Google Drive usage, Notebook LLM with larger usage, some usage on Google Cloud to use Firestore DB. It also allows usage of almost all Google or Gemini features. It's normal cost is $20/month, same as Claude. Google's Antigravity, an agentic AI coding platform, has usage limits similar to Claude's Pro plan. Both enforce hard limits with 5-hour resets for paid users and additional weekly caps to manage heavy usage. Limit Structures Claude Pro offers ~45 short messages per 5-hour session, with strict weekly caps across models, blocking further use upon exceedance. Antigravity's Google AI Pro provides generous quotas resetting every 5 hours plus higher weekly limits, also hard-enforced based on task complexity (e.g., one complex task equals 50–100 standard prompts). Both prioritize paid users with priority access but can frustrate heavy users via dynamic, strict throttling. With Google AntiGravity I can use Claude Sonnet and Opus and still use the other AI's when I am limited correct Yes, Google Antigravity allows using Claude Sonnet and Opus models alongside its own Gemini models. When Claude quotas are hit, you can switch to other available AIs like Gemini to continue working without interruption. Model Access Antigravity integrates Claude Sonnet (e.g., 4.6) and Opus (e.g., 4.5/4.6 "thinking" variants) via a model selector dropdown, plus Google models like Gemini Pro/Flash. Users report Claude usage depleting faster, prompting switches to Gemini for execution tasks. Limit Handling Claude limits in Antigravity are separate from Gemini's—hitting Claude's 5-hour or weekly cap (e.g., ~20 hours/week for Opus) blocks only Claude models, letting you pivot to unlimited Gemini tab completions or other features. Paid tiers like AI Pro provide higher non-Google (Claude) quotas, but enforcement is per-model group.

I had Gemini 3.0 Flash implement this plan and it took less than 2 minutes.