1
Send to the shared area
When one item or a multi-selection is active, the shared-area button can copy the selected part from the workspace, group, true/false action branch, dialog, and variables surfaces into the device-local library.
No-Code Workspace — Block Reference
Data and UtilitiesBlock usage recipe
Clipboard Write (CLIPBOARD_WRITE)
Writes text into the system clipboard
Documented for app version 1.0.50Updated:
Block Preview
Captured from the in-app Visual Builder block card in the English UI.
English UI
What Does It Do?
Writes a fixed string or variable-driven text template into the device clipboard. Ideal when your flow needs to prepare text for another app or later paste operations.
When to Use?
1
Use it when you need to:
2
Prepare a URL, command, verification code, or canned message
3
Combine multiple variables into one clipboard value
4
Leave paste-ready content for the user or the next automated step
How to Use?
1
Add the CLIPBOARD_WRITE block
2
Enter fixed text or a {{ variable }} template, or bind the field with the lightbulb
3
Prepare the final text first with STRING_OP / JSON_PARSE when needed
4
Continue with the paste flow in the target app or step
Parameters
Text to Write
Fixed text, a {{ variable }} template, or a variable bound with the lightbulb
| Parameter | Description |
|---|---|
| Text to Write | Fixed text, a {{ variable }} template, or a variable bound with the lightbulb |
Example Usage
1
Scenario: Prepare an order summary in the clipboard
2
Build the message with STRING_OP or SET_VARIABLE
3
Use CLIPBOARD_WRITE to put it in the clipboard
4
Move to the target app with PANEL_CONTROL or SYSTEM
5
The user or next step pastes it
Combinations / Used With
1
COMBINATIONS:
2
SET_VARIABLE + CLIPBOARD_WRITE: compose a reusable message
3
JSON_PARSE + CLIPBOARD_WRITE: turn API output into pasteable text
4
CLIPBOARD_WRITE + SYSTEM: jump to the destination app
Tip
For long text, compose the final value first in a variable, then write it to the clipboard in one step.
Warnings / Cautions
1
WARNING:
2
The clipboard is device-wide; other apps may also access it
3
If the value is sensitive, overwrite it later instead of leaving it indefinitely
Step-by-Step Mastery: Basic → Advanced → Pro
The same block at three levels: a quick start, the real options, and professional techniques.
Basic
CLIPBOARD_WRITE writes the text you provide into the device clipboard. Its only setting is Text to Write, which can be fixed text, a {{ variable }} template, or a variable bound with the lightbulb. Use it to prepare data (a URL, command, code, canned message) that the user or the next step will paste into another app.
Advanced
The generated code calls Clipboard.copy("text"). Embed {{ variable }} templates in the Text to Write field to combine several variables into one clipboard value. For long or multi-part text, it is tidier to compose it first in a variable with SET_VARIABLE/STRING_OP/JSON_PARSE, then write it in one step. The clipboard is DEVICE-WIDE: other apps can read the value you write, so do not leave sensitive content sitting on the clipboard.
Pro
Paste-ready pipeline: compose the value (SET_VARIABLE/STRING_OP), write it with CLIPBOARD_WRITE, switch to the target app with SYSTEM/PANEL_CONTROL, then let the user or next step paste. Turning JSON_PARSE output into a copyable summary is a fast way to share an API result. For privacy, clear the clipboard at the end of the flow — e.g. overwrite the sensitive content with neutral text via a final CLIPBOARD_WRITE. Because the clipboard is device-wide, in environments where automation races (like a clipboard manager) a small WAIT buffer between write and paste improves reliability.
Real-World Scenarios — Step-by-Step Recipes
Small, reproducible examples that combine several blocks — build them straight into your own macro.
Prepare an order summary in the clipboard
- 1SET_VARIABLE: summary = "Order #" .. orderId .. " ready"
- 2CLIPBOARD_WRITE → text field bound to summary with the lightbulb
- 3SYSTEM → open the target app
- 4The user or next step pastes
Turn an API result into pasteable text
- 1HTTP_GET → response=resp
- 2JSON_PARSE → read a field from resp → status
- 3CLIPBOARD_WRITE → text="Status: {{status}}"
Which Blocks to Pair With — Pro Combinations
This block is useful on its own — but it shines when paired with the right partners.
+ SET_VARIABLE
Composes a multi-part message in a variable first, then writes that one variable, bound with the lightbulb, to the clipboard.
+ JSON_PARSE
Turns a field extracted from an API response into a copyable summary.
+ SYSTEM
After writing to the clipboard, jumps to the destination app to begin the paste flow.
+ CLIPBOARD_READ
Completes the read → process → write-back pipeline, and overwrites sensitive content at the end of the flow.
Common Mistakes and Fixes
Leaving sensitive content on the clipboard. The clipboard is device-wide; OTPs/passwords can be read by other apps. Fix: overwrite it with neutral text via CLIPBOARD_WRITE at the end of the flow.
Trying to build long text with multiple write blocks. CLIPBOARD_WRITE overwrites the clipboard each call, losing the previous part. Fix: combine the whole text in one variable first, then write once.
Chaining write and paste too fast. In some environments the clipboard update can lag. Fix: insert a small WAIT in between if needed.
Pro Tips
Use {{ variable }} placeholders in the text field; Lua concatenation written outside a template ("a" .. b) is not evaluated and is copied as plain text.
Clearing the clipboard with a final neutral write in canned-message/command flows prevents you from accidentally clobbering the user's next copy.
This Block's Code (Editor View)
LuaThe Lua below is what the Code Editor generates for this block with sample settings. Adding cases, branches, actions or loops, or changing settings, extends the generated code accordingly. Study it to see what the block does under the hood, to learn Lua, or to copy and adapt it. Use the Copy button (top-right) to paste it into the Code Editor, or “Try in Editor →” to run it in the live editor.
Clipboard.copy("text")Note: generated code can evolve across versions; helper names (e.g. _reg1, m1) and internal optimizations may change. The logic and the called APIs reflect the block’s behavior.
Shared Controls for This Block Family
The guidance below is not identical for every block. It summarizes the professional controls that most often repeat in the selected block family.
🗃Source and Destination
Use file paths, key names, regex sources, and JSON paths with clear naming discipline.
🧷Default Value
Define default outputs clearly so the builder flow does not collapse when data is missing.
🔄Write Then Read Back
For KV or file writes, verifying the result in the next block is healthier in production-grade flows.
🪶Narrow Output Design
Instead of carrying large raw payloads, extract the value you need and pass it forward via a result variable.
Builder vs Lua Boundary
Raw touch pointer lifecycle stays code-first
TOUCH and TOUCH_BREAK cover recipe-style touch flows. Raw pointer choreography such as Touch.down, Touch.move, Touch.up, Touch.dispatch, Touch.reset, Touch.breakAll, and Touch.releaseAfter is not exposed as a first-class builder block.
Touch.downTouch.moveTouch.upTouch.dispatchTouch.resetTouch.breakAllTouch.releaseAfterBounded dialog design is builder-backed; freer composition stays code-first
The DIALOG block and dialog designer cover a bounded field set in the builder: Info Text, Text Input, Checkbox, Description, Radio Group, Dropdown, Multi Select, Tab Group, Date Time, Number Range, Slider, Image Picker, Color Picker, File Picker, Recorder Picker, Tag, Signature, and Spacer. The buttons are designed too: the Positive button and Negative button tabs set each button’s text, background, and border color, corner radius, and minimum height next to a preview. Freer Setting.builder composition, multi-step wizard flows, and mixed HUD/dialog choreography still do not map 1:1 into the builder.
Coming soonv1.0.51Two more fields: Agent Detect references (agent_detect_editor) lets the user pick a saved reference set or add and edit references, and Save confirms the selection; Navigation setup editor (navigation_editor) edits a saved map, marker and route from the Dialog and returns the setup and route selection without moving the character.
Setting.builderDialogHudTextViewAgentDetectEditorNavigationEditorAdvanced HTTP request chaining stays code-first
HTTP_GET, HTTP_POST, and HTTP_PUT cover common fixed-method flows; HTTP_REQUEST covers one bounded request with method, header lines, body, content type, query parameters (GET and DELETE), timeout, and a bounded retry. These blocks never throw; they write the status code (-1 on a network failure). Cookie handling, chained request objects, and lower-level client flows still need the code editor.
Request()Request.setCookieRequest.getCookiesCUSTOM_CODEGeneral programming surfaces stay code-first
The MAP, LIST, JSON_PARSE, REGEX_MATCH, and METRICS blocks cover the everyday cases: map actions, a static list, reading a value from a JSON path, regex match, find, replace, and split, and metrics actions. The rest of the Map, Array, JSON, Regex, and Metrics APIs (for example Array sort, filter, and map) is broader than the builder recipe model and stays on the CUSTOM_CODE and code editor side.
MapArrayJSONRegexMetricsLow-level runtime and Lua composition stays code-first
Runtime helpers, raw Request objects, Lua built-ins such as print/pcall/xpcall, and free-form object chaining patterns are represented through CUSTOM_CODE or the code editor.
RuntimeRequestprintpcallxpcallCUSTOM_CODEDebug Mode and Breakpoints
Each block card now exposes an independent breakpoint toggle. When enabled, the breakpoint preference is stored with the block.
Breakpoints are only emitted into runtime code when Debug Mode is enabled from Visual Builder settings. When Debug Mode is off, breakpoints stay saved but do not pause execution.
Use ASSERT for fail-fast validation, and use breakpoints for step-by-step tracing and controlled pauses in the same flow.
Variable Scope
1
Variables defined with SET_VARIABLE are accessible throughout the macro (global scope). All blocks can read/write the same variable.
2
However, a variable defined inside a GROUP will be 'nil' (undefined) until the GROUP executes. Blocks outside the GROUP using this variable may produce unexpected results.
3
FOR_EACH loop variables (item and index) only carry valid values inside the loop body. Outside the loop they are outside local scope and should not be used.
4
TRY_CATCH error variable is only valid within the catch block. If the try block succeeds, the catch branch is not entered and the error variable remains undefined.
5
TIP: Before using a variable inside a GROUP, assign a default value with SET_VARIABLE outside the GROUP. This way the variable won't be nil even if the GROUP has not run.
Inline Expressions
You can embed variable values and calculations into text fields using {{ expression }} syntax. Expressions inside double curly braces are evaluated as Lua code and the result is inserted into the text.
Syntax
{{ expression }}Examples
Skor: {{ score + 1 }} → "Skor: " .. tostring(score + 1){{ name }} kazandı! → tostring(name) .. " kazandı!"X:{{ x }} Y:{{ y }} → "X:" .. tostring(x) .. " Y:" .. tostring(y)Supported Blocks
SET_VARIABLELOGCOMPARECLIPBOARD_WRITENOTIFY_TOASTKV_SET
Security Note
Expressions are checked by the sandbox policy. Security-sensitive calls like loadstring, require, debug are automatically blocked.
General Tips
1
Keep scan regions as small as possible — improves speed, reduces false matches.
2
Always add an exit condition when using infinite loops (BREAK, timeout, or conditional exit).
3
Use network operations and error-prone steps inside TRY_CATCH.
4
If you need global error handling, use the Error Handler (ERROR_HANDLER) block as a singleton in the project.
5
Small coordinate offsets (CLICK/SWIPE) improve tap accuracy across different DPI and screen scales.
6
Customize macros with Dialog block — different parameters each run.
7
Define repeating steps once with GROUP_CALL, call from many places.
Cross-macro local library
Local Shared Macro Area
The Local Shared Macro Area moves blocks, variables, dialog fields, gallery assets, and imported media dependencies between macros on the same device. It is device-local, not cloud sync, not Firebase sharing, and not a replacement for public macro sharing.
Professional usage model: put a reusable login flow, common scan region, shared dialog form, variable group, template image, color profile, replay recording, or imported PLAY_SOUND media file into the shared area from one macro, then import it from the relevant + menu in another macro.
VISUAL_BLOCKSVARIABLESDIALOG_FIELDSTEMPLATE_IMAGECOLOR_SWATCHREPLAY_RECORDMEDIA_FILE2
Import into another macro
The shared-area entry under the + menu imports the selected item into the surface that opened it. Main workspace, group, action branch, dialog, and variables each receive the compatible item type.
3
Share gallery assets
Gallery items include template images, color swatches, replay records, and imported audio/media files. They can move between macros on the same device so repeated templates, colors, recordings, and PLAY_SOUND media assets do not need to be captured again.
4
Keep it clean
The shared area is not a permanent dumping ground. Delete stale shared items from the shared-library panel; imports create a copy in the target macro and do not rewrite the source macro flow.
Checkpoint: after importing, review block names, linked template/image/color/record/media assets, and variable names in the target macro. The shared area creates a copy; delete stale shared items from the shared-library panel to keep the library clean.
AI assistant
Build a block chain with MH AI in natural language
Tell MH AI what you want in plain language; it proposes the right block sequence and lands it in the workspace after you approve. In the current release it works with cloud providers such as Gemini, Claude, and OpenAI; on-device local models are on the roadmap.