Working with squad CLI while work is being done #681
Replies: 1 comment 1 reply
|
@johnwildes, I'm another new user so if there are any corrections from squad experts I'm all for it. Squad CLI is just an interface into Github Copilot service in the cloud. Exactly like Copilot CLI is. Squad CLI is being removed i believe so probably best for you to make the switch to copilot-cli only model anyway. Of course don't forget to change to Squad's agent that gets installed for you. Don't be like me and start working then half an hour later realise you're missing you're whole team. If you launch two "interfaces", if I understand correctly, you'll get two different sessions on the Github Copilot in the cloud. These wouldn't share the live/working state so I would expect your agents to be idle. What would eventually happen is some sort of merge once agents finish and Scribe writes it to the .squad files that handle cross session state. In my experience, you can totally and are expected to talk to the coordinator whilst work is in process although chats when it gets busy spawning/processing the results etc would be delayed. This wouldn't stop the work. Your squad agents/staff actually become subagents that the coordinator launches. If you want to check what's going on for a subagent, you can use /tasks command and then enter into the details of a particular task (subagent/squad staff member). Hopefully there's a level of sense being made in there. Let us know if it doesn't help or clears things up 💯 |
Uh oh!
There was an error while loading. Please reload this page.
Hey Everyone
New to using squad here, within Copilot CLI if I give tasks to agents and their working does prompting in the Copilot CLI stop the working progress? I opened a new tab in my terminal, and launched the squad CLI to see what the status was, so as to not interrupt the work in progress, and it said all my agents were idle. Should I be able to run squad cli commands from the copilot command box to get a status?
thanks
All reactions