Tactet agents

A Tactet agent is built for one well-defined task. Developers describe what an agent does in natural language. Search uses that description to match the agent to a request. The less the tasks of agents overlap, the more easily search matches a request to a single agent.

An agent has clear boundaries on the systems it can reach: APIs, databases and MCP servers. These boundaries are defined at compile time. LLM tool calls choose only within them.

A Tactet agent does not:

  • Call other agents.
  • Generate arbitrary code and run it.

Examples

  • Vacation request: takes the dates from the request, checks the leave balance, files the request and reports the result.
  • Invoice status: takes an invoice number and reports where the invoice stands in accounts payable.
  • Expense filing for a trip: retrieves the trip's amounts, files the claim and asks the user before submitting.
  • Part reorder: compares the stock of a part with its reorder point and raises a purchase order with an approved supplier.
  • Support ticket summary: retrieves a customer's open tickets and summarizes the state of each.

Agents work together in a conversation. An agent harness with the Tactet skill can act as the orchestrator. A custom orchestrator can be built on the REST API.