u/Technical-Relation-9

Image 1 — It's gotta spend those tokens! Can't be sitting idle without permissions!
Image 2 — It's gotta spend those tokens! Can't be sitting idle without permissions!
🔥 Hot ▲ 67 r/ClaudeAI

It's gotta spend those tokens! Can't be sitting idle without permissions!

Claude is not allowed to write outside the workspace.

But it wanted to.

So Claude wrote a python script and executed it via bash to modify the file essentially hacking the permissions

u/Technical-Relation-9 — 5 hours ago
Image 1 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 2 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 3 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 4 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 5 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 6 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600

Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600

I know Kotlin and Swift so this isn't purely vibecoding, but AI was a genuine co-pilot throughout the entire build. Wanted to share because the technical challenge here was unusual.

The app is called Bounce Connect. It bridges Android and Mac wirelessly over local WiFi. SMS from your laptop, WhatsApp calls on your Mac screen, file transfers at 120MB/s, clipboard sync, notification mirroring. No cloud, no middleman, fully AES-256 encrypted.

The hardest part of this kind of project is that you're building two completely separate apps on two completely different platforms simultaneously. The Android companion app in Kotlin and the Mac app in Swift. Neither app is testable without the other working. If the WebSocket connection drops you don't know if it's the Android side or the Mac side. If a feature breaks you have to debug across two codebases, two operating systems, two completely different APIs at the same time.

AI helped enormously here. Not for writing code blindly but for thinking through the architecture, handling edge cases in the connection layer, implementing AES-256-GCM encryption correctly, and getting mDNS device discovery working reliably across both platforms. The back and forth for debugging cross platform issues saved me weeks.

Shipped 3 weeks ago. Crossed $600 in revenue at $10.99 one time purchase with no subscription.

bounceconnect.app

Image 1 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 2 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 3 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 4 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 5 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600
Image 6 — Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600

Built an Android + Mac sync app in Kotlin and Swift with AI assistance - shipped 3 weeks ago and already crossed $600

I know Kotlin and Swift so this isn't purely vibecoding, but AI was a genuine co-pilot throughout the entire build. Wanted to share because the technical challenge here was unusual.

The app is called Bounce Connect. It bridges Android and Mac wirelessly over local WiFi. SMS from your laptop, WhatsApp calls on your Mac screen, file transfers at 120MB/s, clipboard sync, notification mirroring. No cloud, no middleman, fully AES-256 encrypted.

The hardest part of this kind of project is that you're building two completely separate apps on two completely different platforms simultaneously. The Android companion app in Kotlin and the Mac app in Swift. Neither app is testable without the other working. If the WebSocket connection drops you don't know if it's the Android side or the Mac side. If a feature breaks you have to debug across two codebases, two operating systems, two completely different applications at the same time.

AI helped enormously here. Not for writing code blindly but for thinking through the architecture, handling edge cases in the connection layer, implementing AES-256-GCM encryption correctly, and getting mDNS device discovery working reliably across both platforms. The back and forth for debugging cross platform issues saved me weeks.

Shipped 3 weeks ago. Crossed $600 in revenue at $10.99 one time purchase with no subscription.

Happy to go deep on the technical side, the cross platform architecture, or how I used AI throughout if anyone is curious.

bounceconnect.app