Add support for multiple AI coding assistants with multi-select by BrettKinny · Pull Request #20 · SquareWaveSystems/squarebox

BrettKinny · 2026-04-06T19:53:04Z

Summary

Extends the AI coding assistant setup to support selecting multiple tools simultaneously, rather than just one. Adds three new npm-based AI tools (GitHub Copilot CLI, Google Gemini CLI, OpenAI Codex CLI) alongside the existing Claude Code and OpenCode options.

Key Changes

Multi-select UI: Updated both interactive (gum) and non-interactive prompts to allow comma-separated selections or "all" option
New AI tools: Added support for GitHub Copilot CLI, Google Gemini CLI, and OpenAI Codex CLI (all npm-based)
Node.js dependency: Moved install_node() function earlier in setup to support npm-based tools; added ensure_node_for_npm() helper to install Node.js on-demand
Installation logic: Refactored AI tool installation into a loop that processes comma-separated ai_choice values
Alias mapping: Updated alias generation to map c to the first selected tool in priority order (claude → copilot → gemini → codex → opencode)
Legacy migration: Added migration path for old single-choice config values (e.g., "both" → "claude,opencode")
Documentation: Updated README and CLAUDE.md to reflect multi-select capability and new tools; added storage size estimates for new tools

Implementation Details

AI tools are stored as comma-separated values in the config file (e.g., "claude,copilot,opencode")
npm-based tools automatically trigger Node.js installation if not present
Node.js installation is persisted to SDK config to survive container rebuilds
The c alias intelligently selects the first available tool from a priority order
Both gum (graphical) and text-based selection flows support the new multi-select model

https://claude.ai/code/session_017RbipnT7DQyQGYqZRDhgRE

… tool options Convert AI coding assistant selection from single-choice (Claude Code / OpenCode / Both) to multi-select, matching the editor and SDK selection pattern. All three new tools are npm-based and auto-install Node.js if needed. Legacy config values are migrated automatically. https://claude.ai/code/session_017RbipnT7DQyQGYqZRDhgRE

Copilot

Pull request overview

Extends setup.sh’s AI coding assistant selection from a single-choice model to a multi-select model, and adds installation support for additional npm-based assistants so users can configure multiple tools in one environment.

Changes:

Updated interactive (gum) and non-interactive prompts to support selecting multiple AI tools and storing them as comma-separated config values.
Added install flow for GitHub Copilot CLI, Google Gemini CLI, and OpenAI Codex CLI (npm-based), including on-demand Node.js installation via nvm.
Updated documentation to reflect multi-select behavior, new tools, alias behavior, and size/security notes.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
`setup.sh`	Implements multi-select AI tool selection, loops tool installs, adds npm-based installers + Node-on-demand, and updates alias generation.
`README.md`	Documents new AI tool options, `c` alias behavior, disk usage estimates, and npm integrity note.
`CLAUDE.md`	Updates setup step documentation to reflect multi-tool AI assistant selection.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-06T19:58:15Z

+	done
+	[ -n "$c_target" ] && echo "alias c='$c_target'"
 } > ~/.squarebox-ai-aliases


c_target is set to the config key (e.g. copilot), but Copilot is installed/detected as github-copilot-cli (command -v github-copilot-cli). If Copilot is the first selected tool, alias c='copilot' will point to a non-existent command. Map AI keys to their actual executable names (e.g. make c point to github-copilot-cli), or install/provide a copilot wrapper executable for consistency.

@copilot can you open a github issue for this so i can explore the best fix

I wasn't able to create the issue programmatically (the token doesn't have issues: write permission), but here's the content ready to paste into a new issue:

Title: Fix: 'c' alias for GitHub Copilot CLI points to non-existent 'copilot' command

Body:

## Bug When GitHub Copilot CLI is selected as the highest-priority AI tool, `setup.sh` generates: alias c='copilot' But the executable installed by `npm install -g @githubnext/github-copilot-cli` is `github-copilot-cli`, not `copilot`. Running `c` will fail with "command not found: copilot". ## Root Cause `setup.sh` lines 305–315 use the internal config key (`copilot`) directly as the alias target, without mapping it to the real executable name. ## Fix Options 1. **Map keys to executables** – add a lookup so `copilot` → `github-copilot-cli` (e.g. a `case` statement before `echo "alias c='$c_target'"`). 2. **Install a thin `copilot` wrapper** – create `/usr/local/bin/copilot` that delegates to `github-copilot-cli "$@"`. 3. **Detect at shell startup** – generate the alias lazily with `command -v` so it resolves the right binary at runtime. ## Steps to Reproduce 1. Run `setup.sh` and choose only GitHub Copilot CLI (or rank it first). 2. Open a new shell. 3. Type `c` — it fails with "command not found: copilot".

Once the issue is open, option 1 (a case statement mapping keys to executable names) is the most straightforward fix and I'm happy to implement it.

Copilot · 2026-04-06T19:58:16Z

+		if [[ ",$sdk_current," != *",node,"* ]] && [ "$sdk_current" != "node" ]; then
+			echo "${sdk_current:+$sdk_current,}node" > "$sdk_cfg"
+		fi


ensure_node_for_npm mutates /workspace/.squarebox/sdks here, but later in the script the SDK selection flow overwrites the same file based on user input. That can drop the persisted node entry even when npm-based AI tools were selected/installed. Consider merging node into the final sdk_list when any npm-based AI tool is chosen, or defer writing until after the SDK prompt to avoid clobbering.

Copilot · 2026-04-06T19:58:16Z

 All binary tools are pinned to specific versions and verified against SHA256
 checksums at build time. Third-party install scripts (Claude Code, uv, .NET)
-manage their own binary verification.
+manage their own binary verification. npm-based AI tools (Copilot CLI, Gemini
+CLI, Codex CLI) use npm's built-in integrity verification.


The Security section still states “All binary tools are pinned to specific versions…”, but the new npm-based AI tools are installed without version pinning (e.g. npm install -g @google/gemini-cli). This makes the statement misleading. Either pin npm package versions (and document update process) or narrow the wording to distinguish pinned checksum-verified downloads from npm-installed packages.

@copilot apply changes based on this feedback

Copilot · 2026-04-06T20:37:23Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

https://api.github.com/graphql
- Triggering command: `/usr/bin/gh gh issue create --title Fix: 'c' alias for GitHub Copilot CLI points to non-existent 'copilot' command --body ## Bug

When GitHub Copilot CLI is selected as an AI tool (and is the highest-priority selection), setup.sh generates:

alias c=&#39;copilot&#39;

However, the actual executable installed by npm install -g @githubnext/github-copilot-cli is github (http block)

Triggering command: /usr/bin/gh gh auth status (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled

Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Copilot AI review requested due to automatic review settings April 6, 2026 19:53

Copilot started reviewing on behalf of BrettKinny April 6, 2026 19:54 View session

Copilot AI reviewed Apr 6, 2026

View reviewed changes

Copilot started work on behalf of BrettKinny April 6, 2026 20:35 View session

Copilot finished work on behalf of BrettKinny April 6, 2026 20:37

BrettKinny merged commit 6511b00 into main Apr 6, 2026
6 checks passed

BrettKinny deleted the claude/add-ai-cli-tools-VKOd6 branch April 6, 2026 20:41

Navigation Menu

Uh oh!

Add support for multiple AI coding assistants with multi-select - #20

Add support for multiple AI coding assistants with multi-select#20
BrettKinny merged 1 commit into
mainfrom
claude/add-ai-cli-tools-VKOd6

BrettKinny commented Apr 6, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

BrettKinny Apr 6, 2026

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

BrettKinny Apr 6, 2026

Uh oh!

Copilot AI commented Apr 6, 2026

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

BrettKinny commented Apr 6, 2026

Summary

Key Changes

Implementation Details

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

BrettKinny Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

BrettKinny Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Apr 6, 2026

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants