Skip to content

ctrlyokeOne workflow engine for every CLI coding agent

Prompt, steer, automate, and revisit every AI coding session — one prompt or a whole workflow.

What ctrlyoke is for ​

ctrlyoke gives you a better way to write prompts for any harness and to run them. You type a prompt in the dashboard's editor, and completions help you reference the context it needs: files, folders, symbols, editor selections, Git changes and earlier steps' output. ctrlyoke expands those references, sends the prompt to the harness you pick, and keeps the output, file changes and session history together.

ctrlyoke is not an AI agent and doesn't include one. It calls the harness CLIs you've installed and signed in to, and those keep talking to their own providers under your account. See How ctrlyoke talks to a harness.

It works the same way however much you send:

  • A single prompt, the way you would use the harness on its own.
  • A workflow: prompt and script steps run in order, each on any harness, with end conditions that check the result before moving on.
  • A dynamic workflow: a final step reviews the run and appends more steps until the work is done, for example a plan–implement–review loop or a bug hunt that keeps going.

Save any of them as a YAML, JSON or Markdown file to run again, share, or run in CI.

It ships in two forms:

FormWhat it is
VS Code extensionDashboard UI, prompt editor, embedded terminal, schema validation, and harness orchestration inside VS Code
ctrlyoke CLIHeadless or interactive workflow execution from a terminal or CI job, and ctrlyoke server, which opens the same dashboard in a browser without VS Code

Both include a built-in MCP server, ctrlyoke-mcp, and a set of built-in skills. A step that enables ctrlyoke-mcp can work on its own run: it can read earlier steps' output, append more steps (this is how a final step keeps a review or bug-hunt loop going), and coordinate with the other steps in its parallel group.

Where to start ​

Source-available under the ctrlyoke Commercial License.