PostHog Slack app commands and limitations

The full set of commands @PostHog accepts, in the same order it lists them when you run @PostHog help:

CommandWhat it does
@PostHog <task description>Create a task for the agent to work on
@PostHog rules listShow all routing rules
@PostHog rules add "description" org/repoAdd a routing rule
@PostHog rules add "description"Add a routing rule (pick repo from list)
@PostHog rules remove <number(s)>Remove routing rules by number (e.g. remove 1 or remove 1,2)
@PostHog projectShow which PostHog project your mentions route to in this workspace
@PostHog project <id>Set the PostHog project your mentions route to in this workspace
@PostHog helpShow the command list

For repo selection, the bot checks routing rules first. If nothing matches and you have multiple repos, it opens the in-thread picker. If you only have one repo connected, the task runs against it directly. The project commands only matter if your Slack workspace is connected to multiple PostHog projects - see Pick a project.

Routing rules

Routing rules let you map a mention's content to a specific repo so the agent doesn't have to ask. A rule has a free-text description that's matched against the mention and an org/repo target it routes to:

@PostHog rules add "frontend bug" posthog/posthog
@PostHog rules add "billing changes" posthog/billing

When several rules match, the first one in rules list wins. Use @PostHog rules remove 1,2 to drop rules you no longer want; numbers correspond to the positions printed by rules list.

Limitations

An honest (but non-exhaustive) list of things to know before you lean on the Slack app:

  • Ephemeral sandbox. Each task runs in a fresh sandbox that lives roughly six hours. Long iterations need re-prompting once it recycles.
  • Personal GitHub auth is per user. Every teammate who wants to ship a PR has to connect their own GitHub once. First-time setup has known rough edges.
  • Single-author follow-ups. Only the person who started a task can steer it. Colleagues' messages become context, not instructions.
  • Text input only. The agent can't read images yet - paste descriptions instead of screenshots.
  • DMs coming soon. The bot doesn't respond in direct messages yet. For now, add it to a private channel of one if you want a quiet space.
  • 500-repo cap on the picker. If your team's GitHub install exposes more than 500 repos, the list is truncated. Add a routing rule for repos that fall off the end.
  • Workflow timeouts. A single mention has a 10-minute workflow timeout; the repo picker times out after 15 minutes.
  • Behavior is still moving. Prompt construction and review-bot trust heuristics are being actively iterated. Expect shifts between beta builds.

Community questions

Was this page useful?

Questions about this page? or post a community question.