/iblai-vibe-agent-search
First time here? If
iblai.envhas noARCHITECTURE=, run/iblai-vibe-startfirst (four questions; two minutes) — it decides single-org / multi-org / headless and who signs in, and every skill reads the answer.
Add an Agent Search page -- a searchable, filterable agent browser with four sections: starred agents, featured agents, custom agents, and all agents. Includes search input, category/subject/LLM/type filters, star/favorite toggle, and "Create Agent" action.
Common setup (brand, conventions, env files, verification): see docs/skill-setup.md.
Prerequisites
- Auth must be set up first (
/iblai-vibe-auth) - MCP server + skills configured (
@iblai/mcpin.mcp.json)
Step 1: Check Environment
Before proceeding, check for an iblai.env in the project root. Look for
PLATFORM, DOMAIN, and TOKEN variables. If the file does not exist or
is missing these variables, tell the user:
"You need an iblai.env with your platform configuration. Download the
template and fill in your values:
curl -o iblai.env https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/iblai.env"
Step 2: Mount AgentSearch
AgentSearch does NOT use AgentSettingsProvider. It takes tenantKey,
username, and onAgentClick as direct props.
// app/(app)/agents/page.tsx
"use client";
import { useEffect, useState } from "react";
import { useRouter } from "next/navigation";
import { AgentSearch } from "@iblai/iblai-js/web-containers/next";
export default function AgentsPage() {
const router = useRouter();
const [tenantKey, setTenantKey] = useState("");
const [username, setUsername] = useState<string | null>(null);
useEffect(() => {
try {
const raw = localStorage.getItem("userData");
if (raw) {
const parsed = JSON.parse(raw);
setUsername(parsed.user_nicename ?? parsed.username ?? "");
}
const resolvedTenant =
localStorage.getItem("app_tenant") ??
(() => {
try {
return JSON.parse(localStorage.getItem("current_tenant") ?? "{}").key;
} catch { return undefined; }
})() ??
localStorage.getItem("tenant") ??
"";
setTenantKey(resolvedTenant);
} catch {}
}, []);
if (!tenantKey) return null;
return (
<div className="flex h-full flex-col bg-white p-4">
<AgentSearch
tenantKey={tenantKey}
username={username}
=> {
router.push(`/agents/${agent.unique_id}/settings`);
}}
=> {
router.push("/agents/new");
}}
/>
</div>
);
}
Limiting visible sections
By default all four sections render (starred, featured, custom, default).
Use the include prop to show only specific sections:
<AgentSearch
tenantKey={tenantKey}
username={username}
include={["featured", "default"]}
/>
Step 3: Customize Labels (Optional)
import { AgentSearch } from "@iblai/iblai-js/web-containers/next";
<AgentSearch
tenantKey={tenantKey}
username={username}
labels={{
sections: {
starred: { title: "Your favorites" },
featured: { title: "Recommended mentors" },
},
}}
/>;
Step 4: Use MCP Tools for Customization
get_component_info("AgentSearch")
get_component_info("AgentCard")
get_hook_info("useAgentSearch")
<AgentSearch> Props
Import from @iblai/iblai-js/web-containers/next.
| Prop | Type | Required | Description |
|---|---|---|---|
tenantKey |
string |
Yes | Current platform key |
username |
string | null |
Yes | Current user (null = unauthenticated) |
onAgentClick |
(agent: AgentSearchResult) => void |
Yes | Called when an agent card is clicked |
onCreateAgent |
() => void |
No | Called when "Create Agent" is clicked. Hides button if omitted |
onUnauthenticatedAction |
() => void |
No | Called when an unauthenticated user tries a protected action |
enableRBAC |
boolean |
No | Toggle RBAC gating (default: false) |
rbacPermissions |
object |
No | RBAC permissions object |
executeGatedAction |
(fn: () => unknown) => unknown |
No | Gate callback when enableRBAC is true |
createAgentRbacResource |
string |
No | RBAC resource for create (default: /mentors/#create) |
mainTenantKey |
string |
No | Main organization key (default: "main") |
labels |
DeepPartial<AgentSearchLabels> |
No | Override user-visible strings |
include |
AgentSearchSection[] |
No | Sections to show (default: all) |
getLLMProviderName |
(providerKey: string) => string |
No | Map provider key to display name in filters |
Sub-Components
All importable from @iblai/iblai-js/web-containers/next for custom
layouts:
| Component | Description |
|---|---|
AgentCard |
Single agent card with avatar, name, description, date |
AgentSearchInput |
Search text field with icon |
AgentSearchFilters |
Category/subject/LLM/type filter dropdowns |
StarButton |
Favorite toggle star icon |
AgentEmptyState |
"No agents found" placeholder |
Hooks
From @iblai/iblai-js/web-containers/next:
| Hook | Description |
|---|---|
useAgentSearch |
Core search hook wrapping the AI search API |
useAgentSearchWithPagination |
Search with load-more pagination |
useAgentStar |
Star/unstar mutation hooks |
Related Exports
From @iblai/iblai-js/web-containers/next:
AGENT_SEARCH_LABELS-- default label bundle for AgentSearch.AGENT_PICKER_LABELS-- default label bundle for a picker variant.resolveAgentSearchLabels-- deep-merge helper for labels.formatDateString-- default date formatter used by AgentCard.AgentSearchResult-- type for a single agent result.
Step 5: Verify
Run /iblai-vibe-ops-test before telling the user the work is ready:
pnpm build-- must pass with zero errorspnpm test-- vitest must pass- Start dev server and touch test:
pnpm dev & npx playwright screenshot http://localhost:3000/agents /tmp/agent-search.png
Important Notes
- Redux store: Must include
mentorReducerandmentorMiddleware initializeDataLayer(): 5 args (v1.2+)@reduxjs/toolkit: Deduplicated via webpack aliases innext.config.ts- Peer deps:
sonnerand@iblai/iblai-web-mentormust be installed (pnpm add sonner @iblai/iblai-web-mentor) - No AgentSettingsProvider: Unlike the tab components,
AgentSearchtakes identity props directly. Do NOT wrap it inAgentSettingsProvider. - Starred agents: Require an authenticated user (
username !== null). Whenusernameis null, the starred section is hidden. - Brand guidelines: BRAND.md