Skip to content

Commit 6aedaae

Browse files
authored
docs: Add open swe FAQ section (#112)
1 parent 1fdbdca commit 6aedaae

File tree

2 files changed

+47
-0
lines changed

2 files changed

+47
-0
lines changed

src/docs.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -309,6 +309,12 @@
309309
"labs/swe/setup/monorepo",
310310
"labs/swe/setup/ci"
311311
]
312+
},
313+
{
314+
"group": "FAQ",
315+
"pages": [
316+
"labs/swe/faq"
317+
]
312318
}
313319
]
314320
}

src/labs/swe/faq.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: "FAQ"
3+
description: "Frequently Asked Questions"
4+
---
5+
6+
<Accordion title="How much does an end to end Open SWE run cost?">
7+
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.
8+
9+
For most tasks, you can expect to pay between $0.50 -> $3.00 when using Claude Sonnet 4.
10+
For the same tasks running on Claude Opus 4, you can expect to pay between $1.50 - $6.00.
11+
12+
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.
13+
</Accordion>
14+
15+
<Accordion title="Does Open SWE automatically cache tokens?">
16+
Yes. When using Anthropic models, all input tokens are cached on Anthropic's servers.
17+
</Accordion>
18+
19+
<Accordion title="My run failed midway through. What now?">
20+
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.
21+
22+
If a run fails, you will need to start over.
23+
</Accordion>
24+
25+
<Accordion title="Can I use Open SWE in a production environment?">
26+
Yes! We've been using Open SWE internally at LangChain for a while now, and it's been giving us great results.
27+
28+
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.
29+
</Accordion>
30+
31+
<Accordion title="I installed Open SWE on a repository in my organization, but it doesn't show up in the UI. Why?">
32+
Some GitHub organizations require administrator approval to install GitHub apps. Please reach out to an administrator in your organization to approve the installation request.
33+
</Accordion>
34+
35+
<Accordion title="What sandbox environment is Open SWE running in?">
36+
Open SWE's sandbox environment is powered by [Daytona.io](https://daytona.io).
37+
</Accordion>
38+
39+
<Accordion title="Can I contribute to Open SWE?">
40+
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.
41+
</Accordion>

0 commit comments

Comments
 (0)