Engineering

Build on Kortecx, with your stack.

Connect the tools you already use, chain agents into workflows, and read exactly what each one may touch before it runs. What you read is what will happen.

Talk to us Read the docs

The console is available today. The kx command line and an SDK are coming soon; the commands on this page show what they will do.

Read the ask before it runs.

Switch a grant off, or say Kortecx cannot fire a tool, and watch the manifest answer.

kortecx :: manifest · an example appEXAMPLE

granted = what it asked for ∩ what you hold ∩ what Kortecx can actually fire

Connect what you already run, or write the missing one.

Bring your own model provider, or your own MCP server on a host the team has approved, in preview. Register it once, and Kortecx dials it, asks what it can do, and writes the answer down. Slack, Notion, Gmail and Discord are coming soon.

kortecx :: connectionsEXAMPLE

Its tools, as agents see themRegister as

Why two providers can both offer “search”

Every discovered tool is named after the connection it came through: <connection name>/<tool>. Rename the connection on the left and the names follow. A grant is written against that exact name.

When the one you need is not there

Describe it and Kortecx drafts a working connector and checks it, so you can build and test it before a real credential exists.

kx new connector acme

Connections and MCP

One line is the whole dependency graph.

Say what runs after what, and what can run at the same time. A name used twice is the same step. Type your own; the command line that runs it is coming soon.

kortecx :: chainLIVE IN YOUR BROWSER

Chain expression

The operators

a > b      b runs after a
a & b      run together
a | b      together, looser
[ a > b ]  grouping

> binds tighter than &, which binds tighter than |. So a > b & c is not a fan-out: bracket the side you mean.

Nodes

Edges

Workflows and chaining

On a schedule, and still stopping to ask.

Put the work on a clock and it runs while nobody watches. Ask for approval, and anything it cannot take back is held until a person says yes, decided by how each tool declares itself.

kortecx :: approvalsEXAMPLE

The tool's declared class

The tool is reached through a connector

A schedule that still asks

kx triggers add --kind cron --interval 86400 --require-approval

A duplicate event still runs it once. If a step fails, a retry runs that step again, and the work already finished is not redone.

Approvals

No cluster to keep warm.

It runs end to end as a managed service, and there is nothing to provision before it does. It is also early, and we would rather you found the limits here than in your own week.

Talk to us What it isn't yet