You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,7 +137,7 @@ doesn't have an OpenAI API compatible endpoint (like Google or Anthropic) you ca
137
137
138
138
The following sequence diagram illustrates how the request and responses go through optillm.
139
139
140
-

140
+

141
141
142
142
In the diagram:
143
143
-`A` is an existing tool (like [oobabooga](https://github.com/oobabooga/text-generation-webui/)), framework (like [patchwork](https://github.com/patched-codes/patchwork))
@@ -198,7 +198,7 @@ When using Docker, these can be set as environment variables prefixed with `OPTI
198
198
199
199
## Running with Docker
200
200
201
-
optillm can optionally be built and run using Docker and the provided [Dockerfile](./Dockerfile).
201
+
optillm can optionally be built and run using Docker and the provided [Dockerfile](https://github.com/codelion/optillm/blob/main/Dockerfile).

266
+

267
267
268
268
### optillm with Patchwork (July 2024)
269
269
270
270
Since optillm is a drop-in replacement for OpenAI API you can easily integrate it with existing tools and frameworks using the OpenAI client. We used optillm with [patchwork](https://github.com/patched-codes/patchwork) which is an open-source framework that automates development gruntwork like PR reviews, bug fixing, security patching using workflows
271
271
called patchflows. We saw huge performance gains across all the supported patchflows as shown below when using the mixutre of agents approach (moa).
272
272
273
-

273
+

0 commit comments