teal;dr
HOMEDOCS

Search Commands

Comprehensive guide to TeaL;DR's semantic search capabilities.

/ask

The primary search command. Uses natural language processing to find relevant messages based on semantic meaning rather than exact keyword matches.

Syntax

/ask query: <your search query> [channel: #channel] [user: @user] [limit: number]

Parameters

  • query (required): Natural language search query
  • channel (optional): Limit search to specific channel
  • user (optional): Limit search to specific user's messages
  • limit (optional): Number of results to return (default: 5, max: 20)

Examples

Basic search:

/ask query: deployment issues last week

Search in specific channel:

/ask query: API documentation channel: #dev-team

Search specific user's messages:

/ask query: bug reports user: @john limit: 10

💡 Pro Tips

  • Use descriptive phrases instead of single keywords for better results
  • The bot understands context - "what did we decide about the API?" works better than "API decision"
  • Follow-up questions maintain context from previous searches
  • Results are ranked by relevance, not chronological order

/recap

Generate AI-powered summaries of conversations over a specified time period. Useful for catching up on missed discussions or reviewing past conversations.

Syntax

/recap period: <time period> [channel: #channel] [format: brief|detailed]

Parameters

  • period (required): Time period to summarize (Last 24 hours, Last 7 days, Last 30 days, Custom)
  • channel (optional): Limit recap to specific channel
  • format (optional): Summary format - brief (key points) or detailed (comprehensive)

Examples

Daily recap:

/recap period: Last 24 hours format: brief

Weekly channel summary:

/recap period: Last 7 days channel: #general format: detailed

Recap Output Includes

  • Main topics discussed
  • Key decisions made
  • Action items mentioned
  • Most active participants
  • Important links or resources shared

/timemachine

View what happened on a specific date in previous years. Great for anniversaries, recurring events, or historical context.

Syntax

/timemachine date: <MM-DD> [channel: #channel]

Parameters

  • date (required): Date in MM-DD format (e.g., 01-31)
  • channel (optional): Limit results to specific channel

Examples

View today's history:

/timemachine date: 01-31

Channel-specific history:

/timemachine date: 12-25 channel: #announcements

Search Best Practices

Use Natural Language

TeaL;DR understands context and meaning. Write queries as you would ask a person.

❌ Less effective:

bug fix

✅ More effective:

what bugs were fixed last week?

Be Specific

Include relevant details to narrow down results.

❌ Too vague:

meeting

✅ More specific:

sprint planning meeting decisions

Use Filters

Combine query with channel and user filters to quickly find what you need in large servers.

← InstallationAnalytics Commands →