Sync OpenSWE Documentation Files (#127)

This PR syncs documentation files from the OpenSWE repository.
  
  **Changes:**
  - Updated MDX files from `apps/docs/`
  - Target directory: `src/labs/swe/`
  - Updated images from `apps/docs/images/`
  - Target directory: `src/images/`
  - Source commit: 0a41c0ac0b9f4d148da85699876d1f66d1c79164
  - Synced at 2025-08-06 18:18:37 UTC
  
  **Auto-generated by:** OpenSWE Documentation Sync Workflow

Co-authored-by: OpenSWE Bot <[email protected]>

Author: bracesproul

src/images/ui-screenshot.png

@@ -0,0 +1,41 @@
+---
+title: FAQ
+description: Frequently Asked Questions
+---
+
+<Accordion title="How much does an end to end Open SWE run cost?">
+  The cost per run varies greatly based on the complexity of the task, the size of the repository, and the number of files that need to be changed.
+
+  For most tasks, you can expect to pay between `$0.50` -> `$3.00` when using Claude Sonnet 4.
+  For the same tasks running on Claude Opus 4/4.1, you can expect to pay between `$1.50` -> `$9.00`.
+
+  Always remember to monitor your runs if you're cost conscious. The most expensive run I've seen Open SWE complete was ~50M Opus 4 tokens, costing `$25.00`.
+</Accordion>
+
+<Accordion title="Does Open SWE automatically cache tokens?">
+  Yes. When using Anthropic models, all input tokens are cached on Anthropic's servers.
+</Accordion>
+
+<Accordion title="My run failed midway through. What now?">
+  We're sorry you're experiencing this! Open SWE will automatically commit any changes it makes to a draft pull request. Please check the draft pull request and make any necessary changes.
+
+  If a run fails, you will need to start over.
+</Accordion>
+
+<Accordion title="Can I use Open SWE in a production environment?">
+  Yes! We've been using Open SWE internally at LangChain for a while now, and it's been giving us great results.
+
+  We recommend forking and deploying Open SWE yourself if you plan on using it in a production environment. For checking out the product, the [demo application](https://swe.langchain.com) will work fine.
+</Accordion>
+
+<Accordion title="I installed Open SWE on a repository in my organization, but it doesn't show up in the UI. Why?">
+  Some GitHub organizations require administrator approval to install GitHub apps. Please reach out to an administrator in your organization to approve the installation request.  
+</Accordion>
+
+<Accordion title="What sandbox environment is Open SWE running in?">
+  Open SWE's sandbox environment is powered by [Daytona.io](https://daytona.io).
+</Accordion>
+
+<Accordion title="Can I contribute to Open SWE?">
+  Yes! We're always looking for contributors to help us improve Open SWE. Feel free to pick up an [open issue](https://github.com/langchain-ai/open-swe/issues) or submit a pull request with a new feature or bug fix.
+</Accordion>

src/labs/swe/faq.mdx

@@ -5,11 +5,6 @@ description: "An introduction to Open SWE"
 
 Open SWE is an open-source cloud-based coding agent built with [LangGraph](https://langchain-ai.github.io/langgraphjs/). It's designed to autonomously understand, plan, and execute code changes across entire repositories.
 
-<Note>
-  Open SWE is currently under active development and is not yet ready for
-  production use.
-</Note>
-
 ## How It Works
 
 Open SWE operates through three specialized LangGraph agents:
@@ -20,6 +15,8 @@ Open SWE operates through three specialized LangGraph agents:
 
 The agent can be used through a web interface or triggered automatically via GitHub webhooks, making it flexible for both interactive development and automated workflows.
 
+![Open SWE UI Screenshot](/images/ui-screenshot.png)
+
 <CardGroup cols={2}>
   <Card title="Setup" icon="robot" href="/labs/swe/setup/intro">
     How to set up Open SWE for development