Search & Activity

​

Global search

Global search lets you find any entity in your workspace without navigating to a specific screen. It searches across issues, patterns, predictions, recommendations, and members simultaneously.

​

Opening search

Click the search icon in the top bar (present on every screen that renders the Topbar component) or use the keyboard shortcut to open the Command Palette. Start typing and results appear immediately.

​

Typeahead suggestions

As you type, the Command Palette surfaces up to 8 typeahead suggestions via GET /v1/search/suggest?q={query}. Suggestions are scoped to entity types your token has access to: Each suggestion includes the entity name, type badge, and a direct link. Selecting a suggestion navigates immediately to the entity detail page.

​

Full search

Press Enter (or click Search) to run a full federated search via GET /v1/search.

​

Query parameters

If you omit types, all entity types you have scope for are searched. If you specify an unknown type explicitly, the API returns a 400 validation_error.

​

Search results

Results are grouped by entity type. Each result item includes:

• Type — the entity type
• ID — the entity ID
• Title / name — the display text
• Link — the in-app URL for that entity
• Snippet — a short excerpt showing where the query matched

​

Activity feed

The Activity feed is a chronological log of everything that has happened in your workspace — issues ingested, patterns detected, analyses completed, recommendations generated, and more.

​

Viewing the activity feed

The activity feed appears in a few places:

1. Dashboard — the Live activity panel on the lower half of the Dashboard shows the most recent events in real time, streaming via WebSocket, backed by GET /v1/dashboard/activity (or its simpler alias GET /v1/dashboard/recent-activity).
2. Workspace Activity API — GET /v1/activity is the full workspace feed: it unions the recorded-activity store with a humanized projection of the append-only event log, so it shows everything that actually happened, not just the handful of call sites that write a dedicated activity row. High-cardinality machine bookkeeping (field_updated, criticality.computed, loop.assigned) is filtered out of the human feed — it stays fully visible per-entity via GET /issues/{id}/events and the workspace event log.

​

Activity event fields

Each activity event contains:

​

Filtering the feed

GET /v1/activity accepts: GET /v1/dashboard/activity (the simpler Dashboard-panel alias) accepts type, since, limit, and cursor.

​

Event types

Event types you will see in the feed include: An event type with no dedicated human-message mapping still appears — it falls back to the raw type, humanized (. and _ replaced with spaces).

​

Related pages