About Backtrack
Backtrack is an MCP server published by SahilSaxena007 in the Developer Tools category: mCP server: Backtrack.
The repository has 1 stars and 0 forks, with the last commit 8 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/SahilSaxena007/backtrackThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Backtrack
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 7 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
Backtrack AI
Backtrack AI is an Electron desktop agent for safe file organization with natural language. It is built around a strict safety loop:
- Understand intent with Gemini.
- Generate a structured plan.
- Show a before/after preview.
- Execute only after explicit approval.
- Support deterministic undo.
Quality checks:
npm run lint(tsc --noEmit)npm run build:main(main-process TypeScript compile)
Features
- Floating agent button + detachable chat drawer.
- Dedicated preview workspace (before/after + execution controls).
- Human-in-the-loop approval before filesystem mutations.
- Undo support for completed executions.
- Folder scope onboarding and path validation.
- MCP filesystem integration with local fallback support.
Tech Stack
- Languages: TypeScript, JavaScript, HTML, CSS
- Desktop: Electron
- Frontend: React, Vite, Tailwind CSS, Zustand, Framer Motion
- AI: Google Gemini via
@google/generative-ai - Agent/tool layer: Model Context Protocol (
@modelcontextprotocol/sdk) - File services:
fs-extra
Repository Structure
src/main/: Electron main process, IPC handlers, execution/safety servicessrc/renderer/: React UI pages/components/storessrc/shared/: shared types for main/renderer contractsdist/: build output
Prerequisites
- Node.js 18+ (recommended: Node 20 LTS)
- npm 9+
- Windows is the current primary tested environment
Setup
- Install dependencies:
npm install
- Create environment file:
copy .env.example .env
- Set required env values in
.env:
GEMINI_API_KEY(required)GEMINI_MODEL(optional, default currently used by app:gemini-3-pro-preview)BASE_PATH(optional)MCP_ALLOWED_PATHS(optional)USE_LOCAL_FS=1(optional fallback mode if MCP filesystem server is unavailable)
Run
npm run dev
What to expect:
- Control panel opens.
- Click
Deploy Agent Button. - Open chat from the floating button.
- Enter a request, review preview, then approve execution if correct.
Example prompt:
Organize this folder by creating Images and Pdf folders, move image files to Images and pdf files to Pdf.
Commands
npm run dev: start Vite + Electronnpm run lint: TypeScript type-checknpm run build:main: compile Electron main processnpm run build: full production buildnpm run verify: run lint + main build
Keyboard Shortcuts
Ctrl/Cmd + K: open chat drawerCtrl/Cmd + P: open preview workspaceCtrl/Cmd + Z: undo latest organization
Troubleshooting
No files found in this folder yet:- Make sure the selected folder actually contains files.
- Re-check onboarding folder selection and active scope.
- Gemini key errors:
- Ensure
.envexists andGEMINI_API_KEYis valid.
- Ensure
- MCP filesystem issues:
- Use local fallback by setting
USE_LOCAL_FS=1in.env.
- Use local fallback by setting
- Port conflict on
8000:- Stop the process using the port, then re-run
npm run dev.
- Stop the process using the port, then re-run
Security model
- Renderer runs with
contextIsolation: trueandsandbox: true. - Filesystem operations are executed through controlled main-process handlers.
- Scope-boundary checks prevent planning/execution outside selected folder.
README fetched from the repository 7 days ago. The original is authoritative.