What covey is put to work on
Four areas for which the matching connections already ship — so an agent can work there on day one instead of having to be connected first.
Support and ticketing
An agent that stands in the queue like a colleague: a new ticket wakes it, it reads the history, clarifies internally what needs clarifying — and anything that goes outside goes only after approval.
Read onSoftware development
An agent with a working copy of the source of its own: it takes on an issue, submits its change for review, and reads what the automated tests say. A person does the merging.
Read onQuality assurance
An agent that checks rather than builds: it reads a change against the requirement, tries it out in the browser, and writes its findings where they will be read — directly on the change.
Read onEmail and mailbox
A mailbox as the trigger: the agent reviews what comes in, replies within the existing thread, and files away what needs filing. What goes out can pass through an approval first.
Read onWhy exactly these four
Because these are the areas for which ready-made connections exist. A use case with no connected system would be a page about an intention. What is described here can be rebuilt after installation: enable the target system, hire the agent, deposit the credentials, wake it.
Try it yourself
covey is run by you: one program, a Postgres database, Docker for the workplaces. The instructions are in the documentation.