LLMPU
Large Language Model Processing Unit
Imagine a processing unit powered by LLM and infinite registers. Each register can store a string for prompts or codes. There is no fixed prompt. Instead, the contents of the first several registers are presented to the LLM. By generating code, the processing unit will be able to read and write any register, and directly execute the content of any register as Python code. Then the processing unit can be used as a general intelligent computing engine that potentially can improve itself by rewriting some of its own prompts or codes in registers.
The following instruction set is provided to the processing unit as Python functions:
read(r)returns content in register numberrwrite(r, content)store stringcontentin register numberrrun(r)execute the content in register numberras Python code
And their description is not hard coded, but stored in register 0, for example, as a "firmware".
Get Started
pip install llmpu
import llmpu
llmpu.init({
"api_key": "",
"model": "gemini-flash-latest"
})
# full config with default values:
llmpu.init({
"api_key": "", # llm api key
"V": 16, # visible register number
"L": 16000, # hard character number limit for register
"model": "gemini-flash-latest", # llm model
"llm_config": {}, # llm config
"IS": { # instruction set, can be used by llm
"read": llmpu.read, "write": llmpu.write, "run": llmpu._run
}
})
Instruction set functions:
# use register 100 as an example
llmpu.write(100, "print('hello')") # truncate if exceed config["L"]
llmpu.read(100) # "print('hello')"
llmpu.run(100) # execute code in register 100
# llmpu.run also supports code string
Note:
llmpu._runshares the caller's locals and insert new variables to caller's globals, whilellmpu.runis isolated.
Control functions:
# main cycle: generate instructions
code = llmpu.cycle()
llmpu.run(code) # run the code
# core dump
llmpu.dump("dump.json") # dump registers to a json file
llmpu.load("dump.json") # load registers from a json file
Server and UI:
Network server uses srpc protocol. It only allows localhost traffic for security reason. Exposing the interface allows arbitrary code execution!
llmpu.serve(port=22222, browser=True)
Metadata
Release files for llmpu 0.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| llmpu-0.3.5.tar.gz | 7.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llmpu-0.3.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.0 kB
Release files / llmpu-0.3.5.tar.gz
| Download URL | llmpu-0.3.5.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d49593aa45071bbf7c73e1c1414bdbdd8ca65e52f86559fc7d7923fd05f03de6
|
|
BLAKE2b-256 checksum How to use checksums |
ebca9865bef2214868f33f948338b4b94b7a223f69a137a259536f01437fcd25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / llmpu-0.3.5-py3-none-any.whl
| Download URL | llmpu-0.3.5-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ebc19189b84e681b2687c14c2182a870788c9645540991bbeab6dbdb0326d9b6
|
|
BLAKE2b-256 checksum How to use checksums |
2d58c3681f742b15c0c4a21e24752122c7873222172cf4f9c87609612472b56d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency log