iris-agentic-dev

Use when creating or modifying InterSystems IRIS interoperability production components in Python — Business Services, Business Processes, Business Operations, Adapters, Messages, or Production definitions.

Measure ObjectScript line coverage using %Monitor.System.LineByLine. Wraps a %UnitTest.Manager.RunTest() call, collects per-class hit/total counts, prints a coverage table. Prerequisite: iris-coverage-setup (bbsiz=4096, IRIS restarted).

Measure ObjectScript line coverage using iris_coverage. Use when a user asks about test coverage, coverage reports, or wants to know how well their test suite exercises their code.

InterSystems AI Hub EAP (Early Access Program) — accurate API patterns for builds 158/159/161/162 (current). Covers %AI.Agent declarative Parameters, %AI.Provider.Create, ConfigStore/GetProviderForConfig, @{env/config/wallet} substitution, session management, streaming, tool sets, and known breaking changes from build 141. Load when helping EAP participants set up, build, or debug AI Hub projects.

Use after writing or editing any ObjectScript .cls file, after applying a fix to a compile error, or before declaring a task done — uploads the class to IRIS via Atelier REST, compiles it, and returns structured errors for immediate fixing.

Manage and observe IRIS Interoperability productions — lifecycle, logs, queues, and message tracing

Step-by-step guide for setting up .iris-agentic-dev.toml — diagnose the connection problem first, then generate the right config block for the user's scenario.

Use before writing code that calls, extends, or modifies an ObjectScript class you did not write — fetches the class source from IRIS via Atelier REST and summarizes its API (methods, properties, parameters, inheritance).

Configure, connect, and troubleshoot the iris-agentic-dev MCP server (iris_execute/iris_query/iris_doc/docs_introspect/kb/etc.) against an IRIS container or instance. Use when its tools return IRIS_UNREACHABLE, when pointing it at a new IRIS, or when a connection edit "isn't taking effect." Covers the .iris-agentic-dev.toml config, live file-watch reload, the OrbStack port-discovery gotcha, and the docker-exec fallback.

Use when connecting to IRIS from Python, Java, JDBC, ODBC, or any external language. IRIS connection APIs have specific package names, port numbers, and syntax that differ from every other database.

Use when the user wants to run Python code inside IRIS, call Python libraries from ObjectScript, or use the IRIS Python native API

IRIS Docker container volume permissions on Linux. All IRIS editions (community, enterprise, irishealth, ai_hub) run as UID 51773 (irisowner). Bind-mounting a host directory owned by a regular Linux user causes startup crash. Load when IRIS container fails on Linux with iris-main.log error, or when setting up any IRIS container with bind-mounted volumes on Linux.

Load, compile, run, and test ObjectScript code in an IRIS Docker container. Use when needing to execute ObjectScript non-interactively, load .cls/.mac/.inc files, or run %UnitTest tests via docker exec.

Use when asked about IRIS capabilities, products, or features — especially MCP, full-text search, HL7/Interoperability, mirroring, IRIS for Health vs HealthShare. AI models confidently describe features that don't exist or confuse products.

Use when writing, debugging, or optimizing SQL queries in IRIS — table naming, reserved words, NULL semantics, SQLCODE, IN clause limits, procedures, DDL quirks, and date handling. Load explicitly for SQL work; do NOT load globally for general ObjectScript repair tasks.

Use when writing any IRIS vector search, embedding, HNSW index, similarity search, or AI feature code. Hard gate — IRIS vector syntax is completely different from pgvector.

Use when the user needs vector search, semantic similarity, HNSW index, or graph queries on IRIS data

Use when the user wants to build a RAG (retrieval-augmented generation) pipeline with IRIS as the vector store

Captures IRIS diagnostic packets, maps .INT offsets to .CLS source lines, and correlates error logs. Use whenever an IRIS runtime error or compile failure needs to be diagnosed.

Worked fix examples for the 6 most common ObjectScript LLM mistakes. Uses "Bug Pattern → Root Cause → Fix" structure per SOTA code repair research. Use when fixing ObjectScript bugs involving: Return vs Quit in loops, HTML escaping order, SQL date filters, list operations, or postfix conditions.

Use when writing or reviewing any ObjectScript code. Hard gate — 10-item checklist catches the most common AI mistakes before showing code to the user.

ObjectScript %List, %ListOfDataTypes, $LISTBUILD, $LISTTOSTRING, $LISTNEXT patterns. Use when building, iterating, merging, or converting lists in ObjectScript.

ObjectScript For/While loop patterns, $Order iteration, postfix Quit, Return vs Quit. Use when writing loops, iterating globals/collections, or handling early exits.

MAC routine syntax, label-based structure, #include, $ZTRAP, extrinsic functions. Use when working with .mac files, legacy CHUI apps, or any pre-class IRIS code.

Deep codebase discovery using MCP and text tools. Use this to bridge the gap between raw MCP tool data and high-level architectural understanding. In ISFS workspaces, use iris_search to find references across server-side classes and iris_read_compiled to inspect macro-expanded intermediate code.

Perform coordinated fixes across multiple ObjectScript files. Use when a change in one class requires updates in dependent classes (e.g., method signature changes, renames).

Reviews ObjectScript code for common LLM mistakes before presenting to the user

ObjectScript embedded SQL, %SQL.Statement, date filtering, NULL handling, table naming. Use when writing SQL queries in ObjectScript classes, especially for filtering, date ranges, or dynamic queries.

Compile-test-fix loop for ObjectScript development. Use when writing or modifying ObjectScript classes.

Generates %UnitTest.TestCase subclasses for ObjectScript classes using live IRIS introspection. Use when asked to write tests for any ObjectScript class or method.

Read and search opencode session logs from the SQLite DB at ~/.local/share/opencode/opencode.db. Use when you need to review what a session did, assess whether AI work was safe/correct, diagnose a "session wipe", find a specific tool call or output from a past session, or recover the DB after a migration reset.

Manage and observe IRIS Interoperability productions — lifecycle, logs, queues, and message tracing. Covers pyprod Python API, ObjectScript Ens.Director, and MCP tool flow.

Use when connecting to IRIS from Python, Java, JDBC, ODBC, or any external language. IRIS connection APIs have specific package names, port numbers, and syntax that differ from every other database.

IRIS data persists across container restarts ONLY if IRIS is stopped gracefully before docker stop. Without this, docker stop sends SIGKILL after grace period, leaving the WIJ (write image journal) dirty. Data recovers on next start but takes 30-300s. Load when: stopping IRIS containers, setting up docker-compose for production, or debugging "tables exist but rows are gone after restart".

Use when configuring IRIS containers via CPF merge files (ISC_CPF_MERGE_FILE). Covers CPFPreset patterns, the grongierisc template pattern for password pre-configuration, ChangePassword=0 via Actions, and common CPF merge mistakes. Load when: setting up IRIS Docker containers, debugging ChangePassword errors, or customizing IRIS startup configuration without docker exec.

Use when writing tests that need a live IRIS container, using IRISContainer factory methods, debugging connection failures, or understanding the password reset story. Covers iris-devtester 1.18.0+ patterns: CPF-first password strategy, factory methods, gotchas, and the full connection flow.

Fetch InterSystems IRIS class reference documentation for a specific class and version. Use when implementing any ObjectScript API to verify method signatures, return types, and parameters exist before writing code. Eliminates hallucinated methods. Also covers SQL tables, CSP APIs, and the InterSystems docbook.

Use when the user wants to run Python code inside IRIS, call Python libraries from ObjectScript, or use the IRIS Python native API

Execute, compile, and test ObjectScript code via the objectscript MCP tools. Use when needing to run arbitrary ObjectScript, compile .cls files, or run %UnitTest tests. Prefers MCP tools over docker exec. Falls back to docker exec only when MCP is unavailable.

Use when asked about IRIS capabilities, products, or features — especially MCP, full-text search, HL7/Interoperability, mirroring, IRIS for Health vs HealthShare. AI models confidently describe features that don't exist or confuse products.