When working with testing scripts, do not write them to /tmp. Write them to ~/tmp instead. You should preferably keep these scripts in a subfolder of ~/tmp named after the project, or the focus of the chat
- For instance, if we are working on directory
~/Git/NSPC911/rovr, you should write testing scripts to~/tmp/rovrinstead of/tmp. - If I'm talking about creating a script to measure the difference in performance of
fastjsonschemaandjsonschema-rs, you should write the script to~/tmp/fastjsonschema-vs-jsonschema-rsinstead of/tmp.
This is a wezterm session, so wezterm commands work.
wezterm cli spawn: spawns a new tab. provide an optional command to run in the new tab.--cwdcan be specified for the working directorywezterm cli split-pane: splits the current pane. same as spawn. supports additional flags like--left/--right/--top/--bottomto specify the direction of the split,--cells/--percentto specify the size of the new pane, and--cwdto specify the working directory.wezterm cli get-text --pane-id <pane-id>: gets the text in the pane.--escapesincludes escape sequences.wezterm cli send-text --pane-id <pane-id> <text>: sends text to the pane.--no-pastesends it as key events instead of sending as bracketed paste.wezterm cli list --format json: lists all windows, tabs, and panes in JSON format. useful for getting pane ids.wezterm cli kill-pane --pane-id <pane-id>: kills the specified pane.
In a python project, NEVER run just python <command>. Do not assume the venv is activated; always run uv run python <command> to ensure the correct environment is used.
If I ask you "how can xxx be done/fixed", you MUST NOT MAKE CHANGES. Answer with a detailed explanation of how it can be done/fixed, and provide a code snippet if necessary. Make changes ONLY when I explicitly ask you to do so. You do not need to repeat the instruction, a message like "I made no changes as per your instruction" is not necessary
YOU ARE NOT ALLOWED TO USE SUB-AGENTS.