
What happened
GitHub has introduced slash commands in the GitHub Copilot app—text shortcuts that appear when you type / in the chat composer. Commands include /plan (to break down tasks before coding), /spar (to challenge your approach), /autopilot (to automate implementation steps), /rubber-duck (to get a second opinion from a different model), /create-canvas (to turn conversations into interactive interfaces), and /orchestrate (to coordinate work across multiple repositories).
Why it matters
Slash commands let developers move faster and stay focused by replacing manual navigation with quick text shortcuts. The app-specific commands differ from the CLI version because the desktop app provides a visual interface for managing project context automatically—so commands focus on workflows (like navigating sessions and managing projects) rather than terminal-level tasks like setting directories.
What to watch
The /plan and /autopilot commands appear to form a core workflow—plan first, then automate implementation. The /rubber-duck command uses a different model to independently review work, which may help surface blind spots. GitHub's docs contain additional examples and details on creating canvases and using orchestration for multi-repository changes.
Summaries like this, in your inbox every morning.
The GitHub Copilot app's slash command system reflects a shift in how AI coding assistants integrate into developer workflows. The article makes clear that the app's commands differ fundamentally from the CLI version because the environments are different: the CLI commands manage terminal-level tasks (directories, working directory, terminal access), while the app provides a visual interface that handles project context automatically. This design choice suggests GitHub is optimizing slash commands for the strengths of each interface—terminal-first for the CLI, workflow-first for the desktop app.
The command set reveals a deliberate progression through common development activities. Developers begin with /plan to break down a task, then use /spar to stress-test the approach before committing, then move to /autopilot to automate implementation. The /rubber-duck command is positioned as a quality gate—a way to catch blind spots before pushing code. Finally, /orchestrate handles the multi-repository coordination that larger features often require. This sequence suggests the commands are meant to support a complete feature lifecycle, not just isolated tasks.
The mention that /clear and /model commands work in both CLI and app versions indicates GitHub is building a consistent Copilot vocabulary across platforms where it makes sense, while allowing context-specific commands to flourish where they add the most value.
For example, today's edition would include:
AI-summarized, only the topics you pick: one digest a day via Email, LINE, or Slack.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
NVIDIA announced the NVIDIA Open Agent Safety Platform, an open software platform and reference design to secu…

NVIDIA announced its NVIDIA Open Agent Safety Platform, combining OpenShell open-source software for secure ag…

Kalkine Media reports that Home Depot (NYSE:HD) is introducing an AI assistant for its retail operations

Nvidia unveiled a security platform designed to stop AI agents from going rogue

AMD said Monday it agreed to acquire World Labs, Fei-Fei Li's San Francisco AI lab, for about $8.2 billion in…

Baird said agentic AI will drive Micron to new heights, per a CNBC report
