Charts on the dashboard, goals and activity
The dashboard, goals and activity pages now open with charts. Goals show their health and period at a glance, and activity shows events per day, by action and by the busiest actors above the timeline.
Every change to ConvOps a user can notice, dated by the day it reached the product. Newest first, grouped by month.
plain language · real dates · rss feed
Template packs
Explore and install workflows
Starter workflows for every work type
Connect first, set up your workspace after
The ConvOps changelog lists every change a user can notice in ConvOps, the operations layer for AI agents, dated by the day it reached the product. Entries run newest first and are grouped by month. Each one says what you can now do, in plain language, and links to the page that explains it.
New here? Start with how to connect ConvOps to your AI client, or see how ConvOps compares with other AI agent workflow tools.
4 entries
The dashboard, goals and activity pages now open with charts. Goals show their health and period at a glance, and activity shows events per day, by action and by the busiest actors above the timeline.
When a decision invokes a sub-workflow, the task page shows the parent workflow with the open sub-workflow nested inside it. You see exactly which step the run is on, at every level.
How decisions invoke sub-workflowsMemories and routes are now filed under a project from your workspace catalog. Recall, context lookups and memory lists can be narrowed to one project, and a memory can be moved to another project when you edit it.
The brainMerge one project into another and its work moves with it. A task that names an unknown or archived project is now refused with a clear message instead of creating a new project by accident.
Workspaces9 entries
An environment can set the name and email on every commit a run makes. You also choose which repository receives the work, and whether a finished run lands on a task branch for review or straight on the branch you configure.
EnvironmentsAdd MCP servers to your workspace and attach them to an environment, with rules that allow or deny each tool. Isolated runs start those servers next to the agent, and the agent is offered only the tools the rules let through.
EnvironmentsEach environment lists the ConvOps tools an unattended run is offered, and a person switches each one on or off. Task tools reach only the run's own task unless you widen them.
EnvironmentsThe command palette now searches tasks, memories, routes, workflows, projects and executors from one box. Press C anywhere to create a task.
An executor can now start every run as its own Kubernetes Job: a fresh pod with its own volume and secret, and a time limit. Each run keeps a history with its event log and transcript, and a Stop button.
One run, one podPrepare once what every run needs: repositories, git access, secrets and variables. A check clones every repository and resolves every secret in a throwaway copy before any run starts, and reports what is ready or failed.
EnvironmentsBrowse, filter and read your workspace memories and routes in the web app, and add or correct them from the same page. When a new memory replaces older ones, the app tells you which.
The brainMark one workflow as the router of your workspace. Every new task, bug, initiative or plan starts there, and the router sends it to the right workflow. The app shows a Router badge on that workflow.
Graph engineeringEvery dispatched run now shows its status, timeline and transcript on the task page, and a new executions page lists runs across the workspace. Your AI client can read the same status and transcript, and stop a run.
Unattended runs6 entries
Your AI can change one passage of a task description or a step instruction by anchoring on the text around it, instead of sending the whole thing back. A version check stops two agents from overwriting each other, and replacing a long text outright needs an explicit confirm.
Workflow engineMark when work is committed: now, next or later. Children inherit the horizon of their nearest ancestor, the dashboard groups work by horizon, and four built-in pools list what is committed now, what is actionable, what is next and what has gone quiet.
Pools and autonomyWhen you create an API key you can limit it to the workspaces you pick. A key scoped this way only reaches those workspaces.
SecurityA workspace setting stops anyone, person or agent, from marking a task done while its workflow is still running. The refusal names the current step, so the work finishes through the workflow. Cancelling stays possible.
GovernanceEvery installable workflow template and pack is now browsable on convops.app, with its real steps, gates and decisions. Pick one, then install it into your workspace in the app.
Template catalogEach workspace now keeps one list of projects. Tasks, routing rules and every project picker in the app read from it, and a project can be archived when the work is done.
Workspaces5 entries
Every change now records the server-verified person behind it next to the label the agent gives itself. The app shows the person on the task and next to the agent on every activity row, so you can always answer who approved that.
Dual attributionA step can name the executor that should run it, and a task can carry its own default. When a run reaches a step meant for a different executor, the agent is told to hand it over. Nothing is dispatched behind your back.
ExecutorsDefine executors for your workspace, each naming which AI client runs the work and where. Dispatch a task to one of them, then follow its status and read its transcript from your AI client.
ExecutorsSave a query as a pool, and an agent can ask it what to work on next. The pool is resolved live on every call and returns exactly one task or nothing, so empty is an answer the workflow can branch on.
Work poolScheduled runs that go quiet are picked up and resumed automatically. After repeated tries the task moves to a new Stalled status with the reason, and a parent waiting on it continues instead of hanging.
Autonomy8 entries
Create a workspace, accept or decline an invitation and manage your API keys straight from your AI client. Creating or revoking a key still needs a signed-in person.
Connect your AI toolPass a short context note with a task or workflow call and it is stored as a memory linked to that task. A step can require that note before it advances, and automatic capture is available as a workspace setting, off by default.
The brainThirteen new starter workflows in four packs: Content Studio, Sales Outreach, Business Ops and Chat Essentials. They are written for a plain AI chat, with approvals only where something is published, sent or decided.
Template catalogA single connection now reaches every workspace you belong to. Writes name the workspace they go to, and search and recall look across all of them at once.
WorkspacesInvite people to a workspace by email, then resend or revoke an invitation and manage members from settings. Invitations expire on their own.
WorkspacesAttach a schedule to an existing task and each fire resumes its workflow where it stopped, instead of creating a new task every time. Schedules that spawn a fresh task per fire work as before.
Unattended runsSign up or sign in with Google, including on the page that opens when you connect your AI client for the first time.
Connect your AI tool5 entries
Point your workspace at your own OpenCode server and tasks can run there without anyone typing. The connection is validated when you save it, from a new Execution page in settings.
AutonomyYour workspace gets a shared brain. Agents store what they learn as memories, record where things live as routes, and look both up before they act, so the next run starts from what the last one found.
The brainWrite a rule once, globally or for one workflow, and it is delivered inside the step the agent is working on. Edit it and every run picks it up. Policies inform the agent, gates enforce.
Workflow policyAsk your AI client to add, remove, move or update a single step, or to change a workflow's details. Each edit is validated against the whole workflow before it is saved.
Workflow engineInstall a whole pack of workflows in one go. Shared fragments come along automatically, and the app warns you before you uninstall something another workflow depends on.
Template catalog3 entries
A new Explore page lists every starter workflow with suggested prompts. Install one into your workspace, where it sits next to the workflows you write yourself, and pick your first workflows during onboarding.
Template catalogReady-made workflows for goals, plans, phases, features, bug fixes and tasks, with gates between the stages. Every type of work can start on a process from day one.
Agentic workflows, explainedConnect your AI client and sign in before you have a workspace. Sign-in takes you to onboarding to create one, then hands you back to your client.
Connect your AI toolSubscribe to the RSS feed in any reader. Every entry on this page becomes one item, linked to its anchor here.
https://convops.app/changelog.xmlContinuously, not in big releases. A change goes live as soon as it reaches the product, and this page lists the ones a user can notice, each dated by the day it landed.
Internal work: tests, build pipelines, refactors and infrastructure. Each entry describes what you can now do, not how it was built.
No. ConvOps runs as a hosted MCP server, so a change is live for every connected AI client without installing anything. You bring your own AI client; ConvOps holds the process and the record.
Yes. The feed at https://convops.app/changelog.xml is RSS 2.0, with one item per entry that links to its anchor on this page.