Hyperterse supports Redis as a connector for key-value operations, caching lookups, session retrieval, rate limit checks, and working with Redis data structures (hashes, lists, sets, sorted sets). Statements are standard Redis commands executed directly against the server.
Hyperterse connects to your existing Redis instance. It does not create or
manage databases — you provide a running Redis server (self-hosted, AWS
ElastiCache, Upstash, etc.) and a connection string.
Adapter configuration
Create an adapter file in app/adapters/:
connector: redis
connection_string: '{{ env.REDIS_URL }}'
options:
pool_size: '10'
Standard
TLS (cloud providers)
redis://user:password@host:port/db_number
rediss://user:password@host:port/db_number Note the double s in
rediss:// for TLS-encrypted connections.
Connection options
Maximum number of connections in the pool.
connection_string: 'redis://:password@localhost:6379/0'
rediss:// scheme:
connection_string: 'rediss://:password@host:6379/0'
Verify the connection
Start the server and confirm the adapter connects:
A successful connection produces:
INFO Connected to adapter: cache
Usage
Redis tool statements contain the Redis command to execute. Use {{ inputs.field }} placeholders for dynamic values.
app/tools/get-cached-value/config.terse
description: 'Retrieve a cached value by key'
use: cache
statement: 'GET {{ inputs.key }}'
inputs:
key:
type: string
description: 'Cache key'
auth:
plugin: allow_all
Common command patterns
Strings
Hashes
Lists
Sorted sets
# GET
statement: "GET {{ inputs.key }}"
# SET with expiry
statement: "SET {{ inputs.key }} {{ inputs.value }} EX {{ inputs.ttl }}"
# Get all fields
statement: "HGETALL {{ inputs.key }}"
# Get a specific field
statement: "HGET {{ inputs.key }} {{ inputs.field }}"
# Get a range
statement: "LRANGE {{ inputs.key }} 0 {{ inputs.count }}"
# Top entries by score
statement: "ZREVRANGE {{ inputs.key }} 0 {{ inputs.count }} WITHSCORES"
Separate adapters for different concerns
Use separate Redis adapters for distinct purposes:
Each adapter can connect to a different Redis database number or a different Redis instance entirely. Tools reference the appropriate adapter by name.
Troubleshooting
Connection refused
Verify Redis is running:
A PONG response confirms the server is accessible. Check firewall rules for remote instances.
Authentication failed
Ensure the password is correct in the connection string:
redis://:correct_password@localhost:6379/0
requirepass directive).
TLS required
Cloud-hosted Redis instances typically require TLS. Switch from redis:// to rediss://:
rediss://:password@host:6379/0
Memory issues
Monitor Redis memory usage with INFO memory. Configure maxmemory and an eviction policy (maxmemory-policy) on the Redis server to prevent out-of-memory conditions. 
