iflytek/astron-agent

Summary I'd like to propose adding Langfuse integration to astron-agent, so users get built-in observability, tracing, evaluation, and cost monitoring for their agentic workflows. Background astron-agent is an enterprise-grade, commercial-friendly agentic workflow platform for building next-generation SuperAgents (now part of the CNCF Landscape 🎉). As multi-agent workflows become more complex in production, operators need deep visibility into every LLM call, tool invocation, retrieval step, and inter-agent handoff. Langfuse is the leading open-source LLM engineering platform. It provides: Hierarchical tracing — capture every LLM call, tool use, retrieval, and agent step in a nested trace view. Cost & latency monitoring — track token usage, per-model costs, and end-to-end latency over time. Evaluation framework — run model-based evaluations (LLM-as-a-judge), custom scoring, and user feedback on traces. Prompt management — version, deploy, and compare prompts centrally. Data

Expand the documentation FAQ 📖 The FAQ pages — docs/faq.md (English) and docs/zh/faq.md (中文) — are a high-traffic landing spot for new users. Help us grow them with real questions people hit. What to do Pick one or two common questions — good sources are Discussions, recently closed issues, or anything that tripped you up during setup. Add a clear question + answer to docs/faq.md (English). Mirror the same entry in docs/zh/faq.md (中文) at the same position. Only comfortable in one language? Add that one and say so in your PR — someone can add the other. Preview locally: cd docs && npm run docs:dev Good candidates Common deployment / environment-variable pitfalls "Which model do I need and where do I put the credentials?" How to import a workflow from the examples gallery Differences between the deployment guide variants (with/without auth, with RPA) Small, self-contained, and genuinely useful — a perfect first PR. Tip: every page has an "Edit this page on GitHu

Show preview.png thumbnails in the examples gallery 🖼️ The examples gallery currently renders text-only cards. The example spec already reserves an optional preview.png per example — let's render it so cards get a screenshot of the workflow canvas or its output. Scope Gallery component — update docs/.vitepress/theme/ExamplesGallery.vue to show a thumbnail when the example has a preview.png, with a graceful text-only fallback when it doesn't. Data loader — update docs/.vitepress/examples.data.ts to expose whether each example has a preview.png and a URL the page can load (e.g. the GitHub raw URL …/raw/main/examples/<id>/preview.png). Seed screenshots — add a preview.png to the three existing seed examples (history-knowledge-qa, ai-radio-podcast, english-essay-corrector). Verify cd docs && DOCS_BASE=/astron-agent/ npm run docs:build Confirm cards with a preview.png show the image and cards without one still render cleanly. Good for someone comfortable with a bit of Vue +

Contribute a workflow example 🧩 The community examples gallery showcases reusable Astron Agent workflows that anyone can import and adapt. Adding one is a great first contribution — and you'll show up as a project contributor. What you need A workflow you've built in Astron Agent that does something useful Its exported DSL (workflow.yml) Steps Copy the template: cp -r examples/TEMPLATE examples/<your-example-id> Drop in your exported workflow.yml. Fill in README.md (frontmatter + description) — see examples/README.md for the field list. Scrub secrets ⚠️ — exported DSL can embed API keys / app ids / tokens. Replace them with YOUR_* placeholders. (CI checks this automatically.) Open a PR. The Examples Lint check validates your frontmatter and scans for secrets. Prefer a guided submission without using Git? Use the 🧩 Submit a Workflow Example issue form instead. Not sure what to build? Browse the existing examples for inspiration — translators, summarizers, content g

Help translate the Astron Agent docs 🌏 Our documentation site now uses a standard VitePress i18n layout: English is the default at the root, and each language mirrors it under its own folder (Simplified Chinese already lives under docs/zh/). Adding a language is one of the highest-impact, lowest-barrier ways to contribute — and you'll show up as a project contributor. We're looking for translators for: 🇯🇵 Japanese (ja) 🇰🇷 Korean (ko) 🇪🇸 Spanish (es) 🇫🇷 French (fr) …or propose another language you can maintain. How it works Each language is a folder under docs/ that mirrors the English pages with identical relative paths (e.g. docs/ja/guide/quick-start.md mirrors docs/guide/quick-start.md). The full workflow — running the site locally, where pages go, and how to register a new locale — is in the Contribute to the Docs guide. To get involved Comment below with the language you'd like to work on (and, if you want, which page you'll start with) so we d