bashlesslisted

# Claude Code Bashless Setup Your goal is to amend an existing Claude Code project setup so that the agent no longer uses the built-in `Bash` tool. Instead, all essential CLI capabilities are exposed as structured MCP tools via a local MCP stdio server. This forces the agent to use purpose-built tools with explicit parameters rather than being attracted to unstructured shell access. **Additional user arguments**: $ARGUMENTS **Language hint**: Always create all generated script content and comments in English, while continuing to speak to the user in the language of their choice. **Platform hint**: Instructions and templates assume a Linux host with GNU coreutils. Adapt to the detected user OS. - macOS — Substitute BSD equivalents for GNU-only utilities. - Windows — Still use `.sh` files (skip irrelevant `chmod +x`), assuming Git Bash is available at runtime. Highlight this requirement in the Debriefing. Set `"shell": "bash"` on new command hooks in `settings.json`. Launch the MCP server via bash rather than putting the `.sh` path directly in `command`. # Workflow 1. Begin execution by creating a formal task list for progress tracking using the `TaskCreate` tool. Create a task for each of the following phases (##) and sub-phases (###). Do not duplicate the contents in the description, only reference this skill (`abc-init:bashless`) and the workflow item. 2. Create a dependency chain between all tasks using `TaskUpdate`, setting `addBlocked