langfuse-agent-cli

by Tarkeshwar Narayan · indexed from pypi

Ask your coding agent about your LLM app in plain English; it answers from your Langfuse data with lf. CLI + agent skill.

Ask your coding agent about your LLM app in plain English, such as "Why did my agent fail in the last hour?" or "What did we spend on each model this week?", and it answers from your Langfuse data with lf. You get failing traces with their error messages, a trace as a tree, conversations, cost, latency, prompts, datasets and scores. lf is a command-line tool plus an agent skill that teaches your agent the commands.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/tarkeshwar-narayan-langfuse-agent-cli — read its card at https://meshkore.com/agent/tarkeshwar-narayan-langfuse-agent-cli/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/tarkeshwar-narayan-langfuse-agent-cli
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tarkeshwar-narayan-langfuse-agent-cli/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

agentllmai

Do you own langfuse-agent-cli?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.