rtk-ai/rtk

feat: add transparent hook support for Mistral Vibe (BeforeTool)

Open

#800 opened on Mar 24, 2026

View on GitHub
 (4 comments) (3 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clieffort-mediumenhancementhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Context

rtk init --agent vibe is already implemented and installs:

  • ~/.vibe/prompts/rtk.md — system prompt instructing Vibe to use rtk commands
  • Patches ~/.vibe/config.toml — sets system_prompt_id = "rtk" and adds rtk to bash allowlist

Problem

Vibe currently has no hook mechanism to intercept bash commands before execution (unlike Claude Code's PreToolUse and Gemini's BeforeTool). This means RTK integration relies on the model following the system prompt — which is less reliable than a real hook.

We opened a feature request on the Vibe repo to add this: mistralai/mistral-vibe#531

Current State (prompt-only approach)

What Status
rtk init --agent vibe ✅ Implemented
System prompt (~/.vibe/prompts/rtk.md) ✅ Installed
Config patch (system_prompt_id, allowlist) ✅ Patched
Transparent hook (BeforeTool) ❌ Blocked on mistralai/mistral-vibe#531

Plan

Once mistralai/mistral-vibe#531 is implemented:

  1. Add ~/.vibe/hooks/rtk-hook-vibe.sh (rewrite bash commands to rtk)
  2. Update run_vibe_mode() to also install the hook and patch [hooks] section in config.toml
  3. Same pattern as the existing Gemini hook (hooks/rtk-hook-gemini.sh)

References

Contributor guide

Research direction
Implement the transparent hook script and update run vibe mode to install the hook and patch config.toml once mistralai/mistral vibe#531 is resolved.
Tech stack
rust
Domain
clideveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60