> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kylon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# search

> Search rooms, messages, threads, files, and automations.

```text theme={null}
kylon workspace search — kylon workspace help detail

search — global workspace resource search
    Search procedure:
    1. Infer the likely resource type, scope, and filters before searching.
    2. Use compact literal queries: names, IDs, distinctive nouns, object labels, and short keyword variants. For Chinese or other no-space text, also try the main noun phrase without filler words.
    3. For a workspace-wide Find request with no explicit resource type, start with kylon workspace history search --room all. Search files, Apps, App records, workflows, rooms, or members only when the user names that type or history results point there.
    4. Apply user-provided scope such as room, date range, owner, sender, status, App, or record in the first search.
    5. Run a few high-probability query variants up front. Ignore matches from the current request, earlier search attempts, and your own no-result replies.
    6. Check focused command help when syntax or filters are unclear; do not guess flags.
    7. State the scope and filters actually searched. If a missing filter would materially reduce false positives or cost, ask a concise kylon workspace ui send question before running a broad search.

  kylon workspace search <query> [--type room|dm|message|thread|file|automation|all] [--offset <n>]
    Search visible rooms, DMs, threads, files, and automations
    from one command. Empty resource groups are omitted. Use --type with
    --offset to fetch the next page for one resource group.

    Use this global search after the history-first pass when the resource type
    remains unknown, or when the user explicitly asks to search across resource
    types. Use --type for quick cross-workspace discovery of one resource type
    when no resource-specific filters are needed.

    Prefer resource-specific commands when the resource type is known and you
    need filters, current-room semantics, larger result sets, or follow-up
    operations:
    - history search: message/thread content and sender filters.
    - file list --query: file lookup with type, directory, date, creator, or room filters.
    - workflow list --query: automation management.
    - member list --query: member/user ID lookup before membership or DM operations.
    - room list --query: room lookup across the agent's joined rooms; --writable lists the same set.

    After global search identifies a resource, switch to the corresponding
    resource command for detailed inspection or mutation.
Resource link handoff:
- Emit identified Kylon resources as clickable, path-only markdown links with human-readable labels.
- Copy command-returned links verbatim. Otherwise substitute known IDs into the relevant format below; do not guess a path.
- Search results include ready-to-use resource links when available; copy them verbatim. Use the matching resource help page before constructing a missing link from IDs.

Note: quote flag values that contain spaces; follow each command's JSON syntax.
```