Environment variables

There are a bunch of environment variables that must be set up in order for the instance to run properly.

LICENSE_KEY

HOST

REDIS_URL

POSTGRES_HOST
POSTGRES_USER
POSTGRES_PORT
POSTGRES_DB
POSTGRES_PASSWD

AUTH0_CLIENTID
AUTH0_DOMAIN
AUTH0_AUDIENCE

MAILGUN_API_KEY
MAILGUN_DOMAIN

Let's go through these variables in detail.

License Key

The license key to use with this docker container. The container will exit if it is not able to contact https://taskforce.sh and validate the license.

You will find your license key on your Taskforce.sh account.

Host

This variable should point to the actual host running the dashboard, for example: https://my.taskforce.dashboard.com

Redis

The dashboard uses Redis for some internal communication and for the Monitoring and Alerts system. A small instance of about 128Mb RAM will be enough in most cases.

PostgreSQL

There are a few variables used to configure the required postgres database, just fill in the values for your database provider accordingly. You won't need a powerful PostgreSQL instance for the dashboard, any minimal instance will do.

Auth0

The authentication of the users is performed by Auth0. If you are not using Auth0 you can just create a free account which will most likely be enough for your needs. There are some steps involved in configuring Auth0 properly, please refer to this guide.

Mailgun

Mailgun is used for sending alert messages as well as team invitations. You can get a Mailgun account with generous quotas for free, then just follow these instructions.

AI Agents (MCP)

These variables are optional. They tune the AI agents feature and its MCP endpoint (https://<your-taskforce-host>/mcp). If they're not set, the defaults below apply, which are the same limits used on the hosted Taskforce.sh.

Variable	Default	Description
AGENTS_MAX_PER_ORGANIZATION	3	Maximum number of agents per organization
AGENTS_RATE_LIMIT_MAX	120	Maximum MCP requests per agent token per window. Set to 0 to disable rate limiting
AGENTS_RATE_LIMIT_WINDOW_MS	60000	Length of the rate-limit window, in milliseconds
AGENTS_REQUEST_BODY_LIMIT	256kb	Maximum size of an MCP request body (e.g. 512kb, 1mb)
AGENTS_REQUEST_TIMEOUT_MS	30000	Maximum time a single MCP request may run, in milliseconds

TIP

The rate limit is tracked in memory by each dashboard instance. If you run several instances behind a load balancer, each one enforces the limit separately.

INFO

Currently the dashboard will be exposed at port 9876, and cannot be configured to a different port.