Feature Request: Expose chat labels/folders in Desktop API (available on mobile)

[turian]

Summary

Labels/folders exist in Beeper mobile apps but are not exposed in the Desktop API, blocking read-only triage workflows.

Current State

The Chat model in desktop-api-python exposes these fields:

• id, account_id, network, participants, title, type
• unread_count, is_archived, is_muted, is_pinned
• last_activity, last_read_message_sort_key, local_chat_id

Missing: Any field for labels, folders, or spaces.

Evidence That Labels Exist

Labels were announced for iOS/Android in the November 2025 Beeper update:

"With labels, you can segment your life and better organize your chats, optionally hiding them from the main view, or simply tag certain people with a label."

Use Case Blocked

I'm building a CLI for inbox triage (read-only). A natural workflow is:

beeper triage --folder personal --needs-reply

"Show me chats in my Personal folder where I haven't replied yet."

Without label/folder exposure, this requires heuristics or manual filtering, which degrades the agent/automation experience.

Request (Read-Only Sufficient)

1. Expose labels on Chat objects

Add fields like:

labels: list[str]  # or list[{"id": str, "name": str}]
# OR
folder: {"id": str, "name": str}  # if single-folder semantics

Include in:

• GET /v0/chats/{id}
• GET /v0/chats (list/search endpoints)

2. Add endpoint to list available labels

GET /v0/labels

Response:

[
  {"id": "abc123", "name": "Personal", "color": "#..."},
  {"id": "def456", "name": "Work", "color": "#..."}
]

3. (Optional) Label-based filtering

GET /v0/chats?label=personal

Or support in search filters.

4. Write support (not needed yet)

Read-only access is sufficient for triage workflows. Write support (assign/remove labels) can come later.

References

• November 2025 Labels Announcement
• Desktop API Reference
• Chat model source

Documentation Request

If labels are intentionally not supported in Desktop API, please document this explicitly in the API reference to prevent developer confusion.

Thank you!