Separate interface and execution
Study the workbench’s layers when deciding which part of a workflow should collect context and which part should execute the task.
ZCode
Study ZCode’s workbench and agent-runtime design to improve your own workflows. Use its interface separation and public source as references for organizing task context, execution feedback, and human review around work in Floatboat.
Keep a diagram task connected to its workspace
Describe a long task whose material, progress, and review decisions need to stay connected. Use ZCode as a reference for interface and execution responsibilities, then ask for a bounded design that makes the proposed outcome understandable before expanding tools or views.
Describe the diagram format, workspace inputs, allowed edits, and export target.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatYour request for Floatboat
Preview and copy the request. It is not sent automatically from this page.
Reference: ZCode https://github.com/zai-org/ZCode Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Study ZCode’s UI Plugin documentation and Excalidraw example. Design a workflow that turns my project notes into an editable process diagram, keeps revisions linked to the source notes, and exports a reviewable result. Check APIs before proposing integration. Expected deliverable: A plugin interaction sketch with data boundaries and a small compatibility test.
About ZCode
ZCode is Z.ai’s coding-agent harness and development workbench. The official repository describes desktop, browser, and terminal experiences, and includes client code, backend services, shared UI, and the agent CLI and runtime. It is broader than an editor plugin or a single task instruction.
Its value as a workflow reference is the relationship between the interface, backend services, and agent execution. A Floatboat user can study those boundaries to decide where context should enter, how a task’s progress should be presented, and when the user should review a proposed action. Actual reuse requires a separately verified integration.
The public source uses Apache-2.0 and the repository also provides a project notice covering additional operational and third-party matters. Source availability does not settle model access, hosted service terms, or every application behavior. Review the official notice and release documentation for the version you choose.
Workflow Mechanisms to Learn From
ZCode separates interface presentation from execution while making task progress available for review. Compare the project material, current activity, and surrounding system responsibilities before borrowing its structure, so a visible status does not replace evidence about the resulting work.
Make task progress reviewable
Use the application structure as a reference for presenting agent activity alongside the context a person needs to judge it.
Inspect the complete system
Read client, backend, CLI, and runtime source together when evaluating a workflow pattern rather than copying an isolated interface.
Use Cases for ZCode
Long-running projects, human approval, and multiple interfaces need a clear owner for task state. Use ZCode to examine how materials, current activity, and proposed results remain connected without confusing a visible execution log with an understandable review artifact.
A task-centered workspace
Long-running work needs source material, working directories, and expected deliverables to stay connected. Describe how the current activity relates to those inputs and how task state is retained as work progresses. The workspace design should make it possible to trace a result back through the activity that produced it.
A human review point
A person reviewing an agent's proposed edit or external operation needs more than an execution log. Identify the relevant context, the change being proposed, and the evidence that supports accepting it. Build those artifacts into the review point so approval rests on an understandable result.
A workflow across interfaces
When a task appears through desktop, web, and terminal interfaces, decide which layer owns state and which performs execution. Map the shared task information and the responsibilities of each entry point, then check consistency between them. Multiple views should not silently become competing versions of the same work.
Map where task information is processed
A desktop interface can present work whose data or execution crosses another service boundary. Use ZCode's project notice and source as references to identify what is local, what is remote, and which component receives each piece of context. Apply that map to your own workspace design before providing sensitive material or deciding how approvals should accompany the execution path.
Check ZCode’s data boundaries
Local and remote execution can expose task information to different recipients. Use ZCode's source and project notice to identify those boundaries before supplying material, with the actual service path checked separately from what the desktop interface appears to contain.
Check data and execution boundaries
Use the project notice and source to assess what is local, what is remote, and which service receives task information.
Prototype a ZCode review loop
A workflow spanning task context, interaction, and tools needs those responsibilities assigned before expansion. Test one complete, reviewable result first, then use its evidence to decide where another interface or tool would add value without splitting the task state.
Map the layers of the task
Separate business context, user interaction, execution tools, and the result that must be reviewed.
Prototype the review loop
Test one task from input to a reviewable result before expanding the workflow across more tools or interfaces.
Related Software Projects
Compare the workflows, operating requirements, and source licenses of these projects.
ZCode FAQ
Does ZCode include a real agent harness?
Yes. The official project identifies ZCode as a coding-agent harness, and the repository includes the agent CLI and runtime alongside its application code. It is not merely a third-party skin around a model API.
Is ZCode only a desktop application?
No. The repository documents desktop, browser, and terminal interfaces. Check the selected interface’s requirements rather than assuming a configuration for one entry point works unchanged in another.
Who publishes the official ZCode repository?
The official repository is zai-org/ZCode under Z.ai. Community forks, including similarly named workbenches, should be identified by their own maintainers and changes rather than treated as the same official release.
What does the source license cover?
The repository is Apache-2.0 licensed. Third-party notices, model APIs, hosted services, and distribution-specific conditions still need separate review; the repository includes NOTICE.md for relevant project declarations.
Can model quality alone explain ZCode results?
No. Tool configuration, context assembly, the execution environment, and how changes are reviewed also affect the outcome. Compare the complete workflow for the task rather than treating the model name as the result.
Must I switch products to use these workflow ideas?
No. You can first use ZCode as a reference for task structure, tool boundaries, and result review in your existing workflow. Reusing software is a separate choice that requires compatibility, permissions, and license checks; applying the design ideas does not automatically connect the software to Floatboat.