ls **/* is wild.
How can we avoid this?
(gpt-5-mini through GitHub Copilot)
preciz
1
josevalim
Creator of Elixir
We are already doing what we can to avoid this, which is to detect when it runs something too long and tell them that it is too long. 
Unfortunately, we can’t really prevent them from doing this regardless of how much direction we provide in the prompts.
Slightly changing subject., I did not have a good experience with GPT-5-mini so far, but GPT-5 has done well. What about you?
0
preciz
For me it was good until yesterday when I felt a drop in quality. Started to make mistakes with the smallest things. I have experience with this with OpenAI, they did this a lot in the past but of course I didn’t measure this however in the past others measured it so I wouldn’t be surprised if something changed.
So in short gpt-5-mini through GitHub copilot was good for a few days but now it’s very chaotic.
1
wallyfoo
I tried it for a bit, but ended up going back to Claude when the gpt 5 models started confidently hallucinating functions it insisted were part of the Elixir core modules.
0
josevalim
Creator of Elixir
preciz
I’m having a good time now with “xAI Grok Code Fast 1” making a lot of small UI changes successfully.
However sometimes an error like the one I attached comes back and the chat stops there.
0
josevalim
Creator of Elixir
That looks like either a copilot or xai bug, as it is emitting invalid function tool calling syntax.
1
preciz
At Octoscreen we just subscribed to a teams plan for all our devs but we had some issues.
-
We should be able to change the email of the main account because that email is not changeable in the paddle account and it gets written on the invoice and it’s my personal email that tidewave.ai got through my github login.
-
We got billed twice, first we got billed with the amount that we pay without VAT and then we got billed separately with the VAT, is this intended?
1
alatriste
I’ve been testing Tidewave with GitHub Copilot and I’m really impressed. I have two comments:
- I asked it to add a new resource to an existing context with the mix phx.gen.live task, but as is often the case, this command suggests creating a new context, so the chat got stuck showing the confirmation request. I don’t know if there’s a way from Tidewave to access the console from the chat and confirm the request. I had to do it manually from a console.
- After only 5 messages, the Context Window Usage was 50% full. I understand this depends on the provider, and in the case of Copilot, it varies by model, with a maximum of 264.0k. What would be the best practices for dealing with the context limit?
2