Skip to content
rocket-pig edited this page May 12, 2023 · 6 revisions

Welcome to the autobabytermux wiki changelog!

Just a changelog for now...

May 12 23 :

  • Memories search now displays top 3 results and has Agent select from them.
  • Post-finish memory saving now asks user confirmation to save, defaulting to No after 5 seconds.
  • edit-memories.sh also uploaded, a menu-driven memories.json selective edit/deletion tool. (which turned out to be good-looking but otherwise worthless code from GPT)

May 10 23:

  • Enable termux-api 'help helper': termux-api cmds have their help @ '-help' OR '--help' OR '-h' OR sometimes no hook at all. Sometimes the help is @ stdout.. OR stderr. Sometimes the command hangs for 15 seconds first. I finally wrote a long convoluted and tiresome script to aggregate them all into a json file. Turning this on means you want REPL calls to '-h' to return text from the json instead of watching the Agent bomb out for eleventy tries. USE_HELP_HELPER = true;

  • Enable 'Memory' chain of events. (requires: npm install minisearch, a tiny little 5K thing with no deps.) Previous completed tasks will be searched and top match included in conversation. Agent is prompted to revise top match (or dismiss if not relevant). Agent will also be prompted after successful 'Finish' with titling and saving new memory. Six or so memories are already included, probably add more over time. ENABLE_MEMORY = true;

See https://github.com/rocket-pig/autobabytermux/blob/main/README.md#latest for a screenshot.

(Note these are both written in a way they can be toggled off - Idk why youd want to. But its all optional. Make sure you re-clone and get the new .json files.)

  • Other changes: like causing termux-api cmds to give feedback, ala 'cmd completed successfully, but with no output' if otherwise silent has REALLY helped the Agent move on. It..is a bit sad really, watching it go around in circles about how to verify the command completed :/ Well, not anymore. :)

May 8 23:

  • Termux:API plugin! Barely tested. But, AA is already getting it! Pretty cool. User can decide what api commands are available to the Agent in the global settings area at the top of the script.

screenshot

May 7 2023:

  • Found a stupid typo: stdout/stderr/log from vm works as it should have been all along now.
  • Added shortcut back that slides into a vm REPL shell. Changed it to '*s' (The [s] is not fun to type when you dont have your external keyboard)
  • A ton of little bugs (like not sending the prefix to the global_history) that while things were still working before, its even better/faster now.
  • I tested removing the 2k char preprompt and preliminary tests show that the single-sentence subprompts _may be all thats needed. If so that saves an absolute ton of API credits. Ill make that the default after more testing.
  • process module is now correctly merged with stdout/stderr overrides so its otherwise functional
  • changed the write/read methods to what is actually happening underneath...its just less confusing.
  • ton of other tweaks and upgrades I cant recall now.

May 6 2023:

  • Removed useless langchain dependency. We were simply being lazy and using their openai interface. Now just uses openai official module.
  • Complete code rewrite: The Q/A flow is now controlled by a delegator that steps thru the Q-O-T-A-F process, with re-prompts each time to keep the LLM on track. It is. so. much faster and more reliable than the previous way of attempting to parse entire return body! This way we arent ever consuming or trying to handle hallucinations.
  • The overall readability is also just incomparably superior to the previous code. I had ironed out all the necessary parts but it needed this refactoring and cleanup something fierce.
  • It can now be run with a question (in quotes) as the first arg on command line.
  • More settings at the top of the file as well for controlling output verbosity, API request limits etc.

May 3 2023 :

  • 'fakefs' wrapper allows AA to have a persistent single-dir 'filesystem' that's saved to fakefs.txt and restored each time. The sandbox otherwise prevents filesystem writes even to the sandbox (using normal methods.) So you can let it do it's thing without worrying about it trashing your drive, AND be able to run commands that save/restore states/data.
Clone this wiki locally