DevelopmentLocal AI

CheapGPT

CheapGPT website.
CheapGPT, September 2026.

CheapGPT began with a desktop I already had and a question: how much everyday AI work could it handle on its own? The model is Ornith, and llama.cpp runs it on the machine's older Radeon graphics card. I built the application around them: chat, document handling, task presets and a view of what the computer is doing.

Keep one model loaded

On this hardware, switching models costs time and memory, so the application is built around a single model that stays ready. The opening screen goes straight to a conversation.

Quick Chat handles a passing, unsaved question. Signing in adds private conversation history, web search and a separate tool for small calculations and code tasks. Quick and Think expose the model's own modes as a plain choice: an immediate reply, or more time spent on the question.

Send the model less on every turn

A long document changes the job. The passage that matters may sit near the end, or the answer may depend on several sections. CheapGPT keeps the extracted text and works through long material in passes, collecting the parts that bear on the question.

Conversation history gets similar treatment. People wander off and come back to earlier subjects, so the full history is kept, while each turn carries only the parts that belong to the current exchange. Making a modest machine reread everything on every turn would mostly add waiting.

Presets and a visible queue

An empty text box leaves all the work of getting started to the person looking at it. Task presets cover common jobs such as drafting an email, summarizing a meeting, translating text and pulling information out of a document. Each one starts the instruction and asks for the details that task needs.

The Activity panel shows whether a request is waiting its turn, reading a document or being answered. On a machine that sometimes needs a minute, knowing which of those is happening is a lot more reassuring than a spinner.

Cory BoehneLet's talk
Creative full-body development portrait of Cory Boehne
03SOFTWARE CASE STUDIES

Software I've built
and how it works.

I've built tools for maintenance teams and company finances, applications that run on local models, image and story software, and games with a little AI in the cast. The problems range from a missing zero in a spreadsheet to a suspect who mustn't reveal the answer.

Building software since the late nineties.

Business tools, games and image software.

Three places
to start.

A Maximo assistant that has to know which release you run. An arcade where one local model plays a different part in every game. An image tool I built while making the portraits on this site.

Dr. Maximo brand character holding a tablet.
AI and reliability

Dr. Maximo

A web application for Maximo and reliability questions that shows its sources, keeps track of the release and reads approved system data without changing it.

Inside Dr. Maximo
Fifteen illustrated game worlds from Tiny AI Arcade.
Interactive experiments

Tiny AI Arcade

Small games and practical tools where the rules stay in charge and the model plays a defined part: suspect, narrator or hint-giver.

Enter the arcade
Personal portrait of Cory, created in Image StudioAI portrait of Cory, created in Image StudioRiding portrait of Cory, created in Image Studio
Creative software

Image Studio

A private image application for keeping one person recognizable across many scenes, with reference roles, saved recipes, masked edits and transparent output.

Inside Image Studio
The Story Scrolls
Alice’s Adventures in Wonderland in Story Scrolls, with John Tenniel’s original illustrations.
Alice’s Adventures in Wonderland in Story Scrolls, with John Tenniel’s original illustrations.
Creative software

An illustrated library with room to make your own.

An illustrated public-domain library, several ways to read and a guided workshop for writing and illustrating a story of your own.

Open The Story Scrolls
  1. Dealerships

    Selling cars showed me what finance and sales software had to do.

  2. Professional Software Systems

    Finance and insurance software for smaller dealerships.

  3. IBM Maximo

    Asset-management work, starting with barcoding software.

Before the current tools

Dealership software led me to Maximo.

I was building, selling and repairing computers by my mid-teens, and did early web work after that. Then came a stretch as an electronics supervisor at OfficeMax and several years selling cars at Casa Chevrolet in Albuquerque.

The car lot turned out to be good preparation. At Professional Software Systems, I built finance and insurance software for smaller dealerships, including buy-here-pay-here loan handling and sales tools. One of those tools compared amortization scenarios to show when a different use of a customer's money could benefit both the buyer and the dealership. I had worked the sales floor, so I knew what those screens needed to show.

The oddest problem involved driver's license numbers. Some states built their identifiers with Soundex patterns, and each state had its own variations. Inside the dealership workflow, we reverse-engineered those patterns and worked through the exception rules one state at a time.

A contracting connection then brought me into IBM Maximo, writing barcoding software. After that I left the industry for a while to travel and study, starting at San Juan College around 2005 and moving on to New Mexico Tech. Banetti brought me back to software.

How that experience grew into technology leadership

All the software stories.

Explore the applications, experiments and server work, including the private prototypes and the decisions that shaped them.

11 entries
Related work

The design, the businesses
and the skills behind the builds.

There's more to a project than its software: the identity it needs, the business it serves and the people who have to use it.

Build something

What needs
building?

Tell me what the software needs to do, what data it touches and where the current process breaks down. I'm glad to work through the details with you.

Tell me what needs building