Slashi

Do anything in VS Code. Just type /

One keyboard-first popup for your files, settings, extensions, Git, terminal, project scripts and AI, plus the commands you build yourself.

Install

Slashi needs VS Code 1.93 or newer. On first launch, a short onboarding sets up the shortcut, your providers and AI.

What you get

Press Cmd / on macOS or Ctrl / on Windows and Linux, then type.

• One list for everything. About 180 VS Code commands with slash names, every extension command and setting, your files, open tabs, symbols, problems, Git branches and themes.
• Commands for your project. Slashi reads your manifests and offers /test, /dev, /prisma-migrate or /compose-up for npm, pnpm, yarn, bun, Next.js, Vite, Vitest, Jest, ESLint, Prettier, Prisma, Playwright, Docker, Make, Python, Rust, Go, .NET, Java, Terraform and more.
• Files from the keyboard. /new, /mkdir, /rename, /move, /dup, /delete (to the trash), copy paths, reveal.
• AI where you work. /ask, /explain, /fix, /edit, /tests, /review and /commit-msg, with GitHub Copilot, Claude Code, Codex, Claude, OpenAI, Ollama or any OpenAI-compatible server. Slashi works fine without AI too.
• Plain English. /do make the font bigger and turn on word wrap becomes a plan of real actions, which you see before it runs.
• Your own commands. Build them with a wizard, share them with your team in the repo, or install action packs from the marketplace.
• Every theme. Light, dark, high contrast and custom themes, with Phosphor icons.

30-second tour

Type / plus a scope and a space to search one area only:

/f files · /p project · /npm scripts · /set settings · /ext extensions · /git · /term · /ai · /do · /tx text · /tab open tabs · /@ symbols · /err problems · /theme · /web · /my your commands · /market

In Markdown, plain text and the Git commit box, typing / at the start of a line suggests slash commands inline.

Files and folders, with Shift Enter for actions	Your project’s scripts and tools, detected automatically
Toggle or edit any setting in place	Streaming AI answers with Apply, Insert and Copy

Providers

Everything in the list comes from a provider. You can turn off a whole provider, or single features inside one: for example, keep Marketplace search but hide installed extensions. Use the Studio (/studio), the picker (/providers) or settings.

Other extensions can add providers of their own (for example /jira). They show up in Studio with the extension's name and turn off the same way.

AI

With slashi.ai.provider set to auto (the default), Slashi uses the first of these it finds:

1. VS Code language models: GitHub Copilot, or any extension that provides chat models. Nothing to set up.
2. Claude: /ai-key → Anthropic. Uses the official SDK; the default model is claude-opus-5-5, and slashi.ai.anthropicEffort sets the effort level.
3. OpenAI: /ai-key → OpenAI.
4. Claude Code or Codex CLI: no key needed. Slashi reuses your sign-in from the Claude Code extension (or claude on your PATH) or the codex CLI.
5. Ollama: local and free, found at http://localhost:11434.
6. Any OpenAI-compatible server (LM Studio, Groq, OpenRouter, Together, vLLM): set slashi.ai.provider to openaiCompatible and set slashi.ai.baseUrl.

Switch models with /models, and test the connection in Studio → AI & Models. Standing instructions go in slashi.ai.customInstructions.

Make it yours

1. The wizard

/new-command asks for a name and steps, then saves the command to your settings or to the team file. No JSON needed.

2. Settings or a team file

Add commands to slashi.customCommands (user settings), or to .vscode/slashi.json to share them with everyone on the repo. The bundled JSON schema gives you autocomplete and validation.

// .vscode/slashi.json
{
  "$schema": "https://raw.githubusercontent.com/meness/slashi/main/schemas/slashi.schema.json",
  "commands": [
    {
      "name": "ship",
      "title": "Ship It",
      "icon": "rocket-launch",
      "args": "commit message",
      "steps": [
        { "command": "workbench.action.files.saveAll" },
        { "slash": "/test" },
        { "terminal": "git add -A && git commit -m ${q:args} && git push" },
        { "notify": "Shipped 🚀" }
      ]
    }
  ]
}

Variables: ${args}, ${selection}, ${file}, ${fileBasename}, ${fileBasenameNoExtension}, ${fileDirname}, ${fileExtname}, ${relativeFile}, ${workspaceFolder}, ${lineNumber}, ${language}, ${date}, ${time}, ${datetime}, ${uuid}, ${clipboard}, ${env:NAME}, ${config:setting.key}, ${input:var}. Add a default with ${args:3000}. Prefix with q: for shell-safe quoting, e.g. ${q:selection}.

Team files and packs ask first. When a team or pack command would run terminal, VS Code or slash commands, change settings or open links, Slashi shows those steps and asks. Always Allow skips the question until the steps change. In them, ${env:NAME}, ${config:…} and ${clipboard} expand only in insert and notify steps, so secrets stay in the editor. In untrusted workspaces, workspace-defined commands are ignored.

3. The action marketplace

/market lists action packs: Git Power Moves, AI Writing Tools, Focus & Present, Web Dev Toolkit, Handy Inserts and more. Packs built by Slashi carry a verified seal, and every download is checked against its registry listing before it installs. Before you install a pack, Slashi shows every step in it and marks the ones that can run commands. /export-pack turns your commands into a pack.

Keyboard shortcuts

To keep VS Code’s default comment shortcut, turn off slashi.shortcut.useSlashKey. Slashi then opens with Cmd Shift ; (macOS) or Ctrl Shift /. You can rebind everything in Keyboard Shortcuts (/shortcuts), separately per OS, and give any slash command its own key:

// keybindings.json
{ "key": "cmd+alt+u", "command": "slashi.run",  "args": "/upper" },
{ "key": "cmd+alt+g", "command": "slashi.open", "args": "/git " },
{ "key": "cmd+alt+t", "command": "slashi.run",  "args": "/run npm test" }

Scoped entry points such as slashi.openFiles, slashi.openGit, slashi.openProject, slashi.openAI and slashi.doWithAI can be bound too. Every result’s actions menu also has Assign a keyboard shortcut….

Settings

The AI backend, model, URL, effort, custom instructions, plan confirmation, web search engines and registry settings are machine-scoped: only your user settings can change them, never a repository’s workspace settings. Search @ext:meness.slashi in Settings for the rest.

Privacy & security

• No telemetry. Slashi collects nothing.
• API keys live only in VS Code Secret Storage. A repository can’t change your AI backend, its URL, your instructions or your confirmation setting, so it can’t send your key or code to another server.
• AI requests go only to the backend you chose. Do-with-AI plans can use only real commands and settings. With slashi.ai.confirmBeforeRun off, a plan still asks before any step that can reach a shell: terminal commands, project scripts, custom commands, and settings that change what runs or what is trusted (Slashi, terminal, task, tool path, workspace trust, proxy and agent auto-approve settings).
• Action packs are fetched only over HTTPS, previewed step by step before installing, and checked against their registry listing. Only packs built by Slashi carry the verified seal.
• Webviews use a strict nonce-based Content Security Policy and load only bundled files. Raw HTML in model output is escaped, never rendered.
• Untrusted workspaces: workspace-defined commands are ignored. Team commands (in .vscode/slashi.json or the workspace's slashi.customCommands) and packs ask before running anything that can reach a shell.

See SECURITY.md to report a vulnerability.

Performance

The popup ranks local results itself, so typing doesn't wait on the extension host. Only big catalogues, such as workspace files, are ranked in the host. The index is lowercased up front, a subsequence check skips non-matches early, and highlights are computed only for visible rows. esbuild bundles the extension, and the Anthropic SDK loads only when you first use Claude.

npm run bench on an Apple M2 Pro:

Extend Slashi

For extension authors, teams and pack publishers. The full guide is docs/BUILDING_ACTIONS.md.

• Publish a pack: add it to marketplace/packs in a pull request, or host a private registry for your team and add it to slashi.marketplace.registries.
• Add commands from your extension with registerCommand:

const slashi = await vscode.extensions.getExtension('meness.slashi')?.activate();
slashi?.registerCommand({
  extensionId: 'acme.deploy',
  name: 'deploy',
  title: 'Deploy to Staging',
  icon: 'rocket-launch',
  args: 'service',
  run: (service) => deploy(service),
});

• Add a whole provider with registerProvider (Slashi 0.5.0+): your own results under your own scope, such as /jira listing your tickets. See Providers.

Contributing

Bug reports, ideas, action packs and pull requests are welcome. You need Node 20+ and VS Code 1.93+:

git clone https://github.com/meness/slashi && cd slashi
npm ci
npm run check       # what CI runs: typecheck, lint, format, unit and smoke tests, pack validation

Press F5 (Run Slashi) to start an Extension Development Host with your build. CONTRIBUTING.md has the project layout, every script, the testing guide and how releases work.

Support Slashi

Slashi is free and open source. If it saves you time, you can support its development with a crypto donation (ETH, Polygon, BTC or SOL). The addresses are in DONATE.md. Stars, reviews and bug reports help a lot too.

Inside VS Code, Studio → Help & Support (/help-center) collects the docs, troubleshooting, feedback links and /support. When you report a bug, run /diagnostics and paste the result. It copies versions and setup only, never keys, file names or code.

License

MIT © meness and Slashi contributors. Icons by Phosphor Icons (MIT). See THIRD_PARTY_NOTICES.md.