InstantRepo be local setup helper. Give it Git repo URL or folder. It clone or read repo, detect stack, check local tools, find env needs, scan for risky files, then make setup plan.
It have three faces:
- Wails desktop app for Windows.
- Go CLI for quick analyze and step run.
- HTTP API for tool use.
Caution
InstantRepo can run commands from repos. Treat unknown repos as unsafe. Read plan and safety notes before approve run.
- Clone GitHub, GitLab, or other Git URL into chosen folder.
- Analyze local repo folder.
- Detect Node.js, Python, and Go projects.
- Detect local tools like
git,node,bun,npm,pnpm,python,go, anddocker. - Read
README.mdfor install, run, env, and service hints. - Detect
.envtemplates and needed secret values. - Draft or update grouped local
.envtargets with safe defaults, while keeping existing values. - Store approved service credentials through the operating system credential store for reuse in Env Drafts.
- Detect Docker Compose services like Postgres, MongoDB, Redis, and MySQL.
- Flag scripts, installers, and binaries before run.
- Classify setup steps as
required,recommended,optional,manual, oruncertain. - Execute one approved step at a time.
.env setup is core product work. Current app can draft or update grouped local env files with safe defaults, topology-aware local URLs and ports, generated local secrets, and vault-backed service credential references while keeping existing values.
Current Env Draft foundation includes:
- App Topology first: detect frontend, backend, workers, databases, caches, and providers before guessing URLs or ports.
- Env Default Catalog: classify dev defaults, generated local secrets, service credentials, and provider config through app-shipped rules.
- Multi-target Save All: handle root, client, server, and weird local
.env*files in one view. - User Env Vault backend: store approved service credentials in the OS credential store and keep only metadata, approvals, fingerprints, and use records in the Local App Database.
- Deepened Env Draft internals: target inference and save policy now live behind smaller behavior-tested modules.
Remaining roadmap:
- Env Vault Manager: dedicated UI for saved credentials, approvals, usage, reveal, action-needed state, and removal.
- Env Pattern Contribution: opt-in value-free env-name/context reports for future catalog patches.
- AI Env Review: bounded review of low-confidence non-secret defaults through validated Env Patches, not raw secrets or full repo files.
See CONTEXT.md and docs/adr/0002-use-catalog-driven-env-drafts.md for the product rules.
cmd/instantrepo Go CLI and API entrypoint
cmd/instantrepo-wails Wails desktop app backend
cmd/instantrepo-wails/frontend
React + Vite UI, built with Bun
internal/analyzer Repo, README, runtime, env, and service detection
internal/service Planning, execution, env writing, Env Vault, repo clone flow
internal/api HTTP endpoints
internal/domain Shared response and plan types
internal/store SQLite local metadata, setup sessions, Env Vault metadata
test Manual MVP test plan and repo matrix
- Go
1.26.2 - Bun
1.3.3or newer - Wails CLI for desktop dev and build
- Git
Install frontend deps:
cd cmd/instantrepo-wails/frontend
bun installRun dev app:
cd cmd/instantrepo-wails
wails devBuild Windows app:
cd cmd/instantrepo-wails
wails build -cleanOutput app:
cmd/instantrepo-wails/build/bin/InstantRepo.exe
Analyze repo URL:
go run ./cmd/instantrepo -repo https://github.com/user/repoAnalyze local path:
go run ./cmd/instantrepo -path C:\path\to\repoRun one plan step:
go run ./cmd/instantrepo -path C:\path\to\repo -step install-node-deps -approvePrepare .env:
go run ./cmd/instantrepo -path C:\path\to\repo -step create-env-file -approveStart server:
go run ./cmd/instantrepo -serve :8080Analyze:
curl -X POST http://localhost:8080/analyze ^
-H "Content-Type: application/json" ^
-d "{\"repoUrl\":\"https://github.com/user/repo\"}"Run step:
curl -X POST http://localhost:8080/execute ^
-H "Content-Type: application/json" ^
-d "{\"localPath\":\"C:\\path\\to\\repo\",\"stepId\":\"install-node-deps\",\"approveRisky\":true}"Run Go tests:
go test ./...Build frontend:
cd cmd/instantrepo-wails/frontend
bun run buildRun frontend behavior tests:
cd cmd/instantrepo-wails/frontend
bun testManual MVP test plan live in test/TEST_PLAN.md. Repo tracking sheet live in test/repo-matrix.csv.
InstantRepo trust stronger evidence first:
- Lockfiles and config.
- Manifests and runtime files.
- Env templates and Docker Compose files.
README.mdas support.- Guessing.
README commands can help, but do not beat manifest-backed commands.
Env Draft foundation is tracked in GitHub Issues:
- #15 PRD: Catalog-driven Env Drafts and Vault-backed Credentials is the parent track.
- #16 Env Draft model + safe Save All is done.
- #17 Env target inference is done.
- #18 Env Default Catalog is done.
- #19 App Topology + allocator is done.
- #20 Structured Env UI is done.
- #21 User Env Vault backend has backend foundation in master and should be verified before moving to UI work.
- #22 Env Vault Manager is next UI work after #21 is accepted.
- #23 Env Pattern Contribution follows the vault manager unless maintainer reprioritizes telemetry earlier.
- #24 AI Env Review + Env Patch should follow deterministic and vault foundations.
Architecture cleanup also landed after #20:
- #25 Deepen setup architecture after Env Draft foundation
- #26 Deepen setup safety scan with ignored generated folders
- #27 Deepen Env Draft foundation interfaces
- Stream live logs while step runs.
- Improve version match logic.
- Build Env Draft foundation from the active roadmap.
- Add more manifests, package managers, and topology detectors.
- Package desktop app for Windows and later macOS.
- Add optional reputation scan for risky files.