Local Development
SkillCloud & infraGet the Opik local development environment running without digging through setup docs. Once added, your AI can set up, start, stop, and troubleshoot the local environment, including Docker and local testing, using ready-made scripts and commands.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the skill, then ask your AI to set up or start the Opik local dev environment. It will use the included scripts and commands to get things running and sort out issues along the way.
Then ask your AI: use the Local Development skill
What your AI can do with it
- Set up the Opik local development environment
- Start and stop the local dev environment
- Work with Docker as part of local development
- Run local tests
- Troubleshoot problems in the local dev environment
- Use ready-made scripts and commands for common setup tasks
What this skill tells your AI
The instructions your AI receives, as published by comet-ml/opik in .agents/skills/local-dev/SKILL.md and read by ahel’s review.
Quick Start
./scripts/dev-runner.sh --restart # First time / full rebuild
./scripts/dev-runner.sh --start # Daily start (no rebuild)
./scripts/dev-runner.sh --stop # Stop everything
./scripts/dev-runner.sh --verify # Check status
Modes
| Mode | Command | Frontend | Use When |
|---|---|---|---|
| Standard | --restart | localhost:5174 | Frontend work, full-stack |
| BE-only | --be-only-restart | localhost:5173 | Backend-focused, faster rebuilds |
| Platform (EM) | PLATFORM_ENABLED=true ./scripts/dev-runner.sh --restart | localhost:9100 | Opik-team only: run Opik connected to the Comet Platform |
Platform (EM) mode — Opik-team only
PLATFORM_ENABLED=true runs the Comet EM/Platform stack (comet-backend +
comet-react, auto-detected sibling checkouts) alongside Opik behind a
single-origin nginx proxy, with Opik in comet mode authenticating/resolving
workspaces via comet-backend. Off by default — Standard/BE-only dev is
unaffected. comet-backend builds under a detected JDK 17/21; Opik still uses JDK 25.
PLATFORM_ENABLED=true ./scripts/dev-runner.sh --restart # then also --start/--stop/--verify
# Integrated UI: http://localhost:9100 (comet-react / Platform)
# http://localhost:9100/opik (Opik, comet mode)
Env vars (COMET_BACKEND_PATH, COMET_REACT_PATH, PLATFORM_JAVA_HOME, PLATFORM_*_PORT)
and --platform-build are documented in ./scripts/dev-runner.sh --help.
URLs
- Frontend: localhost:5174 (standard) / localhost:5173 (BE-only)
- Backend API: localhost:8080
- Health: http://localhost:8080/health-check?name=all
Build Commands
./scripts/dev-runner.sh --build-be # Backend only
./scripts/dev-runner.sh --build-fe # Frontend only
./scripts/dev-runner.sh --lint-be # Spotless
./scripts/dev-runner.sh --lint-fe # ESLint
./scripts/dev-runner.sh --migrate # DB migrations
Logs
tail -f /tmp/opik-backend.log # Backend
tail -f /tmp/opik-frontend.log # Frontend (standard)
docker logs -f opik-frontend-1 # Frontend (BE-only)
SDK Config
export OPIK_URL_OVERRIDE='http://localhost:8080'
export OPIK_WORKSPACE='default'
Troubleshooting
Won't start:
./scripts/dev-runner.sh --verify
lsof -i :8080 # Port conflict?
./scripts/dev-runner.sh --stop && ./scripts/dev-runner.sh --restart
Build fails:
cd apps/opik-backend && mvn clean install -DskipTests
cd apps/opik-frontend && rm -rf node_modules && npm install
Database issues:
./scripts/dev-runner.sh --stop
./opik.sh --clean # WARNING: deletes data
./scripts/dev-runner.sh --restart
Signals
- GitHub stars
- 22k
- Forks
- 2k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
local-dev- Source
- github.com/comet-ml/opik