Hi,

Quick (and possibly simplistic question). I've been using the ChatGPT window successfully in OpusModus but find that keeping track of what needs to be cut and paste becomes challenging on larger projects. I've used Codex in other languages for its agentic capabilities and am stuck on how to give Codex access to the OpusModus documentation files so it can create more OM focused coding similar to way the OM ChatGPT window does. Of course they may be hidden for a reason but the OM ChatGPT says:

The Opusmodus documentation files available in this session are stored under /mnt/data/.

Examples:

• Main manual: /mnt/data/Opusmodus Manual.pdf

• Spectral manual: /mnt/data/Spectral Analysis Manual.pdf

• Ncode manual: /mnt/data/Ncode Manual.pdf

• CLM guide: /mnt/data/CLM-Opusmodus-Guide.md

There are also related Opusmodus knowledge files in the same folder, such as /mnt/data/Opusmodus_Functions.json and /mnt/data/Opusmodus_Functions_Listing.json

and I can't find that directory.

Any suggestions would be much appreciated

Pete

Partly answering my own question. The first 4 files listed are at: /Applications/Opusmodus/Contents/Resources/English.lproj/system.omdocst/Documentation/Manuals

I can't find the .json files though.

I am working now on a new documentation system, which should allow you to get the docs data into the AI.
There is some more work to do, but I am close :-)

Excellent news. After I'd put copies of the documentation files into my workspace. Codex created its own index which may well be similar to the json files. It commented that the searching of the files was easier when the files were either opmo or md files rather than pdf. I don't want to ask for the impossible but for me the next stage would be to give the agents access to a terminal version of the compiler but I'm not sure whether the Lispworks license would allow that. With a version that allows creating new images the approach seems to be:

(in-package "CL-USER")

(load-all-patches)

(save-image "~/lw-console"

:console t

:multiprocessing t

:environment nil)

The agent could then run the opmo files and OM functions and help automate the testing of code.

Many thanks,

Pete