Parts of the system

The Tactet platform has three parts: an agent server, a UI and a cloud service. The agent server and the UI run in your organization. Developers build agents in the UI and users run them there. Chat applications, agent harnesses and your own programs reach the agent server through the same REST API.

Your organization
UIIn the browser, or build your own.
Slack, Teams, Google ChatChat integrations
REST clientYour own application on the REST API.
Agent server cluster Stateless
Cloud service Shared or dedicated Conversations, memories encrypted by default

The agent server

The agent server is a Python 3.12+ package. pip install tactet installs the agent server and the UI together. The agent server runs inside your organization and holds no state. At startup it loads the account's configuration, keeps that configuration current, and runs agents. Its REST API is described at /openapi.json, with Swagger UI at /docs and ReDoc at /redoc.

The server is asynchronous and needs nothing beyond its Python packages. Run one on a laptop, run one as a standalone server, or run several as a load-balanced cluster. No server holds state, so any server can serve any request.

The UI

The UI is a single-page application that the agent server serves at /ui. What a person sees depends on their role. Users get search and conversations. Developers also get drafts, the editor with Draft with AI, validation and publishing, agent configuration and agent execution reports. Administrators also get users, authentication, system configuration and user reports. Owners get account settings and billing as well. See UI.

The UI is installed with the agent server, but the two are separate projects on GitHub: agent-server and ui. The UI uses nothing but the agent server's REST API, so an interface of your own can replace it.

The cloud service

The cloud service holds all state: accounts and users, agent definitions and drafts, configuration, conversation context, the search index, and the data behind the reports. It checks agent definitions, indexes the description a developer writes for a published agent, and answers searches. Only agent servers call the cloud service's API. Calling the cloud service directly can leave the platform in an inconsistent state. The Tactet license also prohibits it. The cloud service is shared or dedicated.

Other interfaces

The UI is one client of the agent server's REST API. Three other kinds of client use the same API.

Chat applications

People can use agents from Slack, Microsoft Teams or Google Chat. Tactet provides the integration points; the bot that sits between the chat application and the agent server is written by your company. See Chat integrations.

Agent harness

An agent harness such as Claude Code, or any client that implements Agent Skills, uses your agents through one skill, tactet-skill. The assistant chooses which published agent runs, the agent runs on your agent server, and each person authenticates with their own integration token. See Skill integration.

REST client

Your own scripts, schedulers and applications call the same REST API the UI uses. Every call under /api/ is an HTTP POST with a JSON body, and the API is described at /openapi.json on the agent server. See REST API and Creating your own client.