`/every` and `/after` commands are listed in `copilot help commands` output, but not present during interactive session

[kajames1]

Describe the bug

I was looking through feedback provided by /chronicle tips and it recommended using the /after and /every commands. When I try to run either in a CLI session I get the message: ✗ Unknown command: /every. Running copilot help commands shows both in the list:

That said it doesn't show up when I use /help from within a session:

I do not run with /experimental on, but I tried just to check, and still got the same error trying to run this command.

Are these real commands and there's a bug in the CLI preventing their use; or is this an errant help/documentation artifact which isn't actually implemented that /chronicle hallucinated about?

Affected version

GitHub Copilot CLI 1.0.48.

Steps to reproduce the behavior

1. Run copilot help commands and observe that /every and /after are present in the list under Other commands.
2. Open an interactive CLI session, prompt: /every 1m ask_user what number they're thinking of and observe the error message: ✗ Unknown command: /every
3. From the interactive CLI session run /help and observe that neither /every or /after are present in the list.

Expected behavior

There's a few places things fell apart for me:

• /chronicle tips shouldn't be suggesting I use Copilot CLI features, that by all accounts don't seem to actually exist.
• copilot help commands should not list slash commands for interactive sessions that don't actually exist.
  • It should also be consistent with what's output by /help with regards to those slash commands it claims exist.

Additional context

No response

[caarlos0]

This will be fixed on the next release. It'll show as experimental.

Thank you!

[kajames1]

This will be fixed on the next release. It'll show as experimental.

Thank you!

Does that mean the feature exists now, but is currently experimental, or that it will be implemented (and experimental) in the next release? It's confusing, since I tried using CLI in experimental mode, and the commands still didn't work.