---
title: Langfuse Community Hour
description: Guide on scheduling and planning the Langfuse Community Hour.
---

# Langfuse Community Hour

## What is the Langfuse Community Hour?

The Langfuse Community Hour is our regular meetup for answering user questions, sharing ideas, experiences, and best practices.

We keep these sessions fun and hands-on, helping users with topics such as:

- Questions about Langfuse
- Improving your evaluation & testing setup
- General chat about building LLM applications

## How to schedule the Langfuse Community Hour?

1. **Create a new event in our Langfuse Lu.ma Calendar**: https://luma.com/langfuse
   - Past events can be cloned when clicking on "manage event" -> "more" -> "Clone Event".
   - Add a "Blast" to the event that reminds people 2 hours before the event.
   - Use the Lu.ma invite function to invite all past participants of our community hour.

2. **Create a new Google Calendar invite** to have a Google Meet link for the event.
   - Change the permissions of the event so everyone can join without host approval (meeting access type = open).
   - Add all participants from the Langfuse team as meeting hosts.

3. **Remind our community on Social media** about the community hour.
   - Use our social tool assembly to post a reminder on Monday.
     - [Example post](https://www.linkedin.com/feed/update/urn:li:share:7396844001577881601/)
   - Post a short message in our Discord `#general` channel.
     - [Example message](https://discord.com/channels/1111061815649124414/1111063198989307964/1440763518046441725)
   - [Social media image](https://www.figma.com/design/5mz0YBp9oQH3wfikRXVLOW/Langfuse-Media?node-id=3463-411&t=BtMggQdKPIilwCnh-4)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/handbook/devrel/community-hour.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.