--- title: "Meko Local Web UI" url: "https://docs.mekodata.ai/use-meko/web-ui/" --- # Meko Local Web UI Use the web UI to manage your local datapacks `meko ui` opens the web UI at [http://127.0.0.1:7777](http://127.0.0.1:7777). It has no login. This is the UI for Meko on your computer. The [Meko portal](https://cloud.mekodata.ai/) is a separate site. Use [`meko`](/reference/meko/) to run the server. ## Datapacks The sidebar lists the datapacks on this computer. If [Meko Cloud](#meko-cloud) is linked, it also lists cloud datapacks, and new datapacks are created there. Selecting a Cloud datapack opens the datapack in Meko Cloud. Select a local datapack to work with it: - **Overview** summarizes the datapack: how much context it holds, how much of that is collective memory, and recent searches. - **Metrics** shows the size of stored context, how memories split between private, pending promotion, and promoted, and how long searches take. - **Conversations** is the saved turns. - **Memories** lists facts taken from those turns, or saved directly. You can add a memory, delete one, and promote one into collective memory. A memory's page shows the conversation it came from. - **Knowledge** lists the [knowledge bases](/concepts/knowledgebase/) that have been added to the datapack. You can upload a file here. - **Artifacts** lists the [artifacts](/concepts/artifacts/) that have been added to the datapack. Agents save them, and you can download them. - **Search** across memories, the knowledge base, and past conversations. With [Search answers](#uses-your-claude-code) on, Claude Code provides an answer above the results, from those results, and cites them. - **Context Gaps** lists searches that found nothing, or nothing relevant, so you can teach Meko the missing fact. - **Connect** shows the address and token an agent uses to reach this Meko. You can edit a datapack's name and description, export it, or delete it. Export writes a datapack that is on this computer to a zip file. To invite teammates to a datapack, open it in Meko Cloud. See [Datapacks](/use-meko/datapacks/) for sharing on Meko Cloud, and [Where to store it](/concepts/where-to-store/) for information about memory, knowledge-base files, and artifacts. ## Status **Status** shows whether Meko is running, the context engine, how long this process has been up, the data folder, and whether a newer release is waiting. ## Agents **Agents** shows the agents on your local machine that are connected to Meko, either locally or on the linked cloud. ## Extensions **Extensions** lists applications that plug into Meko and are served on its port. Meko can install two extensions, Kode and Present. The installer offers only Kode. Add Present with `meko extension install present`. Use the **Extensions** page to manage running extensions, including installing and uninstalling, starting and stopping, and checking for updates and updating. You can also install, start, and remove extensions using `meko extension`. Kode's command is `meko kode`, and Present's is `meko present`. See [meko Commands](/reference/meko/#commands). ### Kode Kode is an agentic coder for ADLC. Kode lets you run parallel coding sessions that take a task from design to merged PR, with Meko as the shared context engine, so designs and what each session learned flow into datapacks your whole team and their agents can build on. Kode runs Claude Code, OpenCode, or Kiro sessions across your projects, from a task to a merged pull request. Open it, pick a repository, and Kode creates a datapack for that project. Start a task in plain words, or from a GitHub issue or pull request. Each task moves through Explore, Design, Code, Pull Request, and Merge & Close phases. You approve the design, opening the pull request, and the merge, or let **Run to merge** do the rest. A session keeps running when you close the page. While Meko Cloud is linked, Kode keeps each new project's datapack in Cloud. Requires Claude Code, OpenCode, or Kiro CLI on your computer. For more information, see [Kode](https://github.com/yugabyte/meko/blob/main/src/extensions/agentk/README.md). ### Present Build presentations from your datapacks dynamically. The deck is a map of paths, allowing you to choose a path for your audience to follow, instead of walking one fixed sequence of slides. To get started, pick the datapacks to draw from, and write a short brief. Claude drafts a story map of scenes, forks, and detours. You can walk through it and reshape it, then let Claude build the slides. During a talk, the console shows the slide, what's next, your notes, and the sources the slide rests on, and the audience window follows on the projector. You pick a fork using a number key. Building a deck requires Claude Code. Playing and editing a deck do not. See [Present](https://github.com/yugabyte/meko/blob/main/src/extensions/present/README.md). ## Projects **Projects** groups datapacks into folders for one outcome. Each datapack stays its own store. See [Projects](/use-meko/projects/). ## Settings Use **Settings** to connect to Meko Cloud and configure your local Meko. ### Meko Cloud Link this Meko to a Meko Cloud account. Sign in with the browser, or paste an API key. While linked, new datapacks are created on Cloud; local datapacks stay local. Agents stay connected to the local Meko, which sends each call to the side that has the datapack. Extensions such as Kode keep a new project's datapack in Meko Cloud. Unlink, and they use your local Meko again. **Your own Meko server** sets three addresses. Leave them empty for Meko Cloud. | Setting | What it is | |--------------------|--------------------------------------------------------------------| | **MCP server URL** | Where agents connect. Empty means Meko Cloud. | | **Web app URL** | Links to datapacks and sharing. Empty is filled in for Meko Cloud. | | **API URL** | The REST API. Empty is the web app URL plus `/api/v1`. | You can also connect to Cloud using [`meko cloud-link`](/reference/meko/#commands). ### Uses your Claude Code Meko can run your own Claude Code in the background, with no tools (Codex and Cursor are in development): - **Memory extraction** pulls memories out of your conversations automatically, from your own messages, every few minutes. - **Search answers** writes an answer above a Search page's results. Because each call uses your Claude quota, these settings are off by default. You can also control these settings using `meko memory-extractor` and `meko answers`; see [meko Commands](/reference/meko/#commands). ### Access **Access** determines who can open the web UI: - **Local** accepts a request made on this computer, straight to Meko's address. A request that arrives another way, such as through a proxy or from another device, is refused. - **Remote** accepts requests from other devices, over HTTPS. There is no login: anyone who can reach this computer's port can use Meko. ### Calls Enable **Calls** to store what agents, `meko-cli`, and the UI asked Meko to do. Click **View calls** to display the **Calls** page, which lists the saved calls. Select a call to see details. ### Anonymous usage stats **Send usage stats** sends anonymous usage stats to YugabyteDB.