
Setup Agent Tail
Auto-configure agent-tail log aggregation for AI-powered development
What You Can Do
This skill detects your project framework (Vite, Next.js, plain Node, or monorepo) and automatically configures agent-tail to pipe dev server and browser console logs into unified log files. You'll get a proposed configuration tailored to your setup, install agent-tail with the correct plugins, and have logs immediately available for AI agents to consume and analyze.
Features
identifies Vite, Next.js, Node, and monorepo structures from package.json and config files
installs and configures the correct browser log capture plugins for your framework
generates npm scripts and shell commands to pipe logs to agent-tail's standard output directory
detects monorepo tools (Turbo, Nx, pnpm, Lerna) and sets up agent-tail-core at root with package-level wrappers
automatically adds tmp/ to .gitignore to prevent log files from version control
proposes the full configuration and waits for approval before making any changes
routes all logs (dev server, browser console, errors) to tmp/logs/latest/ for agent consumption
Example Output
Example 1: Vite Project Detection
✓ Detected: Vite project with React
✓ Browser logs: vite-plugin-agent-tail
✓ Dev server logs: piped via CLI
✓ Output: tmp/logs/latest/
✓ npm script added: "dev:logs"
Example 2: Next.js Setup
✓ Detected: Next.js with App Router
✓ Browser plugin: next-agent-tail
✓ Server logs: piped automatically
✓ Output location: tmp/logs/latest/
✓ .gitignore updated
Example 3: Monorepo Configuration
✓ Detected: Turbo monorepo with 3 packages
✓ Root init: agent-tail-core init
✓ Package wrappers: agent-tail-core wrap (applied to all packages)
✓ Log aggregation: tmp/logs/latest/
What's Included
- SKILL.md: Complete agent-tail setup workflow and configuration logic
- Framework detection templates: Vite, Next.js, Node, and monorepo detection patterns
- Configuration proposer: Pre-filled setup options based on detected framework
- Plugin installation checklist: Browser log capture and CLI runner setup steps
- Post-setup verification: Validation that logs are flowing to tmp/logs/latest/ correctly
Who It's For
- AI/Prompt engineers — building agents that need to read dev server and browser logs
- Full-stack developers — debugging multi-layer applications with unified log visibility
- DevOps engineers — setting up centralized logging for dev environments
- Engineering teams using AI coding agents — configuring agent-accessible log streams
- Framework-agnostic developers — working across Vite, Next.js, and monorepo projects
Best For
- Initial agent-tail setup for a new project
- Adding AI-readable logging to existing dev workflows
- Configuring monorepo log aggregation
- Automating log pipeline configuration across multiple projects
- Debugging AI agent decisions with full application log context







