feat(dashboard): bring new tabs back

[jog1t]

Description

This change adds new tabs to the actor details interface, specifically adding Queue, Workflow, and Database tabs alongside the existing tabs. The implementation includes both the tab triggers in the navigation and their corresponding content components. Additionally, an unused import for useQuery from @tanstack/react-query and the ActorTracesTab import have been removed.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-4249 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
frontend-inspector	😴 Sleeping (View Logs)	Web	Feb 23, 2026 at 11:17 pm
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 23, 2026 at 11:08 pm
ladle	❌ Build Failed (View Logs)	Web	Feb 23, 2026 at 11:06 pm
website	❌ Build Failed (View Logs)	Web	Feb 20, 2026 at 10:31 pm
mcp-hub	✅ Success (View Logs)	Web	Feb 20, 2026 at 10:31 pm

[jog1t]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• chore: multiplayer cookbook #4200 : 2 dependent PRs (#4201 , #4253 )
• feat(dashboard): bring new tabs back #4249 👈 (View in Graphite)
• fix(rivetkit): fix sqlite teardown logic #4259
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: feat(dashboard): bring new tabs back

Overall: The PR is simple and mostly correct, but has one clear bug and a minor structural issue worth addressing.

---

Bug: Database tab content is unreachable

A TabsContent block is added for value="database" (rendering <ActorDatabaseTab>) but no corresponding TabsTrigger with value="database" was added to the TabsList. The existing triggers in the nav bar are: State, Connections, Queue, Workflow, Metadata — Database is absent. This means the Database tab is completely inaccessible in the UI despite the content being wired up.

// This was added — but there's no TabsTrigger for "database"
<TabsContent
    value="database"
    className="min-h-0 min-w-0 flex-1 mt-0 h-full"
>
    {guardContent || <ActorDatabaseTab actorId={actorId} />}
</TabsContent>

A trigger like the following is missing from the TabsList:

<TabsTrigger
    disabled={disabled}
    value="database"
    className="text-xs px-3 py-1 pb-2"
>
    Database
</TabsTrigger>

---

Minor: Logs tab also lacks a trigger (pre-existing)

Not introduced by this PR, but worth noting: there's also a TabsContent for value="logs" with no matching trigger in the current nav. If logs are intentionally hidden, the content block should be removed too; if not, the trigger is missing. This PR would be a good opportunity to fix both gaps.

---

Positives

• Removing the unused useQuery and ActorTracesTab imports is a clean-up.
• The queue and workflow tab wiring (trigger + content) looks correct and consistent with the existing connections tab pattern.
• The individual tab components (ActorQueueTab, ActorWorkflowTab, ActorDatabaseTab) each handle their own loading/disabled/error states properly.

[graphite-app]

Graphite Automations

"Test" took an action on this PR • (02/20/26)

1 assignee was added to this PR based on Kacper Wojciechowski's automation.

[graphite-app]

Merge activity

• Feb 24, 3:21 AM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Feb 24, 3:22 AM UTC: CI is running for this pull request on a draft pull request (#4274) due to your merge queue CI optimization settings.
• Feb 24, 3:23 AM UTC: Merged by the Graphite merge queue via draft PR: #4274.