Using Codex (or Claude, etc) with ObjectScript

[RyszardWithAZ]

I'm set up so that my ObjectScript code sits locally, and any changes are automatically pushed to our IRIS server with unit tests automatically executing for those classes or routines that are pushed.

In the last few months, we've started using Codex to help write ObjectScript, but Codex can't see the unit test results that are pushed into the Output|ObjectScript window.

I'm attempting to edit the ObjectScript extension so that it populates a local workspace file that can then be accessible to Codex, but is this the right way? Is there a better way? And maybe should the extension do this automatically as a new feature?

[gjsjohnmurray]

I haven't tried this myself, but if you set up your ObjectScript extension so your unit tests can be run within VS Code (see https://docs.intersystems.com/components/csp/docbook/Doc.View.cls?KEY=GVSCO_unittest) does this put the results somewhere Codex can find them?

[RyszardWithAZ]

It does make the (local) unit tests available to VSCode's Test utility, but that test utility also isn't accessible from Codex.

[gjsjohnmurray]

Another approach might be to use the iris_test tool that's part of iris-agentic-dev.

[RyszardWithAZ]

We aren't allowed to run unsigned code and it looks like iris-agentic-dev.exe is unsigned. I hope it gets a signature with later versions.

[RyszardWithAZ]

Although, reading through the doc, this DOES look promising, I just can't run it!

[gjsjohnmurray]

pinging @isc-tdyar

[isc-tdyar]

Looking into it!

[RyszardWithAZ]

I got a corporate exception to run this unsigned, but it turns out we only allow a whitelist of MCP servers. This part is a "me" problem. Sigh.

[isc-tdyar]

@RyszardWithAZ - great you got the exception, because signing the Windows iris-agentic-dev binary is not going to happen any time soon, since that is only something our corporate dev pipelines can do. I also need to request an exception ;)

I also looked into other ways to do it and came up with a free docker-based possibility: I could package the (homebrew) signed linux binary inside a signed docker image that you can run locally (or wherever). It would not be as user- or dev-friendly, but would work for most use cases, unless docker is locked down for you as well. @gjsjohnmurray, do you have thoughts on this approach?

[gjsjohnmurray]

@gjsjohnmurray, do you have thoughts on this approach?

If it can be made to work with tolerable performance and without falling foul of other corporate restrictions then I guess it's worth offering.