tinyhumansai/openhuman · error

no app session JWT — not signed in

Error message

no app session JWT — not signed in

What it means

Doctor diagnostic: reading the app session JWT succeeded but no token is stored (empty/None), meaning the user is not signed in to the TinyHumans backend. This is a warn-level state report, not an error: backend-dependent features (hosted inference, announcements, team, sync) will be unavailable or degraded, while purely local operation continues.

Source

Thrown at src/openhuman/platform/doctor/core.rs:210

        .filter(|s| !s.is_empty())
    {
        items.push(DiagnosticItem::ok(cat, format!("api_url: {url}")));
    } else {
        let resolved = crate::api::config::effective_api_url(&config.api_url);
        items.push(DiagnosticItem::ok(
            cat,
            format!("api_url: (unset) resolved to {resolved}"),
        ));
    }

    match crate::api::jwt::get_session_token(config) {
        Ok(Some(token)) if !token.trim().is_empty() => {
            items.push(DiagnosticItem::ok(cat, "signed in with app session JWT"));
        }
        Ok(_) => {
            items.push(DiagnosticItem::warn(
                cat,
                "no app session JWT — not signed in",
            ));
        }
        Err(err) => {
            items.push(DiagnosticItem::error(
                cat,
                format!("failed to read app session JWT: {err}"),
            ));
        }
    }

    // Model configured
    if config.default_model.is_some() {
        items.push(DiagnosticItem::ok(
            cat,
            format!(
                "default model: {}",
                config.default_model.as_deref().unwrap_or("?")
            ),

View on GitHub (pinned to 7491200858)

Solutions

1. Sign in via the app's auth flow if backend features are needed
2. If you believe you are signed in, check whether the keyring/credential store is accessible — a failed token read reports as a separate error item
3. Re-run 'openhuman doctor' after sign-in to confirm 'signed in with app session JWT'
4. Local-first usage can ignore this warning

When it happens

Trigger: Thrown at src/openhuman/platform/doctor/core.rs:210 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17). Data as JSON: /api/errors/e64d56902ceb1d9e. Report an issue: GitHub.