
Vibe code full stack ideas💡at the speed of @laravelphp.
🌍
Joined September 2025
- Tweets14
- Following1
- Followers8
- Likes13
Helfer.dev retweeted
I tried so much for GPT 5.4 used in @helferdev to stop referencing /var/www to no much success.
I guess I can’t defeat the training on this one. Good thing is that there’s no issues
Helfer.dev retweeted
Very soon, @helferdev will be able to deploy to the @turingpi running in my living room. This excites me!
Helfer.dev retweeted
Tired of typing in the same paths in @helferdev so I added a basic dropdown to select the path inferred from @laravel routes.
Helfer.dev retweeted
Hacking the background task support on helfer.dev out bit by bit. 🛠️
Helfer.dev retweeted
Tried so much to not follow the Kanban style with the task UI and this is the best representation in my head. 🎨
Maybe this will change… we’ll see.
Helfer.dev retweeted
You can also attach captured mails in helfer.dev as context in the chat in case you want to follow up or make changes. 📩
Helfer.dev retweeted
Projects on helfer.dev now supports email capture which allows emails leaving your app to be captured and previewed easily with no need for an external service.
All in a single workspace in @helferdev.
📩
Helfer.dev retweeted
Helfer.dev now supports deployment to Laravel Forge.
The agent builds locally until it’s actually ready to ship.
Then it pauses and prompts the user to connect Forge, create the site and trigger a deployment.
Helfer.dev retweeted
Replying to @taylorotwell
This is basically why I choose Laravel templates for @helferdev . It’s so much straightforward for LLMs to get things working when “how” is already known.
Helfer.dev retweeted
Helfer.dev now requests env vars and secrets during the build and no longer tells you to "put STRIPE_SECRET in .env later."
It pauses the flow with a secure prompt and continues once provided.
This further closes the gap to a working app. ⚡️
Helfer.dev retweeted
First steps on getting @helferdev connected to @laravelphp Forge for deployments.







