Conversation is the primary way to use Metnos. The interface makes visible what dialogue represents less effectively: system state and the controls used to govern it. This page describes its structure and shows where to find each administrative function.
This map is generated from the list of pages defined in the Metnos code. Names, paths, and addresses therefore follow the interface. Ask the Tutor about a page's fields, controls, or instructions: it uses information from your installation.
Metnos is available through the instance's web chat and through Telegram. Both channels recognise the same identity and authority, but keep separate conversations and histories. Administration pages belong exclusively to the web interface: a Settings path mentioned on Telegram must therefore be opened in a browser. If the web chat is opened on a second device while another session is active, Metnos offers three choices. Cancel preserves the existing session and leaves the new browser read-only; Make this session active activates the conversation already present in the new browser; Continue the previous session transfers the first device's conversation to the new one. Histories are not merged, and the browser whose active session is revoked becomes read-only. Sessions and histories remain separate for each user: an owner session conflict does not involve a guest, and vice versa.
Settings is the administration area of the web interface. Its first page provides an overview of system state. The sections listed below group pages by subject. Each page is reached through “Settings > Section > Page” and has an address beginning with /admin. Labels are available in Italian and English; if the selected language is not translated yet, the interface uses English. The Tutor reports paths using the same labels shown by the interface.
/adminStatus overview and access to the administration areas.
/admin/turnsRequests with channel, actor, steps, and outcome.
/admin/runsScheduled-task runs with outcome and duration.
/admin/timersSystem timers, state, and available controls.
/admin/monitorComplete user request trends and collection health.
/admin/monitor/requestsMeasurements for complete requests and linked turns, without retaining question text.
/admin/monitor/modelsCall statistics by logical name, physical model, and provider; separate from model configuration.
/admin/executors/statsOperational executor statistics.
/admin/changesChange proposals and their approval lifecycle.
/admin/executorsInstalled executors, membership, state, and exclusion reasons.
/admin/praxisCognitive-engine layer state and related configuration.
/admin/virtEffective configuration for language, embedding, and vision models: LLM and VLM are editable; embedding is view-only. Storage of OpenAI and Anthropic API keys.
/admin/servicesMetnos services with state, health, installation, PID, and controls.
/admin/lreConsole for long-running work submitted to LRE, including progress, limits, events, and artifacts.
/admin/safetySignatures governing executor authorization and confirmation.
/admin/usersUsers, roles, and associated channels.
/admin/credentialsStored credentials, never showing passwords or other secrets.
/admin/devicesPaired remote devices that run executors.
Pages under /admin require the instance administrator role and are not available to guests. The Tutor can explain a page to someone allowed to know about it. An explanation does not grant permission to open the page or change its data.
You do not need to memorise the map. For example, ask: “Show me which embedder is configured under Settings > System > Models and tell me how to reach the page from the web chat.” The Tutor answers in both the web chat and Telegram, but administration paths always open in a browser. When you ask where a function is or what a page contains, the answer uses the path, address, and contents verified in the current installation, not a generic description. If the page is unavailable, the Tutor says so rather than suggesting a path that does not exist.