Skip to main content

Terminal-layouts

Eight ready-made terminal workspaces. One command opens each, in tmux, Zellij or Herdr.

Type tmux-pentest and a full engagement workspace is in front of you: four tabs, fifteen panes, live socket and process monitors already running. zellij-pentest and herdr-pentest open the same layout (Herdr starts the monitors only when you ask, with --run-commands).

Install Terminal-layouts and enable the shell commands

The workflows

Open any of them with tmux-<workflow>, zellij-<workflow> or herdr-<workflow>.

Workflow Tabs you get Opens in
🖥️ project work (editor or agent, live git status, logs) · scratch current directory
🤖 ai-agents cockpit · implement · research · review, one coding agent per tab current directory
🏠 claude-projects cockpit · one tab per project · scratch ~/projects
🐳 docker stack (Compose, live docker ps) · logs · debug ~/docker
🎯 pentest recon · exploit · post · loot ~/ops/pentest
🔬 malware-analysis static · dynamic · network · ioc ~/ops/malware
📡 osint target · web · social · timeline ~/ops/osint
🏁 ctf cockpit · web · pwn · crypto · forensics · misc ~/ops/ctf

Each tab is laid out for its job. Two examples:

project › work                           pentest › recon
┌───────────────────────┬─────────┐      ┌───────────────────────┬─────────┐
│                       │ git     │      │ scanner               │ netmon  │
│ editor / agent        │ status  │      │                       │ live ss │
│                       ├─────────┤      ├───────────────────────┼─────────┤
│                       │ logs    │      │ enum                  │ notes   │
└───────────────────────┴─────────┘      └───────────────────────┴─────────┘

Every tab and pane of every workflow: Workflows. They are plain YAML, so you can change them or add your own.

Install

pipx install terminal-layouts
echo 'eval "$(command tl init zsh)"' >> ~/.zshrc    # bash: tl init bash, in ~/.bashrc
exec zsh
  • Needs Python 3.10+ and at least one of: tmux 3.4+ with tmuxp, Zellij, Herdr 0.8.2+.
  • Runs on Linux and macOS. On Windows, use WSL2.
  • Upgrade with pipx upgrade terminal-layouts.

Install with an AI agent

Paste this into Claude Code, Codex or any agent that has a shell:

Install Terminal-layouts from https://github.com/gl0bal01/terminal-layouts.
1. Check which of tmux (3.4+), zellij and herdr are installed. If none, ask me which one to install.
2. For tmux, make sure tmuxp is installed (pipx install tmuxp).
3. Run: pipx install terminal-layouts (already installed: pipx upgrade terminal-layouts)
4. Add eval "$(command tl init zsh)" to ~/.zshrc (bash: tl init bash, in ~/.bashrc),
   unless the line is already there. Show me the line before you write it.
5. Verify in a new shell: tl --version, tl validate, layouts.
Do not start any session, and do not use sudo without asking me.

Use

Every command is <backend>-<workflow>. Tab completes names, directories and options.

layouts                      # every command, with its directory
tmux-project                 # tmux:   this directory, session <directory>
zellij-docker                # Zellij: ~/docker, session docker
herdr-ai-agents              # Herdr:  this directory, workspace ai-<directory>
tmux-pentest --new acme      # create ~/ops/pentest/acme, session pt-acme
tl help                      # the manual

One manifest, three backends

tmux reads tmuxp YAML, Zellij reads KDL, and Herdr has no layout file at all. Keeping the same workspace by hand in each of them means the copies drift apart. Here each workflow is one YAML file, the only thing you edit. The tl command generates every backend from it, and the tests fail when two backends stop describing the same workspace. You can switch between tmux, Zellij and Herdr and find the same tabs and panes.

Documentation

Read To
Commands and options learn every command, where a workspace opens and how it is named
Tmux · Zellij · Herdr start from zero with one backend: install, first session, the few keys you need, troubleshooting
Workflows see the tabs and panes of each workflow, change them or write your own
Development work on the code: Make targets, tests, CI, how the generators work

In the terminal, tl help prints the manual for the manifest you use and tl COMMAND -h covers one command.

Development

git clone https://github.com/gl0bal01/terminal-layouts && cd terminal-layouts
pip install pyyaml jsonschema
make            # list every target
make test       # schema, parity, idempotence, unit and shell tests
make e2e        # launch every workflow on real, throwaway tmux, Zellij and Herdr servers
make ci         # every CI job, locally

Details in Development.

License

MIT

Metadata

Release files for terminal-layouts 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for terminal-layouts 0.2.0
File Size Uploaded Provenance Actions
terminal_layouts-0.2.0.tar.gz 59.0 kB Without provenance Details for terminal_layouts-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for terminal-layouts 0.2.0
File Interpreter ABI Platform Actions
terminal_layouts-0.2.0-py3-none-any.whl Python 3 none any Details for terminal_layouts-0.2.0-py3-none-any.whl

Total release size: 104.3 kB

Release files / terminal_layouts-0.2.0.tar.gz

Download URL terminal_layouts-0.2.0.tar.gz
Size 59.0 kB
Tags Source
SHA-256 checksum
How to use checksums
3d2df5a6f5207fe3fc9a032f062b2a727f45a008647ac221ddc330054e76b68e
BLAKE2b-256 checksum
How to use checksums
2edd8e18caa1718acc835c74bc133bd66ac7dc5feb8a42489e1bf292e0cba931
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / terminal_layouts-0.2.0-py3-none-any.whl

Download URL terminal_layouts-0.2.0-py3-none-any.whl
Size 45.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4e839292941e503f2906637ab328590ab73ea1071c80476f1573cb5895531e7a
BLAKE2b-256 checksum
How to use checksums
798d5986457b9cbffb9cafc8db3a9fad5125d964a4de81db7505c4df5667b62f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for terminal-layouts 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page