Search syntax
GitHub-style qualified search for files and issues — type:, mime:, ext:, category:, status:, assignee: and more, with autocomplete.
Search boxes across Multica accept GitHub-style qualifiers mixed with free
text. Plain words run a full-text search; qualifiers narrow the results. Prefix
a qualifier with - to exclude, and wrap multi-word values in double quotes.
Autocomplete
The file search box suggests qualifier keys as you type, and the values for the
key under the cursor (document types, categories, is:/has: options, …). Use
↑/↓ to move, Enter or Tab to accept, Esc to dismiss. Click the ? next to any
search box for the in-app reference.
Files
Search files by metadata (title, description, filename — never file content):
type:prd is:root # all PRDs with no parent
ext:pdf category:Docs # PDFs in the "Docs" category
type:rfc -has:children # RFCs with no nested files
issue:MUL-7 in:title plan # files attached to MUL-7, matching "plan" in the title| Qualifier | Meaning |
|---|---|
type:<slug> | Semantic document type (plan, ard, test, rfc, prd, brd, fsd, user-story, or a workspace-custom type) |
mime:<class|mime> | Format / MIME (mime:image, mime:pdf, mime:text/markdown) |
ext:<ext> | Filename extension (ext:pdf, ext:md) |
category:<name|uuid> | Workspace category |
issue: project: agent: squad: checker: | Files attached to that owner (name or UUID) |
owner:<type> | Files attached to any owner of that type |
is:root is:child is:orphan | Hierarchy position |
has:children has:parent has:attachments | Relationship presence |
parent:<file-id> | Direct children of a file |
in:title in:description in:filename | Restrict free-text matching to one field |
creator:@me creator:<member|agent|system> | Who created the file |
type: changed meaning
type: now selects the document type, not the file format. Filter by format
with mime: (MIME) or ext: (filename extension).
Manage document types and categories in Settings → Files. System types are built in and read-only; add your own to classify files. From the CLI:
zagents files types list --output json
zagents files types create --slug design-doc --name "Design Doc"
zagents files list --type prd
zagents files search "type:prd category:Docs -has:children"Issues
Issue search accepts a focused set of qualifiers mixed with free text:
status:in_progress assignee:@me # my in-progress issues
priority:high is:open payment # open high-priority issues mentioning "payment"
project:Backend status:todo # todo issues in the Backend project| Qualifier | Meaning |
|---|---|
status:<backlog|todo|in_progress|in_review|done|blocked|cancelled> | Issue status |
priority:<urgent|high|medium|low|none> | Issue priority |
assignee:@me / assignee:<uuid> | Assignee |
project:<name|uuid> | Project |
is:open / is:closed | Open (not done/cancelled) vs. closed |
From the CLI: zagents issue search "status:todo assignee:@me migration".
Unknown qualifiers and invalid enum values fall back to plain free-text search — a typo never errors.