Separate task modes
Study the division of agent responsibilities when deciding which workflow stages should inspect, plan, or change a repository.
OpenCode
Study OpenCode’s coding-agent workflow to improve how your own tasks move from investigation to changes and review. Use its interaction and extension design as references for development work organized in Floatboat.
About OpenCode
OpenCode is an open-source AI coding agent published by Anomaly. It connects task conversations with repository tools. The model service supplies reasoning and generation, the execution environment handles files and commands, and the application coordinates the workflow.
For workflow design, OpenCode is a concrete implementation to study rather than a requirement to switch products. Its agent modes and interactive feedback can inform how you separate investigation from implementation, expose a change for review, and add task-specific integrations to your own environment.
The project source is MIT licensed. Model-provider accounts, subscription access, remote services, and community additions have separate requirements. The source can be inspected and adapted without implying that all associated hosted services are free or included.
Workflow Mechanisms to Learn From
Understand what the project demonstrates, then decide which mechanism addresses a real gap in your own workflow.
Expose useful feedback
Use the interactive workflow as a reference for showing progress and tool results where a person can make an informed decision.
Evaluate integrations by task
Inspect an integration’s tools and maintainer before adapting the pattern to the development workflow you actually need.
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 repository investigation stage
Define what an agent must learn before implementation begins, including relevant files, constraints, and unresolved decisions.
A reviewable change pipeline
Separate the proposed change from acceptance so generated code is paired with an inspectable diff and relevant checks.
A task-specific development tool
Study the extension interfaces when considering a connection to a project’s existing checks or external development systems.
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
Describe the desired handoff
Write down what investigation must deliver before planning or implementation can safely continue.
- 02
Limit available actions
Match tool access and the active mode to each stage rather than giving every step the same ability to change files.
- 03
Check the result and feedback
Evaluate whether the workflow makes errors visible and gives the user enough evidence to accept or revise the change.
Related Agent Projects
Compare independent agents through their interfaces, extension models, and approach to carrying work forward.
OpenCode FAQ
Is OpenCode a model provider?
OpenCode is a coding-agent application that provides the interface and execution workflow. The model used by a session depends on its provider configuration; the application and model service have different responsibilities.
Should OpenCode be called a Skill?
No. It is an independent coding-agent project. Skills or other instructions can form part of an agent workflow, but they do not replace the application that runs the workflow.
Who publishes the official repository?
The repository is anomalyco/opencode, under Anomaly’s GitHub organization. Community integrations and similarly named projects should be checked separately rather than attributed to Anomaly automatically.
Are planning and building the same mode?
The official project documents different agent modes for different responsibilities. Read the selected mode’s behavior and permissions before assuming a planning session can or should make changes.
Does MIT include a free model subscription?
No. It covers the application source. Provider accounts, model usage, commercial subscriptions, and external integrations have their own conditions and costs.
Must I switch products to use these workflow ideas?
No. You can first use OpenCode 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.