chore: add claude file

[nimarb]

Important

Add .claude/settings.json for Bash permissions and CLAUDE.md for Claude Code guidance in Langfuse SDK.

• New Files:
  • Adds .claude/settings.json to configure Bash command permissions for Claude Code.
  • Adds CLAUDE.md to provide guidance on using Claude Code with the Langfuse Python SDK.
• Permissions:
  • .claude/settings.json allows specific Bash commands: find, rg, grep, ls, cat, head, tail.
• Documentation:
  • CLAUDE.md includes project overview, development commands, architecture, configuration, testing notes, important files, API generation, testing guidelines, and Python code rules.

^{This description was created by for 0d5204f. You can customize this summary. It will automatically update as commits are pushed.}

Disclaimer: Experimental PR review

Greptile Summary

This PR appears to be adding or modifying a CLAUDE.md file based on the title "chore: add claude file" and branch name referencing LFE-5944. However, the changed files data is not available in the review context, making it impossible to analyze the specific content being added or modified.

From the repository structure, a CLAUDE.md file already exists in the root directory of langfuse/langfuse-python, so this could be either:

• Adding new content to an existing CLAUDE.md file
• Creating a new CLAUDE.md file in a different location
• Modifying the existing CLAUDE.md file

Without access to the actual file changes, I cannot determine the purpose, content, or integration of these modifications with the rest of the codebase.

Confidence score: 0/5

• This PR cannot be safely reviewed due to missing file change information
• Unable to assess any potential issues without seeing the actual modifications
• All files need attention since the changed files data is unavailable for analysis

[greptile-apps]

_{No files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[hassiebp]

Thanks for adding these! Can we remove the permissions from the repo?

I prefer to keep the permissions up to each developer rather than having project wide defaults. For some commands, a developer confirmation should be done. E.g. here we are allowing all cat commands for all files, claude might decide to read .env (cat .env) and send to LLM which we can catch if it requires dev confirmation

[hassiebp]

You can track your local permissions in a settings.local.json