A team on Open WebUI gets a self-hosted open source chat window over its models and documents. The gain comes when agents run the work itself, on their own cloud computers, and hand back finished files.
Four jobs an agent runs on its own cloud computer and returns as a file.
The agent groups new tickets, answers the repeatable ones and flags the rest for a person.
| ticket | account | category | action | owner |
|---|---|---|---|---|
| 4821 | Northwind | billing | draft reply | 17 |
| 4822 | Globex | login | escalate | 04 |
| 4823 | Initech | refund | draft reply | 09 |
38 grouped, 12 drafted, 5 escalated
The agent reproduces the day’s worst error on its own machine, patches it and opens a change request.
+2 -1
9 error groups, top one fixed, 118 tests pass
The agent pulls last week’s numbers from the tools it can reach and returns a short digest a manager can read.
one page, every figure linked to its source
The agent matches the ledger against the bank, finds the missing receipts, attaches them and closes the month.
| cost center | plan | actual | variance |
|---|---|---|---|
| R&D platform | 1225000 | 1182400 | 42600 |
| go to market | 810000 | 742800 | 67200 |
9 receipts chased and attached, 1 center over plan
Open WebUI for teams is a self-hosted chat platform: a window over your models and documents that runs offline on your own hardware. Kortix, the open-source AI Operating System, keeps the same promise of ownership and adds the part a team needs when the reply has to become a file, a fix or a report.
The unit of work differs. In a chat tool a person drives every turn. In Kortix a session runs an agent on its own isolated sandbox and its own branch, and the agent can install, run and break anything on that machine while only what it commits survives. A person reads the diff before merge: work reaches main through a change request, and merge is default-deny for agents.
A team can also start the work without being present. A trigger runs a session on a cron schedule or a signed webhook, and the agent replies where the team already is: Slack, Microsoft Teams, the web app or the CLI.
# kortix.yaml: how a team agent gets its job and its toolsagents: support-triage: file: agents/support-triage.md connectors: all triggers: - slug: daily-digest type: cron cron: '0 0 9 * * 1-5' prompt: Summarize yesterday's support tickets and open a change request with the digest.Each session boots its own cloud computer with the repo and the tools already on it, so there is nothing for a person to install. Thousands of agents run in parallel on one config, each on its own cloud computer. For a team that measures a tool by what it hands back at the end of the day, that is the difference between an interface and a place to put the work. Start from one repo with Try Kortix.