Lattice OS logo
Lattice OS
Support Center

Need help with Lattice OS?

Whether you're troubleshooting a route, trying to understand the platform architecture, or reporting a bug, this page is the fastest way to get support or find the right docs.

Email Support

Reach out directly for account questions, technical issues, bug reports, or product feedback.

[email protected]

Documentation

Use the docs hub for architecture, runtime behavior, API references, environment variables, and operational guidance.

View Docs

Start with self-serve help

The docs surface now covers the platform more explicitly — architecture, security, deployment reality, runtime behavior, API surfaces, and operational reference material.

Platform Documentation Hub

Architecture, security, operations, reference docs, and ADRs in one place.

Runtime & Context Architecture

Best starting point if you're trying to understand how Lattice chooses behavior and assembles context.

Security & Route Boundaries

Useful if your issue looks like a public/auth mismatch, route block, or permission-boundary bug.

Operations & Debugging

Use when the problem looks like deployment, routing, CI/runtime mismatch, or incident diagnosis.

Account & Access

For sign-in, onboarding, auth gates, and user access issues.

  • Sign-in and sign-up issues
  • Unexpected auth redirects
  • Onboarding flow problems
  • Access to docs, support, or protected routes

Product & Runtime Behavior

For chat behavior, workspaces, operating profiles, and runtime-mode questions.

  • Conversation or workspace issues
  • Runtime mode/routing behavior
  • Prepared context and memory behavior
  • Unexpected response or product-state flow

Technical Issues & Bugs

For broken pages, route regressions, deployment/runtime mismatches, and system-level problems.

  • Broken routes or 404s
  • API/runtime mismatches
  • Deploy worked but live behavior is wrong
  • Public/authenticated boundary regressions

Integrations & Operations

For Slack, Telegram, webhooks, automation, cron, and operational troubleshooting.

  • Slack or Telegram integration behavior
  • Webhook/callback issues
  • Cron and background task failures
  • Operational debugging questions

How to report a bug well

The fastest way to get a useful response is to include the details that make the issue reproducible. If you can, include both what happened and what you expected to happen.

Helpful details

  • The route, page, or feature affected
  • What you expected to happen
  • What actually happened instead
  • Whether you were logged in or logged out
  • Screenshots or screen recordings if available
  • Any steps that consistently reproduce the issue

Especially useful for technical issues

  • Include the exact URL if the issue is route-specific
  • Mention whether the issue is public-route, API, or workspace-related
  • Mention whether the problem happened locally, in CI, or only in production
  • If relevant, include any visible error message or request/response clue

Send us a message

If the docs don't answer it, reach out here and we'll get back to you as soon as possible.

Response expectations

We aim to respond to support requests as quickly as possible. If the issue is urgent, make that clear in the subject line and include the route or feature affected.