like it did mkdir -p to the same location it had been working in for like 10 responses in a row until i explicitly told it not to do that
Yep, I've had weirdness like that too. But what I meant was if the agent would spawn a terminal as part of a response, it would also try do things like npm run dev over and over from response to response, almost like it doesn't really keep the terminal it spawned itself in context. I'd have to test using the in-editor-but-not-in-chat terminal pane more. I've just been using a regular external shell most of the time.
Welp, as we like to say around these parts, we're still early~
Yea I think that's exactly the same problem, I'm actually about to make a post on the forums because I can't get multiple repo's to work with the agent in a single workspace
npm run devover and over from response to response, almost like it doesn't really keep the terminal it spawned itself in context. I'd have to test using the in-editor-but-not-in-chat terminal pane more. I've just been using a regular external shell most of the time.