hdresearch/create

Template repository for framework.

Introduction

This repository includes everything you need to bootstrap an online-enabled, LLM-powered web agent.

Prerequisites

You'll first want to cp .env.example .env and configure your LLM.

Then, to get started hacking, just run npm run dev. To run this repo in production, you can run npm run build && npm run start.

In development, your app is available at http://localhost:5173, talking to the server at http://localhost:3040. By default, in production your app is available at http://localhost.

agent

This folder includes the configuration for your agent, which is powered by your LLM. Your LLM has its own system and agent prompt. Both are configurable here.

app

This folder contains the front-end components of your application, powered by Vite and TypeScript.

The example in this repository is simple: it provides a typed list of restaurants for the West Village of Manhattan, NY.

extensions

In this folder you can configure custom type schemas -- ensuring output from your LLM agent matches a typed response -- and provide an inventory of personal data, should you need credentials to log in to another service or need to share personal information for any purpose in a confidential way.

server

This folder runs an Express server that serves the browser back-end, as well as static hosting if you wish to mount the server in production with the Vite.js front-end build.

It imports your browser customisations in the extensions folder and spins up a browser when requested.

create's Issues

Add continuous integration tests

We had a complete breakage for three days, which is of course not ideal, as a consequence of #4 / hdresearch/nolita#44. We need to have a way to assess if the template still functions; sometimes the shape of our type shifts and the props no longer drill, making exposing the events break, too. Likely what we need is to just run the fetch command against our back-end, using our custom schema, directly, and assess the shape of the core flow.

Part 1 of this is #9.

front-end needs to hit port 80 in prod, not 3040

Just a quick fix to test out soon...

remove @ts-expect-error comments

Our types changed sometime between 1.0.0 and 1.2.0 and they have strange asymmetries now that cause errors when we look for complete vs. failed objective cases in the object. Just need to rewrite some of the unions here to be more clever to prevent oracle errors.

Proper location of schema import

Right now we use a type that isn't quite correct and produces an error in server.ts. I need to drill down again and place it.

npm run start hits an error

This only matters for prod deploys, and it likely is just a mismatch between the dist's entry point and where we've specified it to be. Just gotta build, look, and correct.