Your tools. Your website.
Configure OpenCode for the project and CMS operations. Choose the workflow that fits your team and keep the website manageable when tools or suppliers change.
Discuss your OpenCode workflow.
Choose a tool for the task.
Set up the agent’s model, project environment and CMS tools. Start with a concrete task: “Prepare a page for our new service, suggest the structure and show me the result.” Available operations depend on configuration and permissions.
Change tools while keeping the project.
Content, images, publication history and URLs stay in Progressive CMS. Presentation lives in the theme. A freelancer can prepare pages, a studio can develop the design and the client can edit the website in the admin, all around the same project.
Direct the work. Keep control.
Begin with one reviewed task.
Progressive CMS is open-source software with public releases. OpenCode and model access are configured separately. Start with a small task, verify the connection and agree publication rules before extending the workflow to new sections, articles, images or metadata.
Before you begin
Are OpenCode and Progressive CMS one product?
No. They participate in a workflow through configured project tools and CMS access.
Where is model choice configured?
In the agent’s own setup. CMS access and publication permissions are separate.
What remains after changing agents?
The website content, images and publications remain in the CMS; the theme remains in the project.
How can I start using OpenCode with Progressive CMS?
Choose a small task, configure tools and access, then verify the result. The Download page links to public releases and installation guidance.
Choose your next step.
-
Agent workflow
Explore the workflow
Other tools, common permissions and review.
-
Build a new website
Explore implementation
Your design and manageable pages.
-
Migrate a website
Explore migration
Content, URLs and metadata with checks.
-
Freelancers and studios
Explore
Themes, teamwork and client handover.
See the official OpenCode documentation for current agent capabilities and requirements. It is installed and configured separately from the CMS.