Vibe and Antigravity agents missing from CommandRegistrar.AGENT_CONFIGS

[mango766]

Hi there,

I noticed that the vibe (Mistral Vibe) and agy (Antigravity) agents are defined in AGENT_CONFIG in __init__.py but are missing from CommandRegistrar.AGENT_CONFIGS in extensions.py.

This means extensions can't register commands for these two agents — register_commands_for_all_agents() will never detect them even if their directories exist.

I think this might be related to #1816 and #1705.

Location: src/specify_cli/extensions.py, CommandRegistrar.AGENT_CONFIGS dictionary

Happy to submit a fix if that would be helpful!

[wlinna]

Could this explain why spec-kit does not seem to work at all with vibe? .vibe directory is created, but none of the slash commands such as /speckit.constitution) appear on vibe cli, even if I run /reload/ . Even copying the prompts to ~/.vibe/prompts appeared to do nothing.

specify version = 0.7.4
vibe --version = 2.81

[Fango2007]

Hello,

To make Spec-kit work with Mistral Vibe, you must use the new method specified by Mistral to define custom slash commands (https://github.com/mistralai/mistral-vibe#custom-slash-commands-via-skills). It is based on Skills system from now on.
(Originally, the integration between Vibe and Spec-kit happened before the introduction of this feature by Mistral).

The easiest way to plug the spec-kit commands into Mistral Vibe:
1 - Run specify and select Claude AI coding agent (specify init --here -ai claude). It will create a .claude\skills directory with the speckit* commands.
2 - Run specify a second time but with vibe as AI coding agent this time (specify init --here -ai vibe). It will create the .vibe directories.
3 - Create a skills directory under .vibe
4 - Move all the speckit directories from .claude/skils to .vibe/skills
5 - Clean up your root directory : delete .claude dir and CLAUDE.md file

If you run vibe, you should be able to trigger all the speckit commands.

I will open an issue to ask an update from the speckit team.

[mnriem]

Feel free to create a PR to address the issue

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed in 30 days if no further activity occurs.