Context7

Developer Tools

Neotask on OpenClaw keeps your agent's library knowledge current through Context7 — resolving package IDs and fetching up-to-date documentation so your agents code with today's APIs, not yesterday's.

What You Can Do

The Context7 integration gives Neotask 2 documentation retrieval actions.

  • `resolve-library-id` — map a library name to its canonical Context7 identifier for use in documentation queries
  • `query-docs` — retrieve current, version-specific documentation for any library from Context7's documentation database

    • Every action runs autonomously or requires your approval — you decide.

    Try Asking

  • "Resolve the Context7 ID for the React Query library"
  • "Fetch the latest documentation for Next.js 15 App Router"
  • "Get the current API docs for Prisma's latest version"
  • "What does the latest Zod documentation say about async validation?"

    • Pro Tips

  • Add Context7 to every code-generating agent workflow: resolve the library ID and fetch docs before generating code to ensure accuracy against the current API
  • When helping engineers with library upgrades, use Context7 to compare documentation between the old and new version — your agent surfaces exactly what changed
  • Pair Context7 with your code review integration so documentation context is automatically surfaced during PR reviews that introduce new dependencies
  • In multi-agent coding teams, dedicate a research agent to Context7 lookups while implementation agents focus on writing code — no waiting for documentation

    • Works Well With