Using meith

meith is a single window that gathers the things you normally spread across an editor, a terminal, a browser, and a chat app while building a web app. Once you know where each surface lives, the daily loop is fast: open a project, split a couple of panes, start the dev server, and let an agent build features while you watch the preview update at every step.

The workbench at a glance

meith is a fixed desktop shell rather than a scrolling web page. From the outside in, the window is made of a few stable regions:

• A custom title baracross the top, with the meith mark, the active project's run controls, and window chrome.
• The far-left Spaces rail — an icon rail that works like a profile switcher, with one avatar per open project and buttons to create a workspace or open a folder.
• The central workspace, where your editor, browser, terminal, agent, and plugin tabs live and can be split into panes.
• A collapsible diagnostics drawer along the bottom for terminal output and dev-server logs.
• A status bar footer that shows live signals such as how many dev servers are running and on which port, plus whether the runtime is connected.

A typical session

1. Open a project folder from the Spaces rail. meith creates a space for it and scopes every tab you open to that project.
2. Split the workspace so you can see more than one thing at once — a common layout is an agent chat on the left and a live localhost preview on the right.
3. Start your project's run command from the title bar. The status bar shows the running server and its port, and the embedded browser tab can point straight at it.
4. Ask the agent to build something concrete — a component, a page, a feature. As it calls tools, each step appears inline; read-only steps run immediately and anything that touches your machine pauses for approval.
5. Watch the preview update and check the diagnostics drawer for logs as changes land.

Reviewing what changed

When an agent edits files, the edits aren't a black box. meith reads a project's working-tree changes — staged, unstaged, and brand-new files — and presents them as per-file diffs with added and removed line counts, so you can see exactly what was rewritten before you keep it.

Staying in control

Everything an agent or plugin does flows through one shared tool registry, and privileged actions stop for your sign-off. When a tool wants to write a file, control the browser, start a process, or do something destructive, meith pauses and asks. You can:

• Allow once to permit just this action,
• Always allow to create a standing grant, or
• Deny to stop it.

Read-only work never interrupts you, and every call is audited. See Tools & permissions for the full model.

Driving it from the terminal

meith also answers to a command line. The meith command talks to the running app over a local socket and calls the exact same tools the window uses — so you can open tabs, inspect dev servers, or stream logs without leaving your shell. Run meith setup once to add it to your PATH, then explore with The meith CLI.

Go deeper