Metnos is more than a chat window: it can find, read, transform and create content, use configured services, operate on paired devices and run scheduled tasks. This page brings those capabilities together without confusing what is available with what remains an architectural possibility.
A capability is considered available only when it has an executor or active service, an input and output contract, applicable policies, and an authorisation path. Ideas without those elements are explicitly identified as unavailable. The current operational list is also available in web chat under Settings › System › Services.
Metnos can work on authorised server paths and, when requested, on paired devices. Operations include:
Search does not grant automatic access to the whole filesystem: every path remains subject to workspace policy and the user's identity.
Configured accounts extend available operations without changing the authorisation model. Depending on active services, Metnos can:
Additional mailboxes and accounts can be used by entering their credentials. Credentials belong to the user who configured them and do not make data, sessions or authorisations shared.
Metnos currently provides no ambient voice listening, home-automation control, passive observation of third-party chats, or general agent-to-agent channel. It does not monitor a family conversation in the background or infer assignments from sources the user has not queried or authorised. An external agent cannot approve operations on a user's behalf.
These possibilities may be studied as future extensions, but they require verifiable identity, consent from the people involved, constrained sources and a dedicated audit contract. They are neither hidden options nor capabilities that can be enabled by a simple setting.
Metnos can formulate proposals when the producing subsystem has a mandate and relevant data, for example by suggesting the next step after a search or showing a change before applying it. A proposal is not an authorisation: operations with external effects still pass through policy, the vaglio and approval.
Scheduled tasks are a separate case. The user creates a mandate with a date or recurrence; the scheduler runs it in the same user's context and records its result, errors and next run. This is not spontaneous initiative by the model.
External capabilities include:
Web content remains untrusted data: it cannot change policy, grant permissions or issue privileged runtime instructions.
Telos express declared ends and preferences. The vaglio separates evaluation from proposal and applies constitutional constraints before any utility judgement. A user profile may guide the final wording of a response, but it does not covertly alter deterministic routing or turn model-generated prose into evidence.
When personal information is used, the reliable source remains the authorised original turn or datum. The relevant user must be able to inspect, correct and delete preferences and observations.
Every operation runs in a user's context. Language, preferences, credentials, services, sessions, scheduled tasks and data are not transferred to another user merely because they share the same server.
A paired device is an execution location, not a second identity. When the same person moves from a phone to a computer, they can continue the earlier session by transferring it to the current device; alternatively, they can make the current session active and close the earlier one, or cancel. The choice affects that user only.
Ask Metnos with requests such as these:
If the request comes from Telegram and refers to a settings page, the stated path is in the Metnos instance's web chat.
Metnos — Extended perspectives
Available capabilities, boundaries and evolution criteria.