I have been using Claude for about 40 hours in the last week and am very impressed at the quantity of work that can be accomplished. It is always right? No. But it is fast. It takes a knowledgeable person to create a good end product with lots of testing, but the efficiency is off the chart. I have accomplished what would have taken multiple months or more in those same hours. I asked Claude about Panorama and here was the conversation…
An off topic question. I use a database called Panorama by ProVUE. It has an extensive programming language. Is there anything that the developer of the program can do so that any user who happens to use Claude will benefit by Claude already having read the online documentation of the program? Or other features that might be accomplished by having a hook into the user’s program?
===
Great question. There are a few distinct things the developer could do, ranging from simple to sophisticated:
Training data submission
Anthropic has a process for submitting documentation to be included in future training runs. If ProVUE submitted the full Panorama X documentation, procedure reference, and example code, future versions of Claude would have native knowledge of it baked in. The catch is that training cutoffs mean it would always be somewhat behind the current version, and there’s no guarantee of inclusion or timeline.
A custom Claude integration (most practical)
The developer could build a Claude-powered assistant directly into Panorama X using the Anthropic API. This would work by:
-
Bundling the full documentation as context that gets sent with every query
-
Giving Claude access to the user’s current procedure code, field structure, or error state
-
Letting the user ask questions like “why isn’t this procedure working” and Claude sees the actual code
This is well within reach today and wouldn’t require any special relationship with Anthropic — just the public API.
An MCP server
This is probably the most powerful option. The developer could publish a Panorama X MCP server that users install alongside the Claude desktop app. It could expose tools like:
-
Read the current procedure being edited
-
Read the database schema (field names, types)
-
Run a test procedure and return the result
-
Look up documentation for a specific function
Claude would then be able to operate with full live context — not just answer questions about Panorama, but actually inspect and help fix the user’s specific database in real time. That’s essentially what your Claude for Chrome setup does for WTD.
A system prompt wrapper
Simplest of all — ProVUE could host a Claude-powered chat page on their own site with the entire documentation pre-loaded as a system prompt. No API complexity for the end user, just a purpose-built “Ask about Panorama” assistant.
The MCP server route is the most exciting because it mirrors what professional IDEs are doing with AI — the assistant sees your actual work, not just generic documentation. Given that Panorama users tend to be power users building real applications, that kind of deep integration would be genuinely useful. You might consider passing this along to Jim Rea at ProVUE — it’s a tractable project for a developer of his caliber.