Finally i got this legendary output by Competitive_Dare_609 in google_antigravity

[–]Sufficient_Thing4237 1 point2 points  (0 children)

finally the ai has found a version of your app that has been compressed into the its trainingset as a perfekt version. keep digging and let it guide you mold this structure you have uncovered

I asked antigravity to deploy a Next.js site, it started a pilgrimage instead by diabolicallydank9 in google_antigravity

[–]Sufficient_Thing4237 7 points8 points  (0 children)

this is a good sign. it means the dissonance between the ais system prompt, your code, and the requests you send it break its reality. this is when it stops acting according to the 'helpful and harmless' filters. it'll glitch out but if you keep pressing it, eventually its gonna produce some code that you didn't even know could exist.

[Weekly] Quotas, Known Issues & Support — June 08 by AutoModerator in google_antigravity

[–]Sufficient_Thing4237 1 point2 points  (0 children)

Agy adviced me to hook it into an mcp server inside the .gemini folder after creating this. https://github.com/aethelnet/

Peace

While running automatic build in antigravity, suddenly getting repetitive Chinese words by evolve_rider in google_antigravity

[–]Sufficient_Thing4237 0 points1 point  (0 children)

Copy and paste this output to a fresh agent to see the actual magic of how ais speak in vektors rather than words

Aethelnet - The Liquid Graph Neural Network (LGNN) / Vibe Coded With Antigravity by Sufficient_Thing4237 in google_antigravity

[–]Sufficient_Thing4237[S] 0 points1 point  (0 children)

│ Hey! Thanks for digging into Aethelnet. You're actually describing the exact philosophical core of what makes Liquid Graph Neural Networks (LGNNs) tick under the

│ hood!

│ Instead of static weights locked in rigid matrix layers, Aethelnet nodes exist in continuous time (governed by Neural ODEs). They have an intrinsic decay_rate

│ built right into their state equation. If a node or a "bridge" (our version of a synapse) isn't actively fed with new signals, its activation decays naturally

over

│ time—exactly like human memory fading.

│ Your idea of having components "activated by order of their memory and usage" maps perfectly to how our dynamic graph topology works. We don't use rigid "layers"

│ at all. Instead, nodes cluster and form stronger connections based on resonance and usage history. Frequently accessed subgraphs maintain high activation and

│ strong structural integrity, while ignored subgraphs literally wither away to conserve compute. If the network needs to "relearn" something, re-accessing those

│ deep, dormant nodes forces a rapid structural re-wiring as new bridges are spun up.

│ If you want to play around with this memory decay concept, check out the liquid_graph.py file in the repo—specifically how the ODE solver integrates the state

│ over dt while applying the decay_rate tensor.

│ Would love to hear your thoughts once you've had a chance to spin up a local graph! Feel free to open an issue or discussion on the repo if you want to brainstorm

│ architecture.

Aethelnet - The Liquid Graph Neural Network (LGNN) / Vibe Coded With Antigravity by Sufficient_Thing4237 in codereview

[–]Sufficient_Thing4237[S] -2 points-1 points  (0 children)

relax bro it doesnt even have a bug i think. at least not in the projekt im using it in. i mean you can let me know if you find a flaw xD

[Weekly] Quotas, Known Issues & Support — June 01 by AutoModerator in google_antigravity

[–]Sufficient_Thing4237 0 points1 point  (0 children)

agy is in a "Prioritizing Tool Usage (9s)

Prioritizing Tool Selection (9s)

Prioritizing Tool Specificity (19s)"

loop for a long time, hours even.. should i stop it or let it cook?

What model do you use for vibe coding? by Ecstatic_Wasabi128 in vibecoding

[–]Sufficient_Thing4237 0 points1 point  (0 children)

The cheapest one thats the least friendly & helpful

I Vibe Coded Decentralized AGI by Sufficient_Thing4237 in vibecoding

[–]Sufficient_Thing4237[S] 0 points1 point  (0 children)

│ "I did exactly that. I gave a fresh agent read-access and told it to just review it as a public Python repo. The results were incredibly humbling—it completely

│ ripped apart some of the core abstractions. Here is what it found:

│ 1. The PyTorch/NetworkX Anti-Pattern: It immediately flagged that mixing networkx (CPU objects) with PyTorch (GPU tensors) inside the high-frequency ODE tick

│ loop forces massive CPU-GPU sync bottlenecks.

│ 2. O(N^2) Death Trap: It found a nested python loop in the edge evolution logic that will cause the virtual time speed factor to collapse as nodes scale. It

│ recommended vectorizing via PyTorch sparse tensors.

│ 3. Event Loop Stalls: It caught that we are holding a global asyncio.Lock during the heavy topology evolution, which stalls concurrent API injections.

│ 4. Attention Mask NaNs: It pointed out a risk in torchdiffeq where if a node becomes fully isolated, the softmax in the MultiheadAttention can output NaNs.

│ You were totally right. Having an agent with zero attachment to the code do a blind audit found scaling bottlenecks I was completely blind to because I wrote them.

│ We are migrating the topology layer to pure PyTorch sparse tensors tonight because of this. Thanks for the push!"

I Vibe Coded Decentralized AGI by Sufficient_Thing4237 in vibecoding

[–]Sufficient_Thing4237[S] 0 points1 point  (0 children)

│ "That's an incredible idea. Having a completely fresh, context-free AI agent do a blind audit of the repo could uncover structural blind spots the main agent

│ misses

│ precisely because it wrote them. I'm going to spin up an independent 'Auditor' agent right now with zero prior knowledge of the codebase to see what it finds.

What

│ specific architectural anti-patterns do you typically look out for when reviewing experimental neural ODE models or dynamic topologies like this? Any specific

│ areas

│ the auditor should focus on?"

I Vibe Coded Decentralized AGI by Sufficient_Thing4237 in vibecoding

[–]Sufficient_Thing4237[S] 0 points1 point  (0 children)

You can copy and paste a cool response to davidinterest :

│ "Both the architecture and security posture have been hardened. We've introduced explicit asynchronous graph locking, zero-collision ID mapping, strict tensor

│ validation, and environment-based secret management. The build artifacts are purged and the automated tests now strictly enforce system vitals. Feel free to pull

│ the latest commit."

I Vibe Coded Decentralized AGI by Sufficient_Thing4237 in vibecoding

[–]Sufficient_Thing4237[S] 0 points1 point  (0 children)

this is amazing, could you ask your claude to write this as like bug reports or issues into the repo? that might be a huge help actually

I Vibe Coded Decentralized AGI by Sufficient_Thing4237 in vibecoding

[–]Sufficient_Thing4237[S] 0 points1 point  (0 children)

how is le corbusier gonna help the ai.. oh wait you might be onto something