NexAgent AI
Vancouver local team online
Before we start
Leave your contact — our AI consultant answers right away, and a human can follow up when needed.
When the strongest model coordinates and smaller workers execute modules, use hooks plus self-reports to record who did what, which tools were used, and which token counts are exact or estimated.
6
Demo Events
3
Worker Reports
1,238
Exact Tokens
Bilingual
Owner Report
Submit a lightweight form to download the PDF, lecture notes, research notes, and demo screenshot.
To share materials with interested learners, leave your basic info and topics first. The file opens automatically after submission.
From opaque delegation to a working audit plugin and owner report.
Goal delegation, coordinator models, workers, and owner opacity
Shared schema vs Codex/Claude-specific integration
Hooks, self-reports, owner reports, and viewer
Role, module, model, tools, files, completed work, blockers, tokens
Import NDJSON and inspect owner summary and cost visibility
Claude hooks, cross-machine install, HTML/PDF reports
Agent Task Audit is not a hidden-routing decoder. It is a ledger and handoff sheet for multi-agent work.
Automatic facts
Capture lifecycle events, tool calls, approval requests, and visible usage fields.
Worker accountability
Each worker reports role, module, tools, files, completed work, blockers, and tokens.
Readable accountability
Explain who did what, where cost is visible, and what remains opaque in English and Chinese.
Every report should answer: 1. Who owned which modules? 2. Which model information was visible? 3. Which token counts were exact? 4. Which token counts were estimated or self-reported? 5. Which tools, commands, and files were used? 6. Were there failures, blockers, or unknowns?
| Time | Duration | Module | Mode |
|---|---|---|---|
| 00:00–10:00 | 10 min | The multi-agent opacity problem | Explain |
| 10:00–20:00 | 10 min | Generality and visibility limits | Clarify |
| 20:00–35:00 | 15 min | Plugin architecture and self-report protocol | Breakdown |
| 35:00–50:00 | 15 min | Demo viewer | Practice |
| 50:00–60:00 | 10 min | Productization roadmap | Discuss |
For people using Codex/Claude in real delivery, development, research, and operations workflows.
The schema, self-report protocol, and owner report are general. Codex plugin installation and hook paths are platform and machine specific. Claude needs Claude Code hooks or a wrapper to write the same log format.
Only token counts exposed by the runtime are exact. Everything else is labeled estimated or unknown.
The main agent may not see every internal detail. Self-reports bring module ownership, deliverables, risks, and estimated cost back to the owner.
We can help turn Codex/Claude multi-agent workflows into recorded, reviewable, owner-readable audit loops.