The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agents-api	Ready	Preview, Comment	Apr 1, 2026 2:12pm
agents-docs	Ready	Preview, Comment	Apr 1, 2026 2:12pm
agents-manage-ui	Ready	Preview, Comment	Apr 1, 2026 2:12pm

🦋 Changeset detected

Latest commit: b0192f0

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@claude add a changeset

Claude finished @dimaMachina's task in 51s —— View job

Adding changeset

• Analyze PR changes
• Create changeset

Added a patch changeset for @inkeep/agents-manage-ui: "Reuse existing TanStack Query hooks for project fetching instead of manual fetch calls"

Pushed in commit b0192f0.
|

TL;DR — Replaces ad-hoc fetchProjects calls in three manage-UI pages with the shared useProjectsQuery TanStack Query hook, eliminating duplicate fetches and local state for the projects list.

Key changes

• Replace manual project fetching with useProjectsQuery in billing page — Drops the projectCount state and fetchProjects call from the Promise.all, using the cached query result instead.
• Replace manual project fetching with useProjectsQuery in cost page — Removes the useEffect + useState pair for projects in favor of the shared query hook.
• Replace manual project fetching with useProjectsQuery in ProjectAccessDialog — Decouples project loading from membership loading, renames loading → loadingMemberships for clarity, and derives combined loading state.
• Remove useProjectActions from Biome stable-result list — Cleans up an entry that is no longer needed.
• Add changeset for @inkeep/agents-manage-ui — Patch-level changeset documenting the hook reuse.

_{Summary ｜ 5 files ｜ 5 commits ｜ base: main ← reuse-existing-tanstack-queries}

Shared useProjectsQuery hook replaces imperative fetches

Before: Each page independently called fetchProjects(tenantId) inside useEffect or Promise.all, storing results in local useState. Multiple pages mounting simultaneously would fire separate network requests for the same data.
After: All three consumers use the existing useProjectsQuery hook backed by TanStack Query, so projects are fetched once and shared across components via the query cache.

In ProjectAccessDialog, the enabled: open option ensures the query only fires when the dialog is visible. The previously monolithic loading state is split: isProjectsFetching tracks the query, while loadingMemberships tracks the membership API call. A derived loading combines both before render.

billing/page.tsx · cost/page.tsx · project-access-dialog.tsx · biome.jsonc

  ^{｜ View workflow run ｜ Triggered by Pullfrog ｜ Using Claude Opus ｜ 𝕏}