Setting Up Other Services

While KiloClaw comes with a set of pre-configured tool integrations, your agent isn't limited to just those. KiloClaw can be configured to use virtually any third-party integration as a tool — as long as it has a CLI or an API, you can teach your agent to work with it.

We have seen this pattern work well with outside services like ZenDesk, Todoist, GitLab, and more.

If There Is a CLI

When the tool you want to integrate provides a command-line interface, follow these steps:

  1. Tell KiloClaw to install the CLI.

  2. Add a key, PAT, or token to the KiloClaw's 1Password.

  3. Navigate to the KiloClaw Dashboard (app.kilo.ai/claw/settings) > Danger Zone > Edit Files > workspace folder > TOOLS.md, and add the following to the bottom of the file:

TOOL is 1 SENTENCE DESCRIPTION. You have access to it via the CLI NAME CLI. The username and password are in the 1Password vault under TOOL.

  1. Ask the agent to perform a task using the tool.

If There Is No CLI, but There Is an API

When the tool only provides an API (no CLI), follow these steps:

  1. Add a key, PAT, or token to the KiloClaw's 1Password.

  2. Navigate to the KiloClaw Dashboard (app.kilo.ai/claw/settings) > Danger Zone > Edit Files > workspace folder > TOOLS.md, and add the following to the bottom of the file:

TOOL is 1 SENTENCE DESCRIPTION. You have access to it via the API. API documentation is at URL OF API DOCUMENTATION. Credentials are in 1Password under TOOL NAME.

  1. Ask the agent to use the API.
📝Note

If you have not configured your KiloClaw with the 1Password CLI, you can add the username in TOOLS.md and the key as an Additional Secret in the KiloClaw Dashboard with the config path skills.entries.<TOOL_NAME>.apiKey and environment variable name <TOOL_NAME>_API_KEY.

Improving performance

The instructions above will get your KiloClaw started with using the tool, but it will have to read the documentation every time and may fumble to use the CLI or API in question.

As you use the CLI or API, instruct KiloClaw to do the following to make usage more reliable and less token-intensive:

  • Save usage patterns to TOOLS.md
  • Extract usage patterns into a skill
  • Write a python or javascript wrapper for the CLI or API to encompass the ways you tend to use it