@devinjameson@kentcdodds itβs very common with openai
somehow gpt models love to accept vague types add fallbacks and litter the code with type guards
@kentcdodds@devinjameson more often than not the agent chose to accept way too broad of a type instead of fixing it at the boundary as high as possible and dragged this garbage through the entire call stack
@kentcdodds@devinjameson this exact function is a great indicator that something went wrong with the boundaries though and thereβs most likely a chain of bad types drilled through your system
@mitsuhiko gpt models are quite eager to start blasting python after the edit tool fail with ambiguous input
for me it rarely tries to re-read the file and construct a unique replacement string
@LukeParkerDev it's twice as hard to ship this to web apps because a lot of sub-packages assume nodejs environment and the whole bundling thing is brittle