Skip to main content

Documentation Index

Fetch the complete documentation index at: https://agent37.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

This is where you customize what the agent can do. Preinstall skills it reaches for on its own, add new tools with a plugin, and when you want every instance to start that way, bake it into a template.

​
Plugins

A plugin adds new tools to the agent: actions it can call that are not built in. Hermes loads plugins from its own config, so the format and the mechanism are documented with the agent itself.

Hermes plugins

How to write and load a plugin that gives Hermes new tools.

​
Preinstall with a custom image

Bake your skills, plugins, and packages into an image built FROM our base, then publish it as a custom template so every instance you create starts with them. 
# start FROM the Agent37 base, so the agent runtime, gateway, terminal,
# desktop, file browser, and managed auth all keep working
FROM ghcr.io/agent37/base:latest

# preinstall a skill with the skills CLI
RUN npx skills add vercel-labs/agent-skills --skill deploy-to-vercel

# add your own plugin (use the path from the Hermes plugin docs)
COPY ./plugins/my-plugin /home/agent/.hermes/plugins/my-plugin

# install any CLI or system package the agent needs (passwordless sudo)
RUN sudo apt-get update \
 && sudo apt-get install -y poppler-utils
Everything that makes the agent work comes from the base, so it keeps working; you are only layering on top. To ship this image as a reusable template, see Custom templates.

​
System prompt and agent config

The agent’s system prompt and the rest of its configuration live inside the instance, alongside its files. Change them inside the instance with Run commands or an embedded terminal, or preset them in a custom template.

​
Next steps

Templates

Preinstall skills, plugins, and tools so every instance boots with them.

Run commands

Run any shell command inside an instance from your backend.