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.
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
Understand what the project demonstrates, then decide which mechanism addresses a real gap in your own workflow.
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.
Apply the Ideas to Your Workflow
Use these scenarios as design references for work organized in Floatboat. Any software integration needs its own compatibility and permission checks.
A task-centered workspace
Define how source material, current activity, and expected deliverables should stay connected during a longer task.
A human review point
Plan what evidence and context a user needs before accepting an agent’s proposed change or external action.
A workflow across interfaces
Study where state and execution belong when the same work can be viewed through different interfaces.
From Reference to a Workflow Experiment
Start with a task and a small testable change, whether that means better instructions, a new tool connection, or a runtime component.
- 01
Map the layers of the task
Separate business context, user interaction, execution tools, and the result that must be reviewed.
- 02
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.
- 03
Prototype the review loop
Test one task from input to a reviewable result before expanding the workflow across more tools or interfaces.
Related Agent Projects
Compare independent agents through their interfaces, extension models, and approach to carrying work forward.
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.