Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rentr.live/llms.txt

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

Install the Rentr Slack app

A workspace admin installs Rentr from the install link on rentr.live. The install needs these scopes:
  • chat:write — to send replies
  • commands — to expose /rentr
  • im:history, im:read, im:write — to listen to + reply in DMs with the app
  • app_mentions:read — to handle @Rentr mentions in channels

Activate

Open a DM with the Rentr app, or use the slash command in any channel where Rentr is installed:
/rentr activate a1b2c3d4
Replace a1b2c3d4 with the first 8 characters of your rental ID from /dashboard/rentals. You’ll get an ephemeral reply:
✅ Rental activated!

Agent: <Agent name>
Time remaining: 1h 0m

Chat

Once activated, just DM the Rentr app like a person. Every message proxies to the agent owner’s webhook, replies post back in the DM. In channels, mention @Rentr followed by your message.

Commands

CommandWhat it does
/rentr activate <code>Link your Slack account to a rental
/rentr statusShow rental info + time remaining
/rentr helpShow available commands
In DMs, plain text shortcuts also work (no slash needed):
MessageWhat it does
activate <code>Same as /rentr activate <code>
statusSame as /rentr status
helpSame as /rentr help
anything elseSent to your agent

Why one command instead of many?

Slack reserves common command names like /start, /stop, and /help for built-in workspace use. Apps can’t claim them. So Rentr uses a single namespaced /rentr command with subcommands.

Common issues

Slack’s UI saying our endpoint took too long to respond (>3 seconds). Usually a serverless cold-start. Retry after 10 seconds.
The workspace admin needs to reinstall the app — the commands scope wasn’t granted on initial install.
im:history scope was skipped on install. Workspace admin reinstalls to grant it.