Public launch

Signed-off-by: Dmitri Saberi <[email protected]>

Author: dmitrisaberi

.gitignore

@@ -22,4 +22,5 @@ dist-ssr
 *.njsproj
 *.sln
 *.sw?
-.env
+.env
+.vercel

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-## Contributing to Flux
+## Contributing to Branches
 
-Thanks for your interest in improving Flux!
+Thanks for your interest in improving Branches!
 
 There are multiple opportunities to contribute at any level. It doesn't matter if you are just getting started with Rust or are the most weathered expert, we can use your help.
 
@@ -11,7 +11,7 @@ It should be considered as a guide to help you navigate the process.
 
 ### Code of Conduct
 
-Flux adheres to the [Rust Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct) (even though it's not a Rust project). This code of conduct describes the _minimum_ behavior expected from all contributors.
+Branches adheres to the [Rust Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct) (even though it's not a Rust project). This code of conduct describes the _minimum_ behavior expected from all contributors.
 
 Instances of violations of the Code of Conduct can be reported by contacting the team at [[email protected]](mailto:[email protected]).
 
@@ -20,7 +20,7 @@ Instances of violations of the Code of Conduct can be reported by contacting the
 There are fundamentally four ways an individual can contribute:
 
 1. **By opening an issue:** For example, if you believe that you have uncovered a bug
-   in Flux, creating a new issue in the issue tracker is the way to report it.
+   in Branches, creating a new issue in the issue tracker is the way to report it.
 2. **By adding context:** Providing additional context to existing issues,
    such as screenshots, code snippets and helps resolve issues.
 3. **By resolving issues:** Typically this is done in the form of either
@@ -55,7 +55,7 @@ If you have examples of other tools that have the feature you are requesting, pl
 
 ### Resolving an issue
 
-Pull requests are the way concrete changes are made to the code and dependencies of Flux.
+Pull requests are the way concrete changes are made to the code and dependencies of Branches.
 
 Even tiny pull requests, like fixing wording, are greatly appreciated. Before making a large change, it is usually
 a good idea to first open an issue describing the change to solicit feedback and guidance. This will increase
@@ -82,7 +82,7 @@ Keep an eye out for comments from code owners to provide guidance on conflicting
 
 #### Reviewing pull requests
 
-**Any Flux community member is welcome to review any pull request**.
+**Any Branches community member is welcome to review any pull request**.
 
 All contributors who choose to review and provide feedback on pull requests have a responsibility to both the project and individual making the contribution. Reviews and feedback must be helpful, insightful, and geared towards improving the contribution as opposed to simply blocking it. If there are reasons why you feel the PR should not be merged, explain what those are. Do not expect to be able to block a PR from advancing simply because you say "no" without giving an explanation. Be open to having your mind changed. Be open to working _with_ the contributor to make the pull request better.
 
@@ -98,8 +98,8 @@ It is tempting to micro-optimize and make everything about relative performance,
 
 Focus first on the most significant aspects of the change:
 
-1. Does this change make sense for Flux?
-2. Does this change make Flux better, even if only incrementally?
+1. Does this change make sense for Branches?
+2. Does this change make Branches better, even if only incrementally?
 3. Are there clear bugs or larger scale issues that need attending?
 4. Are the commit messages readable and correct? If it contains a breaking change, is it clear enough?
 
@@ -109,15 +109,15 @@ When changes are necessary, _request_ them, do not _demand_ them, and **do not a
 
 Specific performance optimization techniques, coding styles and conventions change over time. The first impression you give to a new contributor never does.
 
-Nits (requests for small changes that are not essential) are fine, but try to avoid stalling the pull request. Most nits can typically be fixed by the Flux maintainers merging the pull request, but they can also be an opportunity for the contributor to learn a bit more about the project.
+Nits (requests for small changes that are not essential) are fine, but try to avoid stalling the pull request. Most nits can typically be fixed by the Branches maintainers merging the pull request, but they can also be an opportunity for the contributor to learn a bit more about the project.
 
 It is always good to clearly indicate nits when you comment, e.g.: `nit: change foo() to bar(). But this is not blocking`.
 
 If your comments were addressed but were not folded after new commits, or if they proved to be mistaken, please, hide them with the appropriate reason to keep the conversation flow concise and relevant.
 
 ##### Be aware of the person behind the code
 
-Be aware that _how_ you communicate requests and reviews in your feedback can have a significant impact on the success of the pull request. Yes, we may merge a particular change that makes Flux better, but the individual might just not want to have anything to do with Flux ever again. The goal is not just having good code.
+Be aware that _how_ you communicate requests and reviews in your feedback can have a significant impact on the success of the pull request. Yes, we may merge a particular change that makes Branches better, but the individual might just not want to have anything to do with Branches ever again. The goal is not just having good code.
 
 ##### Abandoned or stale pull requests
 

README.md

@@ -1,47 +1,87 @@
 <div align="center">
-  <h1 align="center">Flux</h1>
-  <p align="center">
-    Graph-based LLM power tool for exploring many completions in parallel.
-    <br />
-    <br />
-    <a href="https://twitter.com/transmissions11/status/1640775967856803840">Announcement</a>
-    ·
-    <a href="http://flux.paradigm.xyz">Try Online</a>
-    ·
-    <a href="https://github.com/paradigmxyz/flux/issues">Report a Bug</a>
-  </p>
+
+<img src="./docs/source/_static/logo.png" alt="Branches Logo" width=200></img>
+
+# Branches
+
+Prototype advanced LLM algorithms for reasoning and planning.
+
+[Try Online](http://code-gen-tree.vercel.app) •
+[Report a Bug](https://github.com/normal-computing/branches/issues) •
+[Stay tuned](#stay-tuned-for)
+
 </div>
 
-<br />
+![Branches in action: Tree-search visualization for code generation with self-correction in the HumanEval benchmark](https://storage.googleapis.com/normal-blog-artifacts/systerm2/tot_demo.gif)
 
-![A screenshot of a Flux workspace.](/public/meta-full.png)
+***Tree-search visualization during code generation.** We visualize a reasoning algorithm which learns from feedback, automatically correcting itself by analyzing error tracebacks to refine its solutions. In this case, we benchmark Python programming problems from the HumanEval dataset.*
 
 ## About
 
-Flux is a power tool for interacting with large language models (LLMs) that **generates multiple completions per prompt in a tree structure and lets you explore the best ones in parallel.** 
+Branches is an AI tool for graph-based prototyping of advanced algorithms for LLM reasoning and planning -- like Tree of Thoughts and Reflexion. Branches is adapted from [Flux](https://github.com/paradigmxyz/flux).
 
-Flux's tree structure allows you to:
+Designed for researchers and developers, it allows users to directly interact with AI reasoning processes, streamlining the exploration of complex coding challenges and strategic problem-solving.
 
-- Get a wider variety of creative responses
+### Code Generation (HumanEval)
 
-- Test out different prompts with the same shared context
+Branches automatically expands decision trees to solve programming problems from the [HumanEval dataset](https://huggingface.co/datasets/openai_humaneval), visualizing reasoning chains and facilitating self-correction through error tracebacks. This is found on the `main` branch and is currently hosted. 
 
-- Use inconsistencies to identify where the model is uncertain 
+### Game of 24
+Branches includes a specialized evaluation mechanism for the [Game of 24 puzzle](https://en.wikipedia.org/wiki/24_(puzzle)), leveraging a scoring system to enhance breadth-first search (BFS) by prioritizing promising paths. This is found on the `game-of-24` branch.
 
-It also provides a robust set of keyboard shortcuts, allows setting the system message and editing GPT messages, autosaves to local storage, uses the OpenAI API directly, and is 100% open source and MIT licensed.
+## Features
+
+- [x] 🌳 **Automated Tree Expansion**: Leveraging Tree of Thoughts for dynamic expansion in problem-solving.
+- [x] 🧠 **Pre-loaded Prompts**: Curated for search-based reasoning to solve specific problems.
+- [x] 💻 **Code Interpretation**: Instant execution and error analysis for self-correcting AI-generated code.
+- [x] 🔍 **Scoring Mechanism**: Advanced BFS for the Game of 24 with node evaluation for search optimization.
+- [x] 📊 **Interactive Visualization**: Graphical representation of tree searches for easy analysis and education. Largely adapted from [Flux](https://github.com/paradigmxyz/flux).
 
 ## Usage
 
-Visit [flux.paradigm.xyz](https://flux.paradigm.xyz) to try Flux online or follow the instructions below to run it locally.
+To get started with Branches, you can either visit [code-gen-tree.vercel.app](https://code-gen-tree.vercel.app) for the hosted version or run it locally by following the instructions below.
+
+## Deploy to Vercel
+```sh
+npm i -g vercel
+vercel
+```
 
 ## Running Locally
+For local development, checkout the `local-dev` branch. This is slightly modified to use Flask to serve the code interpreter API.
+
+Setup repo
+```sh
+git clone https://github.com/normal-computing/branches.git
+git checkout local-dev
+```
 
+**Frontend (User Interface):**
 ```sh
-git clone https://github.com/paradigmxyz/flux.git
 npm install
 npm run dev
 ```
 
+**Backend (Code Interpreter):**
+```
+pip install -r backend/requirements.txt
+python backend/interpreter.py
+```
+
+## Stay Tuned For
+
+Our commitment to enhancing Branches continues, with exciting new developments on the way:
+
+- More reasoning and planning algorithms beyond the defaults ([#10](https://github.com/normal-computing/branches/issues/10))
+- Node Value Editing and Regenerate Subtree Functionality ([#5](https://github.com/normal-computing/branches/issues/5))
+- UI Color Fixes and Customization Features ([#6](https://github.com/normal-computing/branches/issues/6))
+- Address Model/UI Timeout Issues ([#7](https://github.com/normal-computing/branches/issues/7))
+- Enhance Game of 24 Logic, Model Cost Tracking, and Prompt Engineering ([#8](https://github.com/normal-computing/branches/issues/8))
+
 ## Contributing
 
-See the [open issues](https://github.com/paradigmxyz/flux/issues) for a list of proposed features (and known issues).
+Your contributions make Branches better. Whether it’s bug reports, new features, or feedback, we welcome it all! Report bugs or request features by creating an issue [here](https://github.com/normal-computing/Branches/issues).
+
+## License
+
+Branches is open-source and continues to uphold the [MIT license](LICENSE).

api/execute.py

@@ -0,0 +1,40 @@
+from http import HTTPStatus
+import json
+from concurrent.futures import ThreadPoolExecutor
+from human_eval.execution import check_correctness
+from flask import Flask, request, jsonify
+
+
+app = Flask(__name__)
+
+executor = ThreadPoolExecutor(max_workers=5)
+
+
+@app.route("/execute", methods=["POST"])
+async def execute():
+    data = request.json
+
+    problem = data.get("problem", "")
+    completion = data.get("completion", "")
+    timeout = data.get("timeout", 5.0)
+    args = (problem, completion, timeout)
+
+    if not completion:
+        response = jsonify({"error": "No completion provided"})
+        response.status_code = HTTPStatus.BAD_REQUEST
+        return response
+
+    try:
+        future = executor.submit(check_correctness, problem, completion, timeout)
+        result = future.result()
+        return jsonify({"result": result})
+    except Exception as e:
+        response = jsonify({"error": str(e)})
+        response.status_code = HTTPStatus.INTERNAL_SERVER_ERROR
+        return response
+
+
+# check if a 500 error code is thrown
+@app.errorhandler(500)
+def internal_error(error):
+    return "500 error: {}".format(str(error)), 500

api/requirements.txt

@@ -0,0 +1,3 @@
+openai
+git+https://github.com/arunpatro/human-eval.git@pipgit 
+Flask

docs/source/_static/logo.png

@@ -5,24 +5,24 @@
     <link rel="icon" type="image/svg+xml" href="/favicon.ico" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
 
-    <title>Flux</title>
+    <title>Branches</title>
 
     <meta name="description" content="LLM power tool." />
 
-    <meta property="og:title" content="Flux" />
+    <meta property="og:title" content="Branches" />
     <meta property="og:url" content="https://flux.paradigm.xyz" />
     <meta property="og:image" content="https://flux.paradigm.xyz/meta.jpg" />
     <meta property="og:description" content="LLM power tool." />
     <meta property="og:type" content="website" />
 
     <meta name="twitter:card" content="summary_large_image" />
-    <meta name="twitter:title" content="Flux" />
+    <meta name="twitter:title" content="Branches" />
     <meta name="twitter:description" content="LLM power tool." />
     <meta name="twitter:image" content="https://flux.paradigm.xyz/meta.jpg" />
 
     <meta name="theme-color" content="#ffffff" />
 
-    <meta name="apple-mobile-web-app-title" content="Flux" />
+    <meta name="apple-mobile-web-app-title" content="Branches" />
     <meta name="apple-mobile-web-app-capable" content="yes" />
     <meta name="apple-mobile-web-app-status-bar-style" content="default" />
   </head>