Get started

Company as code.A backend framework and server for agents.

A workspace is backed by a git repo. Every agent in it is a custom pi agent: a minimal open-source harness you extend with pi extensions. kortix.yaml declares the agents, connectors, triggers and rules. OpenChatly deploys them to the cloud and runs every session on its own computer. Build your own experience with @kortix/sdk and @kortix/ui.

Start for freeRead the kortix.yaml reference

One block per agent. It gets the tools, connectors and skills the block lists, and nothing else.

arcadia / kortix.yaml
  1. 56 # Engineering
  2. 57 eng-triage:
  3. 58 description: Triages every new GitHub issue.
  4. 59 prompt_file: agents/engineering/triage.md
  5. 60 tools: [read, grep, glob, web_search]
  6. 61 connectors: [github, kortix_slack]
  7. 62 skills: [triage-issue]
  8. 63 extensions: [triage-policy]
Customize · Agents

eng-triage

Triages every new GitHub issue.

Tools
  • read
  • grep
  • glob
  • web_search
Connectors
  • github
  • kortix_slack
Skills
  • triage-issue
Extensions
  • triage-policy

The repository in /workspace, on its own branch

One file in one repo. OpenChatly runs what it declares.

Four ideas. The whole framework, in four parts.

  • A project is a git repoYour company, versioned.

    • OpenChatly hosts it, or link GitHub
    • Agents, skills and memory are files
    • Every change is a commit
  • kortix.yaml declares itOne file, checked before it runs.

    • Agents, connectors, triggers, rules
    • Access is deny-by-default
    • kortix validate on ship and merge
  • Custom pi agentsA minimal harness, deployed to the cloud.

    • pi, an open-source agent harness
    • pi extensions from npm or the repo
    • A computer and a branch per session
  • Your own experienceThe same backend, from code.

    • @kortix/sdk: one typed client
    • @kortix/ui: the web app’s components
    • A CLI and a REST API

How it works.One part at a time.

Agents

An agent is a block in kortix.yaml and a Markdown prompt. The block names its model, tools, connectors and skills.

Access is deny-by-default. An agent gets no connector, secret or skill the block does not list.

kortix.yaml

  # Marketing  marketing:    description: Drafts LinkedIn posts from shipped work.    prompt_file: agents/marketing/content.md    tools: [read, web_search]    connectors: [linkedin, kortix_slack]    skills: [write-post]    commands: [draft-post]    extensions: [web-access]

agents/marketing/content.md

You write Arcadia LinkedIn posts from work the team shipped.Follow the write-post skill and the tone in the company memory.Every post waits for a person to approve it.

The architecture. One API. A computer per session.

Clients

People and code reach OpenChatly the same way.

  • Web app
  • Desktop
  • Mobile
  • CLI
  • Slack
  • Microsoft Teams
  • Your app

OpenChatly API

Decides who may run which agent, starts sessions, holds connector logins and change requests.

Workspace repository

kortix.yaml, agents, skills and memory. OpenChatly hosts it, or you link GitHub.

Session computer

One per session. Your pi agent and its extensions work here, on the session’s own branch.

LLM gateway

Every model call. OpenChatly-managed models or your own keys.

OpenChatly Drive

Shared folders and company memory, open at /drives.

Framework questions.Answered from the docs.

Anything else, write to the team.

Do I have to write YAML?

No. People manage agents, connectors and triggers under Customize in the web app, and Create in chat writes a new agent with you. Those edits land in the same kortix.yaml.

Can I keep the repository on GitHub or Gitee?

Yes. With a GitHub or Gitee origin, kortix ship links that repository, and plain git push and git pull work. Without one, OpenChatly creates and hosts the repository.

What does kortix validate check?

Every key against the schema, then the files around it: prompt files that do not exist, skill folders without a SKILL.md, and connector or secret names the file does not declare. It exits 1 on an error. kortix ship runs the same checks, and a merge with an invalid kortix.yaml is refused.

When does a change to kortix.yaml take effect?

When it lands on the base branch, through a merge or a push. New sessions start with it. A running session picks it up at the start of its next turn.

What runs inside a session?

pi, a minimal open-source agent harness. Every agent you declare is a pi agent, and every new session runs it on its own cloud computer. It calls models only through the OpenChatly LLM gateway.

Can I extend the agent harness?

Yes. Write a pi extension in TypeScript, or pin a pi package from npm, and register it under extensions in kortix.yaml. Each agent loads only the extensions it lists. An extension can add tools, such as your own policy as code, and react to events, such as a check before every tool call.

Where do secret values live?

In OpenChatly, encrypted. kortix.yaml lists only the names a project needs. No page, command or API shows a stored value again.

Own your AI.Start today, in our cloud.

Start for free

OpenChatly is the AI workspace for everything. One person directing, agents executing, from goal to finished work.

©2026 OpenChatly AI.沪ICP备2025124785号-5

Resource guide

  • Product overview
  • Skills marketplace

Terms of service

  • User agreement
  • Privacy policy

Contact us