👾Kubiya Teammates

Create virtual teammates who can take on tasks for development and infrastructure operations

In this page, you'll learn:

1. What Kubiya Teammates are

2. What Kubiya Teammates can do

Later in this section, we will also show you:

• Common use cases for Kubiya Teammates

• How to create and configure Kubiya Teammates

• How to manage Teammates

• How to instruct them to perform tasks

What are Kubiya Teammates?

Kubiya Teammates are virtual teammates designed to engage with you and your organization in a familiar conversational manner and execute development and infrastructure operations in a consistent, expected manner. They are powered by LLMs and Kubiya's proprietary platform, and they operate securely and compliantly on your infrastructure.

What can Kubiya Teammates do?

There are endless possibilities to what Kubiya Teammates can do. Kubiya Teammates execute actions, including in 3rd-party platforms, using tools, which are stateless services that can be chained together to form powerful workfuls that solve organizational pains. You can also create your own tools in order to extend your Teammates' capabilities.

Kubiya Teammates can be triggered to execute actions by events (webhooks), time (cronjobs), and on-command (requests by users via chat). They can authenticate in other platforms – both via Oauth or other credentials – and perform actions in those platforms. They can be equipped with organizational knowledge, so that when they perform actions on your behalf they do it correctly.

Kubiya Teammates are a powerful and can solve real organizational painpoints and bottlenecks when used properly. Continue reading to learn about common use cases for which ops teams use Kubiya Teammates.

Table of Contents

1. What are Teammates (technically)

2. What they can do

3. Common use cases

4. How to Create and configure them

   1. Create

      1. Configuration

         1. Prerequisites

            1. Sources

            2. Runner

            3. Integrations

         2. Identity

         3. Instructions

         4. Configuration

         5. Access

      2. Teammates managed by a task (hidden for now)

5. Teammate management

   1. View Teammate

   2. Edit/Update Teammate

   3. Delete Teammate

6. How to instruct them to perform tasks

   1. Connect Slack

   2. Go to Kubiya Slack app

   3. Summoning options

      1. Write a message

      2. Call out a specific Teammate (!)

      3. Browse or Find from the Teammate menu

   4. Breaking down the conversation with Kubi/AI Teammates

      1. How it starts

         1. (Depending on how you summoned it)

      2. How it progresses

      3. How it ends

   5. What to do next

   6. Also: Advanced(?) - Adding Kubiya to a Slack channel

Overview

• Agents are containerized environments with a set of tools that kubiya utilizes during your chat.

• Custom Agents allows you to define a containerized environment with your own set of tools and instructions.

• Each containerized application is defined as a custom profile, utilizing stateless container technology and AI agents to execute a wide array of tasks.

Architecture

1. Custom Agents are built on top of stateless container technology. These containers serve as isolated execution environments where a set of tools and applications can be deployed. The containers terminate after the execution is complete. This ensures a consistent environment for every execution cycle.

2. AI Agent: An AI-powered agent resides within the container, acting as the executor of tasks. It interprets natural language commands and interacts with the tools and applications within the container to perform the specified actions.

3. Custom profiles can be managed using source control for easy maintenance of the core instructions for the AI on the specified profile environment.

   

   The agent utilize git to clone the repo

   

Functionalities

1. Manage your DevOps stack and infrastructure.

2. Ability to plan and execute code.

3. Easy definition of use cases using natural language.

4. Agent's tasks can be scheduled or triggered via webhooks.