Development / Part of the same desktop
From a keystroke
to the work.
A terminal environment is included. Editors and toolchains are yours to choose. Eitr connects the work around them: project folders, Git identities, cloud contexts and optional AI coding agents.
Included / Choose what comes next
A working foundation.
Your choice of tools.
Kitty, Zsh, tmux, Neovim with LazyVim, Git, Lazygit, Lazydocker, Docker and Docker Compose are included in Eitr’s package manifest. Installing Eitr does not install every editor, language environment or coding agent.
| Availability | Workflow |
|---|---|
| Included | Open Kitty with Super + Enter, or tmux with Super + Ctrl + Enter. Use Learn’s LazyVim, tmux and cmux references without leaving the desktop. |
| Curated optional installs | Install → Developer Apps offers Bruno, Cursor, GitHub Desktop, Insomnia, JetBrains Toolbox, Meld, Postman, Visual Studio Code, Zed. Official packages, AUR builds and managed installers keep their source-specific requirements. |
| Optional toolchains | Install → Development Languages offers Java LTS + Maven, Python + uv, Rust + Cargo, Ruby + Rails, Node.js LTS + npm, PHP + Composer, Elixir + Erlang, .NET SDK, Laravel + PHP + Composer. JavaScript Tools adds choices such as pnpm, Yarn, Bun and Deno. |
| Your existing projects | Development → LazyVim Projects or VS Code Projects asks for a folder under ~/Development and opens it in that editor. The VS Code workflow requires VS Code to be installed. |
Installation terminals explain what is happening and request permission where needed. Named Install lists mark installed tools; Delete offers confirmed removal. The Pacman/Yay package pickers remain install-only. Managed toolchain removal explains its wider effect before proceeding.
Keyboard-first / Graphical when useful
Keep your hands
in the flow.
Super + F opens Walker’s main menu. Typing searches apps and actions across Elephant menus; inside a submenu it searches that branch. Super + Space opens Apps, and Shift + Backspace returns to a parent menu.
Hyprland handles tiling, directional focus and workspace navigation. Super + H/J/K/L changes focus; Super + 1–9/0 changes workspace. Super + comma opens Control Center. Graphical configuration offers another entrance to the same settings and actions.
Read the generated keyboard & mouse reference →Optional / Provider accounts are separate
An assistant by choice.
A boundary by design.
Install → AI CLIs offers Claude Code, Codex, GitHub Copilot CLI, Grok Build, Gemini CLI and Antigravity CLI. Eitr’s first-use launchers offer installation when a supported command is missing; installed binaries take precedence. No assistant binaries, credentials or subscriptions are bundled.
Choose a machine-local default in Development → Default Assistant, then open it with Super + Alt + A. Project selection supplies the working folder. The bar’s AI Usage panel reports supported clients’ available usage information; account types and API billing may differ.
“Let assistants work together” is off by default. Supported, configured clients can request a second opinion through a local MCP bridge. Eitr retains the caller’s approval prompt, intends helpers for read-only consultation, and prevents onward delegation. Questions and context may go to the helper’s provider and count toward its limits.
Availability is distinct from validation. The Handbook records sign-in detection and per-client restrictions; Gemini requires a paid API key or a Google Cloud/company account in the documented workflow, and its real-account read-only behavior still needs verification. Antigravity is available as a standalone client and is not a collaboration helper. Do not treat the bridge as a security sandbox or enable blanket tool approval for it.
AI setup, permissions & current limitations →Git identities / Explicit cloud contexts
Choose the account.
Keep the context.
Development → Git Accounts configures a default identity and folder-specific rules after a review step. SSH keys and GitHub/GitLab CLI logins stay separate per account. Repository-local settings win; Eitr does not rewrite remotes or switch global provider CLI logins.
git var GIT_AUTHOR_IDENT
eitr-git cli auth status
eitr-git cli repo viewDevelopment → Cloud selects an account before opening resource tools. AWS profiles, Google Cloud configurations/projects and Azure tenants/subscriptions remain visible. Returning from a terminal retains the context without changing global CLI defaults.
Additional menus cover Cloudflare, DigitalOcean, Hetzner Cloud, Oracle Cloud, Vercel, Netlify and IBM Cloud in private per-account workspaces. These do not import existing provider credentials. Browser consoles use their own sessions; confirm their account separately. Newer provider workflows have mock-tested views, with live sign-in and resource checks still pending.
Cloud operations use your provider permissions. Some actions modify resources and can incur charges; a menu entry is not a promise of a free service or universal live testing.
Optional / Local tools and your services
Inspect the system.
Follow the signal.
Install → Databases offers DBeaver, MariaDB Client, MongoDB Shell (Mongosh), PostgreSQL CLI (pgcli), Valkey (Redis), SQLite. Client installation does not provision a remote database or grant access. Postman, Bruno and Insomnia are optional Developer Apps for API work.
Development → Monitoring saves named dashboard links for Grafana, Datadog, Sentry, New Relic, Prometheus or another service and opens them in your browser. It is a dashboard launcher, not a bundled monitoring backend. Monitoring Tools offers promtool and the Sentry CLI. Amazon Managed Grafana workspaces are under the selected AWS account.
Accounts, service configuration and permissions remain yours. Keep passwords and tokens out of dashboard URLs and shared configuration.
Read the complete development Handbook chapter →One environment / Beyond the editor
The work continues
around the tools.
The same desktop manages displays, sound, capture and appearance. System Update checks news and packages before taking a Btrfs snapshot when an upgrade is needed on supported setups. The Handbook covers recovery boundaries and independent backups.