Christoph Läubrich

> if one creates some file with touch or cp or mv and the target is in the workspace, we could imagine a listener that refreshes the corresponding resource. This...

> Technically, I don't think a new listener is necessary for that, the Terminal API could instead notify of a new command by sending a ProcessHandle to listener, and the...

> I suspect one can find some easyish rule to determine the case of user entering a command in prompt (ie check that the current char has a a prompt...

> The `cd ...` example is just to tell that during a LLM agent conversation, the terminal executions are stateful. The LLM will ask the terminal to run some commands,...

@jdneo I don't think it is stateless per se... e.g. my suggestion was just for the implementation of `run_in_terminal` command, so lets say I call `run_in_terminal("cd xx")` you turn it...

> No, nothing to do about the Copilot CLI. I'm talking about the very basic run_in_terminal invocations in agent mode. Too bad ;-) Just out of curiosity I started a...

@jdneo maybe it works to put the command in a `sh` script or `bat` file, then execute that? This is a bit similar to your eval (Unix) or Invoke-Expression (Windows)...

Another option would be to handle it on all different places where such streams are used, but it seems more clean to handle it more like at the roots.

One problem is that currently `RqTemp` uses `RqLive` in a way that relies on close... so one can also handle this in `BkBasic` @yegor256 any guidance on this how it...

Testcase is currently also missing. Where would be the best place to place such test that fails if no response is given?