convez.ai
Agente
DevinoSolutions

multideck-ai-agent

DevinoSolutions/multideck-ai-agent

Ver no GitHub
InicialPluginScore · de 0 a 100

Open every project in its own terminal (Claude Code / Codex / VS Code) and auto-tile them into a grid across all your monitors — DPI-correct on mixed-scale setups.

Instalação

$npx convez-ai DevinoSolutions/multideck-ai-agent

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
0
Acompanhando
0
Saúde
50%
Último commit
há 1 semana
Versão
v3.21.0
Issues abertas
13
Contribuidores
1

README

A tradução para o português deste README ainda está na fila.

multideck-ai-agent

Open every project in its own terminal — running Claude Code, Codex, or any CLI agent — and auto-tile them into a grid across all your monitors. One config file. DPI-correct on mixed-scale setups.

platform shell license

        Monitor 1  (4K @ 250%)         Monitor 2  (4K @ 250%)        Monitor 3 (1080p @ 175%)
     ┌────────────┬────────────┐    ┌────────────┬────────────┐    ┌─────────┬─────────┐
     │   api      │   web      │    │   infra    │   docs     │    │  ops    │   …     │
     │  [claude]  │  [claude]  │    │  [codex]   │  [code]    │    │ [claude]│         │
     └────────────┴────────────┘    └────────────┴────────────┘    └─────────┴─────────┘
                       columns × rows per screen · true physical pixels on every monitor

You run one command. Each project opens in its own titled, color-tabbed terminal, already cd'd into the right folder with your agent running — then every window snaps into a clean grid spanning all your screens.


Why

If you juggle a fleet of repos with terminal AI agents (Claude Code, Codex, aider, …), you waste minutes every morning opening terminals, cd-ing around, starting the agent, and dragging windows into place. multideck makes that a single double-click — and unlike manual snapping or most tilers, it gets the geometry right on monitors that run different display scales (the usual reason auto-tiling drifts or leaves gaps).

Features

  • 🗂 One window per project, titled and color-tabbed, opened directly in its folder.
  • 🤖 Any CLI agent — Claude Code and Codex out of the box; add your own in one line.
  • 🪟 VS Code support — projects can open in VS Code instead of a terminal.
  • 🧮 Configurable grid — columns × rows per screen, spanning every monitor.
  • 📐 DPI-correct — per-monitor-aware, so a 175% laptop screen next to 250% 4K monitors tiles perfectly (see How DPI works).
  • ✨ Zero-typing setup — point -Init at a folder and it scans your git repos and writes the config for you, with groups and colors filled in.
  • 🏷 Groups — tag projects and launch just one set: multideck -Group lead-gen.
  • 🧭 Interactive menu — run with no arguments for a friendly menu; no flags to memorize.
  • ♻️ Idempotent — re-running only opens what's missing; -RetileAll re-snaps everything.
  • 👀 -DryRun — preview the whole plan before anything launches.
  • 🔒 Your config stays local — multideck.config.json is git-ignored; only the example ships.

Requirements

  • Windows 10 (1703+) or 11
  • Windows Terminal (wt) — for terminal-based tools
  • Windows PowerShell 5.1 (built in) or PowerShell 7+
  • Whatever you launch: the Claude Code CLI, Codex, VS Code (code on PATH), etc.

Install

git clone https://github.com/DevinoSolutions/multideck-ai-agent.git
cd multideck-ai-agent

Option A — run from anywhere (recommended): double-click install.bat (or run .\install.ps1). It adds the folder to your user PATH and drops Desktop + Start-Menu shortcuts, so you can type multideck in any terminal or double-click an icon. Reversible any time with uninstall.bat. (Open a new terminal afterwards so PATH refreshes.)

Option B — run in place: skip the installer and just call .\multideck.bat from the repo folder.

The examples below use multideck; if you didn't install, use .\multideck.bat instead.

First run — build your config

Let it scan for you (no JSON by hand):

multideck -Init -BaseDir C:\code     # scans C:\code for git repos, writes multideck.config.json
multideck -DryRun                    # preview, then:
multideck

-Init walks the folder, finds git repositories (a few levels deep), and writes a config with groups derived from the top folder (internal/api → group internal), auto-assigned tab colors, and unique titles. Just run with no -BaseDir and it'll ask which folder to scan — in fact, the very first time you run multideck with no config, it offers to do this for you.

Or edit by hand: copy multideck.config.example.json to multideck.config.json and tweak it.

Everyday use

Run multideck with no arguments for the menu:

  multideck
  =========
   1) Launch missing + tile new windows   (default)
   2) Re-tile ALL open windows
   3) Launch a group   (internal, infra, lead-gen)
   4) Dry run (preview, change nothing)
   5) Re-generate config from a folder scan
   Q) Quit

Or skip the menu with flags:

CommandWhat it does
multideckInteractive menu (press Enter for the default: launch + tile new).
multideck -GoLaunch any projects that aren't open, then tile the new windows — no menu.
multideck -RetileAllRe-tile every matching window — already-open ones too. (multideck-retile.bat)
multideck -Group <name>Launch only the projects in that group.
multideck -DryRunPrint the launch + tiling plan and exit. Touches nothing.
multideck -Init -BaseDir <folder>Generate multideck.config.json by scanning a folder.
multideck -Config <path>Use a different config file.

Flags combine, e.g. multideck -Group infra -DryRun or multideck -Init -BaseDir C:\code -DryRun.

Configuration

Everything lives in multideck.config.json (generate it with -Init, or copy multideck.config.example.json):

{
  "baseDir": "C:/Users/you/code",            // root that relative project paths join onto

  "layout": { "columns": 2, "rows": 1 },     // tiles per screen

  "settings": {
    "defaultTool": "claude",                  // tool used when a project omits "tool"
    "settleSeconds": 3,                       // wait for new windows before moving them
    "launchDelayMs": 400,                     // pause between launches
    "tools": {                                // command run inside Windows Terminal, per tool
      "claude": "claude --continue",
      "codex":  "codex --yolo"
    }
  },

  "projects": [
    { "path": "internal/api",  "group": "internal", "color": "#3b82f6" },
    { "path": "internal/web",  "group": "internal", "color": "#22c55e" },
    { "path": "infra/tf",      "group": "infra",    "color": "#f59e0b", "tool": "codex" },
    { "path": "docs",          "group": "internal", "color": "#a855f7", "tool": "code"  },
    { "path": "labs/spike",    "group": "labs",     "color": "#ef4444", "enabled": false },
    { "path": "C:/work/ops",   "title": "ops" }
  ]
}

Paths accept forward slashes (internal/api) — no \\ escaping needed. %ENV% vars and ~ work too.

Fields

KeyWhereDefaultMeaning
baseDirtop levelscript folderRoot that relative project paths join onto.
layout.columns / layout.rowstop level2 / 1Tiles per screen. 2×1 = halves; 2×2 = quadrants; 3×1 = thirds; 1×1 = maximized.
settings.defaultToolsettingsclaudeTool for projects that don't set their own tool.
settings.settleSecondssettings3Seconds to wait after launching before tiling (only when something launched).
settings.launchDelayMssettings400Delay between launches so windows register in order.
settings.toolssettingsclaude, codexMap of tool name → command run inside Windows Terminal.
pathproject— (required)Absolute, or relative to baseDir. Forward slashes OK.
groupprojectnoneTag for -Group subset launches.
toolprojectdefaultToolWhich tool to launch. Use "code" to open in VS Code instead of a terminal.
colorprojectnoneWindows Terminal tab color (#rrggbb).
titleprojectfolder nameWindow title + the key used to find the window for tiling. Keep titles unique.
enabledprojecttrueSet false to skip a project without deleting it.

Layout examples

"layout": { "columns": 2, "rows": 1 }   // two columns per screen  (the default)
"layout": { "columns": 3, "rows": 1 }   // three columns per screen
"layout": { "columns": 2, "rows": 2 }   // four quadrants per screen
"layout": { "columns": 1, "rows": 1 }   // one maximized window per screen

Windows fill slots in list order, left-to-right then top-to-bottom, cycling across screens. List more projects than slots and later windows stack on the same slot — just like opening more than fit.

Groups

Tag related projects and launch them as a set:

{ "path": "lead-gen/upwork",   "group": "lead-gen" },
{ "path": "lead-gen/wellfound","group": "lead-gen" }
multideck -Group lead-gen     # opens + tiles just that group

-Init fills group in for you from the top folder of each repo, so a lead-gen/… layout is grouped automatically. Menu option 3 lists your groups to pick from.

Adding your own agent / tool

Anything that runs in a terminal works — add a line to settings.tools, then reference it per project:

"settings": {
  "tools": {
    "claude": "claude --continue",
    "codex":  "codex --yolo",
    "aider":  "aider --model sonnet",
    "shell":  "powershell"
  }
},
"projects": [
  { "path": "ml-service", "tool": "aider" },
  { "path": "scratch",    "tool": "shell" }
]

The command runs via cmd /k <command> inside a fresh Windows Terminal tab opened in the project folder. The special tool name code is handled separately — it launches VS Code in its own window and matches that window by title.

How the DPI handling works

Naïve window tilers read monitor sizes and call MoveWindow from a DPI-unaware process. Windows then hands back a virtualized 96-DPI coordinate space, so a 4K monitor at 250% reports as 1536×864 and a 1080p screen at 175% reports as 1097×617. The half-screen math is computed in that fake space, and on any monitor whose scale differs from the primary the rectangle gets mis-scaled — windows land too small, with gaps.

multideck flips the launcher to Per-Monitor-DPI-Aware (V2) before it reads any screen, so Screen.AllScreens and MoveWindow work in true physical pixels per monitor:

MonitorDPI-unaware (wrong)Per-Monitor V2 (multideck)
4K @ 250%1536 × 8643840 × 2160
1080p @ 175%1097 × 6171920 × 1080

The grid is then computed in real pixels and is correct on every screen regardless of its scale.

Troubleshooting

  • No config found — run multideck -Init -BaseDir <folder>, or copy multideck.config.example.json to multideck.config.json.
  • multideck not recognized after install — open a new terminal so the updated PATH loads.
  • Not found: <name> when tiling — the window title didn't match. Titles must be unique (-Init auto-disambiguates duplicates); if a tool overrides its own title, set a title and raise settleSeconds.
  • A project is skipped — its folder doesn't exist under baseDir (the path is printed), or enabled is false.
  • wt not recognized — install Windows Terminal.
  • Nothing tiles on re-run — by design, a plain run only positions windows it just opened. Use -RetileAll (or multideck-retile.bat) to re-snap windows that were already open.
  • Scripts blocked — the .bat files already pass -ExecutionPolicy Bypass; run those rather than the .ps1 directly.

License

MIT © Devino Solutions

Ver o original no GitHub

Bom para

Relacionados