GitXplorerGitXplorer
a

headlong

public
18 stars
3 forks
1 issues

Commits

List of commits on branch main.
Verified
cf17b60145d51d4c557a257f92e9021a20625da4

Update README.md

aandyk committed 7 months ago
Verified
709896474f5c5679ea9ab029f77e3d66042d262d

Update README.md

aandyk committed 7 months ago
Verified
cce909078901738cd12da20a7cdd2710b946f646

Update README.md

aandyk committed 7 months ago
Verified
15fffd51bbe6778400ef7f37db1184a439809259

Update README.md

aandyk committed 7 months ago
Verified
084f47bfcac8b21bd862c7e18bce9460931392af

Update README.md

aandyk committed 7 months ago
Verified
6ed1d601ebc20cb6b1a221f1e82b74868500d98c

Tweaks to README.md

aandyk committed 7 months ago

README

The README file for this repository.

Headlong is a framework for human users to create and curate high quality chain-of-thought datasets and use them in AI Agents. screenshot of Headlong webapp

Architectural Parts

The webapp frontend is in packages/webapp - it's a vite Typescript project.

The webapp depends on a thought_server (found in packages/thought_server) which is written in Python and wraps LLMs for thought generation.

The environment is in packages/env - it's a node daemon written in Typescript. you should run this in a docker container or EC2 instance.

The environment uses GPT4 function calling to use tools, including a terminalServer that itself wraps ht (headless terminal).

The webapp communicates with the environment via a Supabase thoughts table and Supabase's realtime system.

install and run

### == ht ==
# Download latest ht binary from https://github.com/andyk/ht/releases/latest
# and make sure it is on your path.

### == thought server ==
# in a new terminal 
cd packages/thought_server
# You need python >= 3.10 since we use the `match` syntax. 
virtualenv venv
. ./venv/bin/activate
pip install -r requirements.txt
# make sure you create or get a copy of thinkers.yaml and put it into ./
. ./launch.sh

### == headlong UI webapp ==
cd packages/webapp
npm install
npm run dev

## By default your webapp will connect to the main env running in EC2
## via supabase realtime. If you want to override that and use a local
## env, then you'll need to run the terminalServer and env locally.
## We strongly recommend you run these in a docker instance.

### == terminal server ==
# in a new terminal 
cd packages/env
npm install
npm run terminalServer

### == env daemon ==
# in a new terminal 
cd packages/env
npm run env