LangGraph migration

pipeline/core/builder.py

@@ -2,6 +2,7 @@
 
 import json
 import logging
+import re
 import shutil
 from pathlib import Path
 
@@ -52,6 +53,12 @@ def __init__(self, src_dir: Path, build_dir: Path) -> None:
             ".js",
         }
 
+        # Mapping of language codes to full names for URLs
+        self.language_url_names = {
+            "python": "python",
+            "js": "javascript",
+        }
+
     def build_all(self) -> None:
         """Build all documentation files from source to build directory.
 
@@ -127,6 +134,39 @@ def _convert_yaml_to_json(self, yaml_file_path: Path, output_path: Path) -> None
             logger.exception("Failed to convert %s to JSON", yaml_file_path)
             raise
 
+    def _rewrite_oss_links(self, content: str, target_language: str | None) -> str:
+        """Rewrite /oss/ links to include the target language.
+
+        Args:
+            content: The markdown content to process.
+            target_language: Target language ("python" or "js") or None to skip rewriting.
+
+        Returns:
+            Content with rewritten links.
+        """
+        if not target_language:
+            return content
+
+        def rewrite_link(match: re.Match) -> str:
+            """Rewrite a single link match."""
+            pre = match.group(1)  # Everything before the URL
+            url = match.group(2)  # The URL
+            post = match.group(3)  # Everything after the URL
+
+            # Only rewrite absolute /oss/ paths
+            if url.startswith("/oss/"):
+                parts = url.split("/")
+                # Insert full language name after "oss"
+                parts.insert(2, self.language_url_names[target_language])
+                url = "/".join(parts)
+
+            return f"{pre}{url}{post}"
+
+        # Match markdown links and HTML links/anchors
+        # This handles both [text](/oss/path) and <a href="/oss/path">
+        pattern = r'(\[.*?\]\(|\bhref="|")(/oss/[^")\s]+)([")\s])'
+        return re.sub(pattern, rewrite_link, content)
+
     def _process_markdown_content(
         self, content: str, file_path: Path, target_language: str | None = None
     ) -> str:
@@ -144,10 +184,15 @@ def _process_markdown_content(
             The processed markdown content.
         """
         try:
-            # Apply markdown preprocessing
-            return preprocess_markdown(
+            # First apply standard markdown preprocessing
+            content = preprocess_markdown(
                 content, file_path, target_language=target_language
             )
+
+            # Then rewrite /oss/ links to include language
+            content = self._rewrite_oss_links(content, target_language)
+
+            return content
         except Exception:
             logger.exception("Failed to process markdown content from %s", file_path)
             raise
@@ -577,4 +622,4 @@ def _copy_shared_files(self) -> None:
                 shutil.copy2(file_path, output_path)
                 copied_count += 1
 
-        logger.info("✅ Shared files copied: %d files", copied_count)
+        logger.info("✅ Shared files copied: %d files", copied_count)

src/labs/swe/index.mdx

@@ -21,7 +21,7 @@ The agent can be used through a web interface or triggered automatically via Git
   <Card title="Setup" icon="robot" href="/labs/swe/setup/intro">
     How to set up Open SWE for development
   </Card>
-  <Card title="Examples" icon="database" href="/labs/swe/examples">
+  <Card title="Examples" icon="database" href="/labs/swe/usage/examples">
     Examples of tasks you can try out
   </Card>
   <Card title="Usage" icon="database" href="/labs/swe/usage/intro">

src/labs/swe/usage/intro.mdx

@@ -14,7 +14,7 @@ Open SWE provides two primary ways to interact with the coding agent, each desig
     Interactive chat interface with manual and auto modes for direct agent
     communication
   </Card>
-  <Card title="GitHub Webhooks" icon="webhook" href="/labs/swe/usage/webhook">
+  <Card title="GitHub Webhooks" icon="webhook" href="/labs/swe/usage/github#github-webhook-integration">
     Automated triggers through GitHub issue labels for seamless repository
     integration
   </Card>
@@ -42,7 +42,7 @@ You can explore Open SWE's capabilities using our hosted demo at [swe.langchain.
 <Tip>
   Start with the [Web Interface guide](/labs/swe/usage/ui) to understand Open
   SWE's core capabilities, then explore [GitHub
-  Webhooks](/labs/swe/usage/webhook) for automated integration into your
+  Webhooks](/labs/swe/usage/github#github-webhook-integration) for automated integration into your
   development workflow.
 </Tip>
 

src/oss/use-functional-api.mdx

@@ -1677,7 +1677,7 @@ for await (const chunk of await workflow.stream([inputMessage2], {
 
 ## Workflows
 
-* [Workflows and agent](/oss/workflows-and-agents) guide for more examples of how to build workflows using the Functional API.
+* [Workflows and agent](/oss/agentic-architectures) guide for more examples of how to build workflows using the Functional API.
 
 ## Integrate with other libraries