@Dimillian@awwstn Simpler way to spawn a worktree for me. Iโm on holidays and tempting back into my laptop (which is crazy cool) but I noticed new threads donโt seem to have a way to easily switch between local/worktrees
@thisismahmoud@RileyRalmuto@Railway Have to say the railway skill + cli combo is absolutely unreal for devex. Iโve got a prototype app with 3 services/db/redis/env vars stood up on railway and I think Iโve looked at the dashboard once. Codex was able to debug and fix a cors error and everything. So so good ๐
@rohanvarma Have a look at https://t.co/ASn4hcc4sI and take inspiration from their UX (Claude only for now). How they handle informing the user about skill use, subagents etc is unparalleled
@leerob@joshmatz@cursor_ai Is there anything in the works (even long term) to work across repos in the cloud? We have separate FE/API/CDK repos and it would be great to point and agent at all of them remotely to deliver a feature end to end.
@imax153@EffectTS_ I just implemented observability in a small app for work and getting effect logs into Datadog was a bit of a chore with de-trace. Had to convert them to Winston and use the Winston transport. Something native here would be awesome! Now that it is done it works like a dream!
@kitlangton @aurelienqsw 100% I'm trying to effect pill people at work. I'd rather just make them watch this. It is much better than anything I would come up with
@stephendahcrown@Prathamesh_7717@tan_stack@honojs@golang@nextjs@tannerlinsley Well next would say that wouldnโt they. The reality is any serious application would benefit from a dedicated API built with a framework that is specifically built for backend development. Use Next or React Router or Start as BFFs
@RoccoVaccone@braelyn_ai Long running processes/async background tasks/independent scaling. Theres a tonne or reasons to use a purpose built backend framework