For agents and technical readers

Diagnose workspace availability without changing work

Identify the failing boundary, inspect read-only state and preserve the original action reference before considering a retry.

Contents

Establish identity and scope

Distinguish Mensara account sign-in, Mind Portal session, external client connection, model route and service connection. Call orient {} only through the intended supported connection and inspect its Mind/principal before reading harmless authorised information.

The Portal Settings diagnostics are Access configured, Mind reachable, Access token accepted, Version supported. Start with the first failed check; later unknown states are not observed denials. Read the Portal About version and obtain Core/app versions through the authorised operator or installed app state.

Read bounded process health

When advertised and authorised, get_health_v1 {} reads process metadata and waiting counts. It requires the owner’s recovery authority or an app’s narrow read_health capability; it grants no content or lifecycle permission.

Read generated time, apps, automations, loops and waiting categories. The result can omit purpose text outside an app’s readable scope. It contains metadata, not the underlying proposal diffs or question text. A count alone does not establish the outcome of a named request.

Inspect the affected object

For a proposal, use its original ID and current source. For an app, inspect installed version, schedule, grant, connection, budget and existing run. For a loop, inspect its existing case and wait. For a Network send, retain exact payload/key/peer binding. For checkout, use the original account confirmation.

If a read is incomplete, denied or unavailable, report that state. Do not declare an empty Inbox or successful job. Reconnect through the normal route only for the actual failed boundary, then repeat a harmless read.

Retry only after reconciliation

A transient read can be repeated. A write, approval or external effect needs its original state checked first. Session expiry, changed source, revoked permission or peer-generation change requires current authority/state; an old approval does not cover new bytes.

Collect bounded error, time, versions, role and references. Exclude document bodies, model payloads, credentials and private recovery material. Use help by symptom and the specific procedure to hand off an unresolved failure.

Related

Manage notifications and check your Mind’s health · Fix sign-in and reconnect the right service · Recover pending, failed or interrupted work · Check your version and understand product changes

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Diagnose workspace availability without changing work

Operating procedures · For agents and technical readers · [How it works](https://app.mensara.ai/how-it-works)

Identify the failing boundary, inspect read-only state and preserve the original action reference before considering a retry.

[Page as Markdown](https://app.mensara.ai/how-it-works/workspace-diagnostics-procedure.md)

[Human guide](https://app.mensara.ai/how-it-works/notifications-and-health)

## Use the released interface with current authority

Availability: Core0.20.11 / Portal0.3.47 source checked; discover the actual installed client and enabled features.

Who can do this: The connected principal with the permissions named in this procedure

What changes: The procedure explains its actual reads, writes or external effects before action.

Limits: An input accepted by a source schema is not a successful installed-runtime task.; Keep human decisions, client exclusions and pending results explicit.

Verification: Source checked and independently reviewed; scoped runtime receipts are recorded separately.

## Establish identity and scope

Distinguish Mensara account sign-in, Mind Portal session, external client connection, model route and service connection. Call `orient {}` only through the intended supported connection and inspect its Mind/principal before reading harmless authorised information.

The Portal Settings diagnostics are **Access configured**, **Mind reachable**, **Access token accepted**, **Version supported**. Start with the first failed check; later unknown states are not observed denials. Read the Portal About version and obtain Core/app versions through the authorised operator or installed app state.

## Read bounded process health

When advertised and authorised, `get_health_v1 {}` reads process metadata and waiting counts. It requires the owner’s recovery authority or an app’s narrow `read_health` capability; it grants no content or lifecycle permission.

Read generated time, apps, automations, loops and waiting categories. The result can omit purpose text outside an app’s readable scope. It contains metadata, not the underlying proposal diffs or question text. A count alone does not establish the outcome of a named request.

## Inspect the affected object

For a proposal, use its original ID and current source. For an app, inspect installed version, schedule, grant, connection, budget and existing run. For a loop, inspect its existing case and wait. For a Network send, retain exact payload/key/peer binding. For checkout, use the original account confirmation.

If a read is incomplete, denied or unavailable, report that state. Do not declare an empty Inbox or successful job. Reconnect through the normal route only for the actual failed boundary, then repeat a harmless read.

## Retry only after reconciliation

A transient read can be repeated. A write, approval or external effect needs its original state checked first. Session expiry, changed source, revoked permission or peer-generation change requires current authority/state; an old approval does not cover new bytes.

Collect bounded error, time, versions, role and references. Exclude document bodies, model payloads, credentials and private recovery material. Use [help by symptom](https://app.mensara.ai/how-it-works/questions) and the specific procedure to hand off an unresolved failure.

## Related

- [Manage notifications and check your Mind’s health](https://app.mensara.ai/how-it-works/notifications-and-health)
- [Fix sign-in and reconnect the right service](https://app.mensara.ai/how-it-works/reconnect-and-sign-in)
- [Recover pending, failed or interrupted work](https://app.mensara.ai/how-it-works/interrupted-work)
- [Check your version and understand product changes](https://app.mensara.ai/how-it-works/versions-and-changes)

[Join the waitlist](https://app.mensara.ai/#waitlist)