@anchrd/intel-ui 0.8.8 → 0.9.1

package/src/router/router.tsx

@@ -13,13 +13,13 @@ const rootRoute = createRootRouteWithContext<RouterContext>()({ component: App }
 const redirectRoute = createRoute({
   getParentRoute: () => rootRoute,
   path: "/",
-  component: () => <Navigate to="/knowledge" replace />,
+  component: () => <Navigate to="/nodes" replace />,
 });
-const knowledgeRoute = createRoute({
+const nodesRoute = createRoute({
   getParentRoute: () => rootRoute,
-  path: "/knowledge",
+  path: "/nodes",
   validateSearch: selectionSearch,
-  component: lazyRouteComponent(() => import("@/knowledge/knowledge.tsx"), "Knowledge"),
+  component: lazyRouteComponent(() => import("@/nodes/nodes.tsx"), "Nodes"),
 });
 const flowsRoute = createRoute({
   getParentRoute: () => rootRoute,
@@ -41,7 +41,7 @@ const toolsRoute = createRoute({
 });
 const routeTree = rootRoute.addChildren([
   redirectRoute,
-  knowledgeRoute,
+  nodesRoute,
   flowsRoute,
   toolsRoute,
   archiveRoute,

package/src/title-row/title-row.tsx

@@ -20,21 +20,35 @@ export function TitleRow({
   title,
   description,
   target,
+  leading,
+  divider = true,
   children,
 }: {
   title: string;
   description?: string | null;
   target: ResourceTarget;
+  // ⚠️ A picture before the name, for the one kind that has a face: an agent's initials (#143). A
+  // prop rather than another slot because it must sit BEFORE the title, and a portal can only
+  // append — the same limitation that gave the shell two boxes instead of one list (#56).
+  leading?: React.ReactNode;
+  // Off for the one kind whose next line is its own tab bar: two rules a few pixels apart read as
+  // clutter, so the agent page keeps only the tab bar's (#204).
+  divider?: boolean;
   children?: React.ReactNode;
 }) {
   return (
-    <div className="flex items-start justify-between gap-5 border-b px-6 py-4">
-      <div className="min-w-0">
-        <div className="flex min-w-0 items-baseline gap-3">
-          <h2 className="truncate text-lg font-semibold">{title}</h2>
-          <span data-slot="title-meta" className="shrink-0 text-sm text-muted-foreground" />
+    <div
+      className={`flex items-start justify-between gap-5 px-6 py-4${divider ? " border-b" : ""}`}
+    >
+      <div className="flex min-w-0 items-center gap-3">
+        {leading}
+        <div className="min-w-0">
+          <div className="flex min-w-0 flex-wrap items-baseline gap-x-3">
+            <h2 className="truncate text-lg font-semibold">{title}</h2>
+            <span data-slot="title-meta" className="text-sm text-muted-foreground" />
+          </div>
+          {description ? <p className="mt-1 text-sm text-muted-foreground">{description}</p> : null}
         </div>
-        {description ? <p className="mt-1 text-sm text-muted-foreground">{description}</p> : null}
       </div>
       {/* ⚠️ Document order is tab order here — nothing carries a `tabIndex`. The menu is therefore
           reached last by the keyboard for the same reason it stands last on screen, and the two

package/vite.config.ts

@@ -12,6 +12,10 @@ export default defineConfig({
       "/auth": { target: "http://localhost:8788", changeOrigin: true },
       "/mcp": { target: "http://localhost:8788", changeOrigin: true },
       "/.well-known": { target: "http://localhost:8788", changeOrigin: true },
+      // ⚠️ There is deliberately no `/agents` entry any more (#178). The browser reaches the agent
+      // runtime through intel, which forwards over its `AGENT` service binding — so in development
+      // the runtime still has to be running (`workers/agent`, port 8789, started separately from
+      // `bun run dev`), but Vite proxies nothing to it: wrangler's dev registry connects the two.
     },
   },
 });