@dudousxd/nestjs-agent-codegen

The agent's controllers live in node_modules, where @dudousxd/nestjs-codegen's static AST discovery can't see them. This extension injects the JSON REST routes directly — the agents catalog, threads (incl. rename/promote/fork/truncate), tool-call approve/reject/answer/skip, skills, tools, memories, staged attachments, message feedback, the model catalog, quota, client config, the message queue and cancel — so they show up in your unified generated client. A spec in the package (covers-every-json-route.spec.ts) reads the library's controllers off disk and fails when a JSON route there is missing from the injected list.

pnpm add -D @dudousxd/nestjs-agent-codegen @dudousxd/nestjs-codegen

Minimal exampleCopy Anchor Link

// codegen.config.ts
import { defineConfig } from '@dudousxd/nestjs-codegen';
import { nestjsAgentCodegen } from '@dudousxd/nestjs-agent-codegen';

export default defineConfig({
  extensions: [nestjsAgentCodegen({ basePath: '/api' })],
});

// generated client usage — plain fetch always works:
import { api } from '../lib/api';

const threads = await api.agent.threads.list();
await api.agent.toolCall.approve({ body: { toolCallId } });

With the @dudousxd/nestjs-codegen-tanstack extension registered, each call also returns a handle with .queryOptions() / .mutationOptions():

import { useQuery, useMutation } from '@tanstack/react-query';

const threads = useQuery(api.agent.threads.list().queryOptions());
const approve = useMutation(api.agent.toolCall.approve().mutationOptions());

ExportsCopy Anchor Link

Routes it injectsCopy Anchor Link

Response and body types are hand-mirrored from @dudousxd/nestjs-agent-core (dates are ISO strings); deeply nested tool-call payloads are typed loosely as Record<string, unknown>[].

Peer dependenciesCopy Anchor Link

@dudousxd/nestjs-codegen (>=0.2.0).

When to use itCopy Anchor Link

Add this extension once your frontend already consumes a @dudousxd/nestjs-codegen-generated client and you want the agent's thread/quota/approval surface typed the same way as the rest of your API — rather than hand-writing a client against those routes.

RelatedCopy Anchor Link

• Frontend — useAgentChat, the streaming transport, and where the generated client fits alongside it
• Codegen docs — the extension mechanism and the unified api.ts output