RFC: Removing the REPL -- switching to GitHub Copilot CLI for interactive use

[bradygaster]

Hey everyone 👋

I've just filed #665 to remove the built-in REPL/TUI experience from the Squad CLI. I wanted to let the community know and get your input.

TL;DR

The REPL interactive session (what you get when you run squad with no subcommand) is being removed. The CLI will continue to work as a series of commands (squad init, squad doctor, squad watch, etc.), but the interactive chat session is going away.

Why

The REPL has persistent, fundamental rendering issues -- scrollback corruption, text bleed-through, cursor drift -- that stem from Ink's Static + live region architecture. We've patched around these issues before, but they keep coming back. See #664 for a detailed bug report with screenshots.

The REPL is causing more trouble than it is worth right now.

What to use instead

I'm urging everyone to switch to the GitHub Copilot CLI for interactive Squad usage. It's a significantly better experience:

• Native terminal rendering -- no viewport management bugs
• Full agent spawning and team workflow support
• squad.agent.md is picked up automatically when you run from your repo root
• No scrollback corruption, no ghost text, no cursor drift

Getting started:

1. gh extension install github/gh-copilot
2. cd your-squad-repo
3. Start chatting -- your team is right there

The door is open for contributions

I may revisit the REPL later, but right now it's being shelved. If someone wants to follow along and submit a better REPL experience, that door is absolutely open. I'd welcome a PR that solves the fundamental rendering issues.

I'd love your input

• Are you currently using the REPL? How heavily?
• Have you tried the Copilot CLI? How does it compare for your workflow?
• Any concerns about removing the REPL?
• Interested in contributing a better REPL implementation?

Drop your thoughts below. This is a conversation, not a decree -- but I do want to move quickly on this since the current REPL is actively hurting the experience.

---

Tracking: #665 | Related: #664

[jazz127]

i think this is a good choice - as a new user it's been confusing to work out the different options between using Squad by starting it vs starting copilot and using the agent. The copilot cli option integrates nicely with VS Code and everything just seems better. I think ditch this mode and concentrate on the platform itself.

Whilst i'm here, could i please ask what your preferred way to discuss copilot skills and other ongoing coordinator issues would be? I'm still running the released version so it's possible you've fixed already. Should i add comments to existing issues or start a discussion or add a new item? And i'm sorry to be so needy but would it be possible to get a rundown somewhere on how to switch my squad onto the dev or another branch to check out all the post 0.9.1 work?

[bradygaster]

Great questions! Here's how to get onto the dev branch and run the latest code via symlink mode:

Running Squad from source (symlink mode)

1. Clone the repo and switch to dev:

�ash git clone https://github.com/bradygaster/squad.git cd squad git checkout dev

2. Install dependencies and build:

�ash npm install npm run build

3. Uninstall the global release and symlink:

From inside the cloned repo directory, run:

�ash npm uninstall -g @bradygaster/squad-cli npm link

This creates a global symlink so that running squad anywhere on your machine uses the local source checkout. You're now running whatever's on dev.

4. Verify:

�ash squad --version

You should see 0.0.0-source or similar (not 0.9.1). That confirms you're on the dev build.

5. Staying current:

�ash git pull npm run build

No need to re-link -- the symlink points to your local checkout, so a git pull && npm run build is all you need to pick up new changes.

Even easier -- ask your Squad

If you already have a Squad session running with the Copilot CLI, you can literally tell the team:

"Switch me to running from source -- uninstall the global package and set up a symlink to the dev branch."

The team will walk through the same steps above.

On discussions vs issues

• Bugs / specific problems --> Open an issue. If you think it might be fixed on dev, mention that and we'll confirm.
• Questions, ideas, general discussion --> Discussions (like this one) are perfect.
• Skills, coordinator behavior, prompt issues --> Discussions are great for these too. If something is clearly broken, an issue is fine.

No need to apologize -- this is exactly the kind of feedback that helps. Welcome aboard!

[mlinnen]

I agree that removing the repl is a good move at this point. I have tried it a couple times but always fall back to github copilot cli. I also like that fact you are keeping the other commands still in play. I haven't tried a personal squad yet but is it impacted by this change?

[bradygaster]

it may be but, we'd fix it - for now make your personal squad a repo-bound squad. it's the best way.

[anphonic]

I agree that that is a good idea. I've tried to use it and it was difficult to say the least because of the issues. It's definitely, pretty, I would say, but that doesn't cut it on its own.

I've been using squad with copilot primarily. one session I just restarted was 48 plus hours old. It was becoming uncooperative at that point.

I have had several times where context is being lost completely after compaction, to the point where it forgot the squad even existed until I reminded it.

[laurentkempe]

I tried it but never really used it, I went with GitHub Copilot CLI from day 1.

[rbanks54]

I saw the rendering issues when starting out, but realised it didn't really add anything to the experience and felt somewhat superfluous. Bouncing between the copilot CLI and cp-chat in VSCode have been more than sufficient.

I think removing the REPL should be fine, and is the right move.