This guide explains where to open Metnos, how to sign in for the first time, how to use the chat, and how to add a user. The structure of the administration pages is described separately in the interface guide.
Metnos runs on the computer where it is installed, at home or in the office. The chat address depends on your installation. The addresses below provide direct access from the local network; if your administrator has supplied a protected HTTPS address, use that instead. The metnos.com website hosts documentation, not your conversation.
The web chat is available on port 8770. To open it, type the complete address in your browser's address bar, including http:// and :8770. On the computer hosting Metnos, use http://127.0.0.1:8770/. If, for example, that computer's address on the local network is 192.168.1.42, type http://192.168.1.42:8770/ on a phone or laptop connected to the same network.
By default, the guided installer makes the chat reachable from the local network. During Metnos installation, at step 4, you can choose for greater security to allow access only from the computer hosting the system. With this setting, the chat can be opened only in a browser running on that computer; other devices on the local network cannot connect.
| Where you open it from | Address to type in the browser |
|---|---|
| From the computer hosting Metnos | http://127.0.0.1:8770/ |
| From another device on the same local network | http://192.168.1.42:8770/ (example: use the address shown by the installer) |
You do not have to guess the address: when the installation ends, Metnos prints the exact addresses to use and saves them in ~/.local/share/metnos/install_summary.md. If you lost them, open that file again.
When the installation ends, Metnos gives you a complete address that already contains a single-use access code: open it exactly as it is, without editing it. If there is more than one address, one is for the computer itself and the others are for the other devices on the network.
If that code has expired you have two ways: re-run the last installation phase, which issues a new one, or open /admin/login and paste the administration key. The key is a text file on the computer hosting Metnos, at ~/.config/metnos/admin.key: it is read from there only, and it is not to be sent to anyone.
./.venv/bin/python -m install --force-phase 6Once you are in, the browser keeps the access and does not ask for the key on every visit.
Describe the outcome you want in your own words, without learning a list of commands. When your permissions and instance rules require confirmation, Metnos presents the proposed operation and waits for your consent.
The header shows Metnos and your role. The Settings link opens the administration area after sign-in; administrators also have a Sign out control. Chat and administration pages share the same header. On Settings pages, the Chat link returns to the conversation.
To keep a copy of the conversation, choose Export in the top menu: the chat text is copied to the clipboard, ready to paste into a document. To attach a file to a message, use the paperclip icon beside the message field.
You can also use Metnos through Telegram. Your identity and permissions stay the same, while each channel keeps its own conversation and history. A Settings path mentioned on Telegram must be opened in a browser.
The capability guide offers request examples for each area. Ask the Tutor which functions you can use on your installation.
A red $ on a step indicates use of a cloud model. It remains visible after resuming from a form such as a CAPTCHA; the response also reports the number of requests sent to the cloud model.
Open Settings from the chat header. Its first page gives a system overview; the sidebar groups Activity, Monitor, Lifecycle, Memory, and System. These page addresses begin with /admin. Use the header to return to chat. The interface map lists every page and path, generated from the Metnos code.
Pages under /admin are reserved for the instance administrator. An invited guest may use the chat but cannot open Settings.
/admin/users without a valid administrator session, Metnos takes you to the sign-in page and preserves the destination. After you enter the administration key, the browser returns to the requested page automatically. For example, if Metnos is available at 192.168.1.42, you can open http://192.168.1.42:8770/admin/users; when necessary, the visit to /admin/login happens in the same browser. An authenticated user without the administrator role receives an explicit denial instead and gains no new permissions.Activity > Turns lists completed turns, most recent first. Choose 50, 100, or 200 rows. Dates and times follow the instance language and time zone, including seconds and the zone name; durations use seconds, minutes, or hours. A request still in progress does not appear in this list.
Monitor brings together observations about LLM requests, model performance, and executors. Its glossary explains the measurement terms. Total request time includes waiting and other steps, so it differs from the model’s generation speed. An unavailable measurement should not be read as zero.
Each chart point summarizes an interval: mean tokens per call and mean call duration; median and 95th percentile for request durations. Speeds are weighted by valid durations. The database includes all filtered samples without a 10,000 limit; analytical history expires after 90 days, preserving open requests and chains with recent activity. The glossary explains aggregation and retention.
The Executor catalog card in Settings counts the executors in the current catalog. Select View all to check them in the list: the origin column distinguishes Handcrafted, Built-in, Synthesized, and Imported. The four origins add up to the total; deprecated executors are already included. Under Statistics, counts by origin and state use the same catalog. The events chart preserves the history of the last 30 days, using the origin recorded at the time: an old event does not prove that an executor is still available.
You need this when you want another user — a family member or guest — to use your Metnos with their own identity, history and permissions. There are two distinct steps: first you create the user's profile, then you give them a way in.
/admin/users.| Field | What to put in it |
|---|---|
| name | A short identifier, lowercase letters, digits and underscore only: guest or guest_2. It is required. |
| display name | The name as you read it: Invited guest. |
| The person's address, if they have one. | |
| role | guest for a guest, host for a second owner. When in doubt leave guest. |
| autonomy | How much they may do on their own: read_only only looks, restricted asks for confirmation on operations that change something, full goes ahead alone. When in doubt leave restricted. |
Open the user's name in the list to reach their detail page, and from there issue a connection code for the channel they will use. The code is valid for one hour and is single-use.
/start followed by the code; the bot answers with a confirmation.From that same detail page you can later edit the user's data, disconnect a channel, change their preferences or delete the user.
You do not have to memorise any of this. Ask Metnos in the chat, in your own words: "where do I change the model?", "how do I invite someone?". It answers with the path and the address of the page, and describes what is in your installation. If a page does not exist on your instance it says so, instead of inventing it.