Introduction

meith collects the pieces web developers usually scatter across multiple windows — project folders, code files, terminal sessions, a live localhost preview, run commands, dev-server logs, plugins, and agent chats — and puts them in one place. A shared tool system connects everything, so the visual app, the terminal command, a plugin, and an AI agent all act on the exact same project state instead of their own isolated views.

The name comes from the Irish meitheal: a group of people coming together to work on a common task. In meith, the app, command line, plugins, and agents gather around a single workspace.

What you can do with it

• Open a web project folder in its own workspace.
• Browse and edit your app's code in the integrated editor.
• Start and stop your dev server from the top bar.
• Preview the running app on localhost in an embedded browser tab.
• Watch the preview update and read dev-server logs in the window.
• Split panes to arrange your preview, editor, terminal, or agent side by side.
• Ask an agent to build features in your project's context — editing files, running the dev server, and checking the live preview.
• Install web-app plugins and explicitly approve the APIs they can use.
• Use the meith terminal command to inspect and control a running app instance.

Not locked into one AI provider

meith doesn't tie you to a single model vendor. The agent runtime uses an adapter interface and connects to external agents via ACP (Agent Client Protocol), keeping the desktop app independent of any specific AI provider or SDK.

Where to next