i3
Sway
dwm
Openbox
awesome
Fluxbox
bspwm
Xmonad
Emisar.dev
Emisar is the last MCP server youโll need to install: a Zero-Trust gateway connecting Claude, Cursor, ChatGPT, and any AI agent to your infrastructure. One server handles production access, debugging, alerts, and internal operations, with new capabilities added as packs. Agents can inspect real production state, debug what they shipped, and help resolve incidents. Safe reads run automatically; policy allows, blocks, or routes risky actions for approval. No SSH keys, VPNs, remote shells, or standing shell access โ and every call is recorded.
Emisar.devNo features have been listed yet.
i3wm is recommended for advanced users, developers, and anyone who prefers a keyboard-centric interface. It is ideal for users who like to customize their environment extensively and are comfortable with configuring software via text files. New users with a willingness to learn may also find it rewarding.
No Emisar.dev videos yet. You could help us improve this page by suggesting one.
Emisar.dev's answer:
emisar is for SRE, DevOps, platform engineering, infrastructure, and security teams that want AI agents to inspect and operate production systems. It is especially relevant to teams managing multiple Linux hosts, clusters, databases, cloud services, or regulated environments where unrestricted shell access and incomplete audit records are unacceptable.
Emisar.dev's answer:
The hosted control plane and operator interface use Elixir, Phoenix, LiveView, PostgreSQL, and Tailwind CSS. The host runner and MCP bridge are written in Go. Action packs use YAML and JSON Schema, while production infrastructure is managed with Terraform on Google Cloud. The system communicates through MCP, OAuth 2.1, TLS, and WebSockets.
Emisar.dev's answer:
Emisar.dev's answer:
Founder Andrii Dryga spent a decade working as a CTO, full-stack engineer, SRE, and DevOps engineer. He experienced the cost of running the wrong command on the wrong cluster, while also seeing AI solve operational problems in seconds. emisar grew from the need to preserve both truths: AI agents are useful, and production access must remain bounded. Its answer is to give agents a reviewed catalog of operations instead of a blank terminal.
Emisar.dev's answer:
emisar lets AI agents work on real infrastructure without giving them a shell. Agents choose from a finite catalog of typed, versioned actions. Policy decides what runs, what requires approval, and what is denied, while an outbound-only runner verifies the action again on the host. New capabilities arrive as packs behind the same MCP integration, and every request is recorded in both a searchable audit trail and a tamper-evident host journal. [
Emisar.dev's answer:
Choose emisar when you want an agent to keep investigating and handling routine operations without handing it SSH credentials or supervising every call. Compared with raw shell access, copy-paste workflows, or one-off MCP servers, emisar provides reviewed action contracts, host-level enforcement, risk-based policy, scoped access, approvals, pack integrity checks, and a durable audit trail. It is built specifically for governed infrastructure access rather than generic automation.
Based on our record, i3 seems to be more popular. It has been mentiond 92 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I've been using Omarchy as my main setup since June 26, 2025, the day DHH released the first version. Before that I had my own custom Opinionated Linux, mclovin-ARCHived: an Arch + i3wm installer set up exactly the way I liked. It was total control over the OS: me deciding what goes in, keeping every piece (i3wm, polybar, picom, kitty, dotfiles) up to date and making sure they all talked to each other for the... - Source: dev.to / 3 months ago
Then few years back, in 2015, I got shown i3wm and used it on my ubuntu-netinstall until 2020, then I switched to Budgie and my personal laptop has been using that ever since. - Source: dev.to / 6 months ago
I switched to the i3 tiling based window manager. Because it's a whole different environment and thinking, it was very different from what I was used to. The volume buttons were working on my keyboard, but I didn't get any visual feedback. Furthermore, the volume percentage could go down below zero and increase up to more than hundread percent. There were times when I was confused why the keys stopped working, but... - Source: dev.to / about 2 years ago
This is partially why I use tools like i3 (/ sway). I like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. It just works. It is boring in the best way possible. Source: over 2 years ago
I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development. Source: about 3 years ago
Sway - Sway is a drop-in replacement for the i3 window manager, but for Wayland instead of X11.
dwm - dwm is a dynamic window manager for X. It manages windows in tiled, monocle and floating layouts. All of the layouts can be applied dynamically, optimising the environment for the application in use and the task performed.
Openbox - Openbox is a highly configurable, next generation window manager with extensive standards support.
awesome - A dynamic window manager for the X Window System developed in the C and Lua programming languages.
Fluxbox - Fluxbox is a window manager for X that was based on the Blackbox 0.61.1 code.
bspwm - A tiling window manager based on binary space partitioning
