langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-21 11:55:23 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #3849] docs: add Future AGI integration provider #3861

New Issue
Open
opened 2026-06-05 18:53:23 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:53:23 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3849
Author: @SuhaniNagpal7
Created: 5/3/2026
Status: 🔄 Open

Base: main ← Head: docs/add-traceai-langchain

📝 Commits (3)

  • 470f6eb docs: add Future AGI integration provider
  • 32a6e40 Merge branch 'main' into docs/add-traceai-langchain
  • ac54e19 Merge branch 'main' into docs/add-traceai-langchain

📊 Changes

2 files changed (+90 additions, -0 deletions)

View changed files

📝 src/oss/python/integrations/providers/all_providers.mdx (+8 -0)
➕ src/oss/python/integrations/providers/futureagi.mdx (+82 -0)

📄 Description

Overview

Adds Future AGI as a LangChain integration provider page. Future AGI is an open-source AI tracing and evaluation platform built on OpenTelemetry. The traceAI-langchain package auto-instruments LangChain (and LangGraph) and exports traces to any OTLP-compatible backend.

Type of change

Type: New documentation page

Summary

  • Adds src/oss/python/integrations/providers/futureagi.mdx — provider overview page modeled on the existing observability-vendor pages (langfuse.mdx, arize.mdx, helicone.mdx)
  • Adds a <Card> for Future AGI in src/oss/python/integrations/providers/all_providers.mdx, alphabetically between Friendli and Galaxia
  • Covers installation, env vars (with link to the Future AGI dashboard for credentials), tracer registration, instrumentation, a runnable LangChain example, and the [langgraph] extra
  • Points JavaScript users at the npm package @traceai/langchain

Verification

  • Code examples were executed end-to-end against the published traceAI-langchain==0.1.12 and langchain-openai. The chain ran, the LLM call returned, and spans flushed to the FAGI OTLP endpoint without error.
  • make lint_prose FILES="..." (Vale) — 0 errors, 0 warnings, 0 suggestions on both files.
  • All H2s use imperative verb form per the contributing guide; em-dashes have no surrounding spaces.

Checklist

  • I have read the contributing guidelines, including the language policy
  • I have tested my changes locally using docs dev (Mintlify dev server not run; Vale lint and live code execution were performed instead)
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed (not needed — individual providers are surfaced via all_providers.mdx, matching the convention used by Langfuse, Arize, Helicone, etc.)

Additional notes

  • Naming follows the existing observability-vendor convention (file = company name, lowercase): futureagi.mdx, similar to langfuse.mdx.
  • This PR was prepared with the help of an AI coding assistant (Claude Code). Code samples were verified by execution.

Links

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/3849 **Author:** [@SuhaniNagpal7](https://github.com/SuhaniNagpal7) **Created:** 5/3/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/add-traceai-langchain` --- ### 📝 Commits (3) - [`470f6eb`](https://github.com/langchain-ai/docs/commit/470f6eb81259bdfe95d8b6880d6ee00730274e7c) docs: add Future AGI integration provider - [`32a6e40`](https://github.com/langchain-ai/docs/commit/32a6e402a9c1e3f39a63a5d245bd3ab55211c273) Merge branch 'main' into docs/add-traceai-langchain - [`ac54e19`](https://github.com/langchain-ai/docs/commit/ac54e1923180d81a5a26ec0ab9f67397fc810251) Merge branch 'main' into docs/add-traceai-langchain ### 📊 Changes **2 files changed** (+90 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/python/integrations/providers/all_providers.mdx` (+8 -0) ➕ `src/oss/python/integrations/providers/futureagi.mdx` (+82 -0) </details> ### 📄 Description ## Overview Adds [Future AGI](https://futureagi.com) as a LangChain integration provider page. Future AGI is an open-source AI tracing and evaluation platform built on OpenTelemetry. The `traceAI-langchain` package auto-instruments LangChain (and LangGraph) and exports traces to any OTLP-compatible backend. ## Type of change **Type:** New documentation page ## Summary - Adds `src/oss/python/integrations/providers/futureagi.mdx` — provider overview page modeled on the existing observability-vendor pages (`langfuse.mdx`, `arize.mdx`, `helicone.mdx`) - Adds a `<Card>` for Future AGI in `src/oss/python/integrations/providers/all_providers.mdx`, alphabetically between Friendli and Galaxia - Covers installation, env vars (with link to the Future AGI dashboard for credentials), tracer registration, instrumentation, a runnable LangChain example, and the `[langgraph]` extra - Points JavaScript users at the npm package [`@traceai/langchain`](https://www.npmjs.com/package/@traceai/langchain) ## Verification - Code examples were executed end-to-end against the published `traceAI-langchain==0.1.12` and `langchain-openai`. The chain ran, the LLM call returned, and spans flushed to the FAGI OTLP endpoint without error. - `make lint_prose FILES="..."` (Vale) — 0 errors, 0 warnings, 0 suggestions on both files. - All H2s use imperative verb form per the contributing guide; em-dashes have no surrounding spaces. ## Checklist - [x] I have read the [contributing guidelines](README.md), including the [language policy](https://docs.langchain.com/oss/python/contributing/overview#language-policy) - [ ] I have tested my changes locally using `docs dev` (Mintlify dev server not run; Vale lint and live code execution were performed instead) - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed (not needed — individual providers are surfaced via `all_providers.mdx`, matching the convention used by Langfuse, Arize, Helicone, etc.) ## Additional notes - Naming follows the existing observability-vendor convention (file = company name, lowercase): `futureagi.mdx`, similar to `langfuse.mdx`. - This PR was prepared with the help of an AI coding assistant (Claude Code). Code samples were verified by execution. ## Links - PyPI: https://pypi.org/project/traceAI-langchain/ - npm: https://www.npmjs.com/package/@traceai/langchain - Source: https://github.com/future-agi/traceAI/tree/main/python/frameworks/langchain - Full integration guide: https://docs.futureagi.com/docs/integrations/traceai/langchain --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:53:23 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#3861
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?