Documentation
Copy for a coding agent is the fastest way to give a coding assistant the exact implementation context for a Block. This is not the same as installing a Skill. Skills are installable playbooks; this action copies Block implementation files as AI-ready context.
For verified Blocks, the menu can copy either Next.js implementation files or a standalone Hono API server.
Choose a target
| Target | What is copied |
|---|---|
| Next.js | Curated files selected from meta.criticalFilesToCopy |
| Hono API server | AI-friendly Markdown from the verified, runnable Hono server bundle |
The Hono payload includes server source and configuration, but no React UI or Next.js application shell. See Export a Block for the complete workflow.
What is copied for Next.js
The feature reads meta.criticalFilesToCopy for a Block and only includes files that matter most for changes:
- core AI logic
- orchestration and routing files
- tool definitions and schemas
- key UI integration files
Each selected file also includes an instructionsForAI note so the assistant knows what to focus on.
Output format
The copied payload is structured markdown:
- Block title and description
## Implementation files- For each file:
### <path>- a short instruction block
- a fenced code block with full file content
This format works well in Cursor, Claude Code, Codex, and other coding agents.
Hono uses the same Markdown-oriented approach, but its file set comes from the standalone server export rather than meta.criticalFilesToCopy.
How to use it effectively
- Open a Block page.
- Click
Copy for a coding agent. - Choose Next.js or Hono API server when both are available.
- Paste into your coding agent.
- Ask for a scoped change, for example:
- "Refactor tool execution error handling only."
- "Add approval before the destructive tool runs."
Related
ai sdk blocks.