Feature blocks
Three tools, blocks, block_plan and block_add, let the agent find tested ready-made features, preview what a block adds, then copy it into app/ as the app’s own code.
A block is copied into the app, not linked as a library. Once added, the files belong to the app: the agent adapts them to the spec, and manh.run never upgrades or removes a block on its own.
The blocks:
auth: sign-in and roles.resource: table, API, list and detail pages from a field list. Addflowfor a status workflow and a drag-and-drop board,logfor history and notes.attachments(files on records),search(accent-insensitive search),export-excel,numbering(document numbers),notify(notifications).mail(mail templates the owner edits),email-report(scheduled mail reports),ai-extract.ai-assistant(version 3.0): an AI assistant inside the app. It brings the agent fileapp/assistant/assistant.agent.tswith a few example tools to replace with the app’s own, the chat page/assistant(conversation list, tool steps shown as they happen, Duyệt / Từ chối cards before any change to data, a Dừng button) and thin routes overmanh/agent. Apps that copied 2.x keep their files, which keep working; to move to 3.0, delete the old files and add the block again.tasklist: a to-do page for the app’s users: take, give back and finish the human steps of the app’s processes (.bpmn), each with its own form or Duyệt / Từ chối buttons.site: a local business site with facts, opening hours, a lead form and a price list.web: a website in one design direction, with a section kit.
blocks
Finds blocks for a need.
- Parameters:
q: the need in words, for example “audit history” or “upload files”;tags: filter by tag. - Returns: each block’s
id, summary, the blocks it needs (requires), its parameters (params) and a usage snippet. - When the agent calls it: before writing a common feature such as sign-in, CRUD, file attachments or history.
block_plan
Previews adding a block. It writes nothing.
- Parameters:
project;id: the block id fromblocks;params: the block’s parameters. - Returns: the files it would add, required blocks already installed, app files at the same paths (
conflicts), parameter errors and the hookups left (wire). - When the agent calls it: before
block_add, especially in an app that already has many files.
block_add
Adds a block and the blocks it needs.
- Parameters: the same as
block_plan. - Returns: the blocks added, the file list, usage, the hookups left and the check result.
- When the agent calls it: once
block_planreports no conflicts.
Before copying, manh.run saves an automatic copy of the file tree. An app file at the same path with different content is never overwritten: the add stops and reports the conflict. Adding a block does not deploy. Check warns block.unwired until the agent finishes every hookup, such as putting the notification bell in the layout.
Next steps
- Build a CRUD feature: when to use the
resourceblock. - Checkpoints: going back to before a block was added.
- check: the
block.unwiredwarning.