THE LOCAL DEVELOPMENT ORCHESTRATOR

More building.
Less tab juggling.

Your services, logs, and local stack. Together in one terminal. Keep everything in view with devctl — from the first process to the last request.

Get started Explore on GitHub

Open source. Local first. Your workflow.

ONE TERMINAL. THE WHOLE PICTURE.

devctl 0.6.0demo-platformminimal3/6 runningADC missing

dashboardserviceslogsproxy/ command

services

3/6479 errors

selnamestate

[ ]obilling-consoleSTOPPED

[ ]✓identityHEALTHY

[ ]✓invoices-apiHEALTHY

›[ ]oinvoices-workerSTOPPED

[ ]opostgresSTOPPED

[ ]✓telemetryHEALTHY

logs · all · 17343–17542 of 17542

view 17343–17542 · at latestpgup/pgdn move · g latest

14:50:15invoices-apiINFOhealthhealth HEALTHY 200

14:50:16telemetryWARNstdoutGET /invoices/{id} -> 401

14:50:17telemetryWARNstdoutPOST /invoices -> 429

14:50:17telemetryWARNstdoutrate limit exceeded for client

14:50:17identityINFOstdoutINFO identity 127.0.0.1 "GET /health HTTP/1.1" 200 -

14:50:17identityINFOhealthhealth HEALTHY 200

14:50:18identityINFOstdoutINFO identity heartbeat active_sessions=0

14:50:18telemetryINFOstdoutGET /invoices/{id} -> 200

14:50:19telemetryINFOstdoutPOST /invoices -> 200

14:50:19telemetryDEBUGstdoutqueue depth sample

14:50:19invoices-apiINFOstdoutINFO invoices-api 127.0.0.1 "GET /health HTTP/1.1" 200

14:50:20invoices-apiINFOstdoutINFO invoices-api heartbeat jobs=372 queued=372

14:50:21telemetryINFOstdoutGET /invoices -> 200

dashboardLIVEProfile minimal/ command space select * all – none

Your running stack, in one view.

Services and their combined logs, side by side. Here the minimal profile has identity, invoices-api, and telemetry healthy.

Less switching. More context.TUI / CLI / MCPOne shared session

01 / WORK YOUR WAY

One stack. Your kind of control.

Stay hands-on, script the routine,
or let your agent take the next step.

FOR YOUR FLOW

A home for your stack.

Start services, follow logs, and check health in a keyboard-first terminal interface.

Explore the TUI FOR THE REPEATABLE

Make it a command.

Bring the same controls to scripts and CI. Run tasks, inspect config, and keep moving.

Meet the CLI FOR YOUR AGENT

Give AI the context.

Connect your agent over MCP to inspect and operate the same local session. Enabled when you choose.

Connect with MCP

02 / FIND YOUR FOCUS

The right services.
For the task at hand.

Group services into named profiles.
Start the part of your stack you need.

Explore profiles

DEMO PLATFORM / EXAMPLE PROFILE

devctl start --profile minimal

The profile shown in the demo above: identity, the invoices API, and telemetry.

minimal

current profile · 3 services

identityinvoices-apitelemetry

Your repo, your names. Profiles are defined in your config.

03 / FROM REPO TO RUNNING

Small setup.
Clear head.

Start with Node.js. The npm package includes its own Bun runtime. Google Cloud is optional.

Installation guide

INSTALL ONCE. USE IN ANY REPO.

npm install --global @amr-m-abdelgawad/devctl

Then, from the repo you want to run:

01
devctl setup
Describe your services in a single config.
02
devctl doctor
See what’s missing before you start.
03
devctl
Open your dashboard. Press enter to start a profile.

04 / THOUGHTFUL BY DEFAULT

Your machine.
Your ground rules.

One supervisor keeps processes, containers, the proxy, and logs in sync across every control surface.

See how it fits together

Configuration, not custom code.

Define services, profiles, health gates, and hooks in YAML.

Authentication, handled locally.

An auth-aware proxy injects Google / IAP tokens. Tokens stay out of logs.

Diagnostics without surprises.

Doctor reports missing tools and setup issues. It never auto-enables anything.

05 / TAKE A LOOK AROUND

Meet your practice stack.

A console, an API, identity, and a worker. Explore the included demo platform before configuring your own repo.

Explore the demo

06 / A FEW GOOD QUESTIONS

Before you
press enter.

A little context for your first session.

Do I need Docker or Google Cloud?

Neither is required for local host processes. Use Docker or Podman when your configuration includes containers. Google Cloud tools are optional and only needed for the Google authentication features you choose to use. See installation requirements ↗

Do I have to change my application code?

Describe how your services run in .devctl/config.yaml: their commands, working directories, environment, and health checks. devctl works with that configuration. Explore configuration ↗

Can I use the CLI and TUI together?

Yes. The TUI, CLI, and MCP connect to the same per-repo supervisor. Start a profile from the CLI and attach to its session with devctl attach. See how sessions work ↗

Does my agent get access automatically?

No. MCP is off by default. When enabled, it listens on the local loopback interface. You choose when to connect your agent and can disable individual tools. Read the MCP guide ↗

Can I try it without a global install?

Yes. Run npx @amr-m-abdelgawad/devctl@latest from your repo. Node.js is required; the npm package includes its own Bun runtime. Follow the quick start ↗

LESS FRICTION. MORE FORWARD.

Get your stack together.

Start your first session

Free and open source · MIT licensed

More building.Less tab juggling.