in worst case you just install the old rule back if it fuck up, no really damage can happen.

https://developer.mozilla.org/zh-CN/docs/Web/API/Window/scre...

The words borrowed from someone else:

The react is more about view.

The vue is more about reactivity

Codex's short context and todolist system combined somehow helps here though. Because of the frequent compact. The model was forced to recheck what todo list item has not done yet and what workflow skill it has to use. I used to left it for multi hour to do a big clean up and it finished without obvious issues.

It's a huge step though.

The pyproject.toml can even handles build env for you, so you no longer need a setup.sh that installs 10 tool in specific order with specific flag to produce working environment. A single uv sync, and the job is done.

Plus the result is reproducible, so if this time uv sync work, then it also work next time.

Highly recommend if you are still on pip.

Note: Take a example that I used to install unsloth with rocm setup that based on unreleased git version dependencies and graphic card specific build flag, all of them can be handled with one command 'uv sync'. This will require a big pile of shell script if doing another way. https://github.com/unslothai/unsloth/issues/4280#issuecommen...

and windows mostly use \? and also \h,

java user single - for long argument because it don't have short one.

I doubt it is ever close to reusable.

And even allowed position of parameters (or even meaning of arguments in case of ffmpeg) are program dependent.

Some allow anywhere as long as it is started with a dash, some only allow before first input

And it's also affected by how model is trained. Gemini specifically like to read large amount of text data directly and explodes the context. But claude try to use tool for partial search or write a script to sample from a very large file. Gemini always fills the context way faster then claude when doing the same job.

But I guess in case of a bad designed mcp, there is no much model can do because the results are injected into context directly though (unless the runtime decided to redirect it to somewhere else)

You can probably let llm guess the help flag and try to parse help message. But the success rate is totally depends on model you are using.

However that don't happen unless firefox just stop developing though. New code comes with new bug, and there must be some people or some tool to find it out.

This sounds like your context is too big and getting cut off.