How to use context.json #22
-
|
Hello everyone. It is difficult for me to use the context as it is described here, because many of the scripts I create are completely transactional and do not start from a presentation itself. They are only to access the records, and it is complicated to understand how to use the push tool to send the context to Claude in that case. I think I am missing the concept a bit. Can you help me understand it? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
When considering client development in FileMaker, most everything happens from the context of a given Layout. This layout is tied to various other Table Occurrences. This, by definition, is what, in FileMaker terms, is the "FileMaker Context" that can be seen. An AI agent, which has it's own use of the term context, (called the "context window" - when considering how much it can retain in it's "memory" (typically just files or sometimes a database of vectors), needs to know the critical underlying ID values of table occurrences, layouts and other scripts. This is the information stored within CONTEXT.json. This all applies only if you're creating scripts for execution within the FileMaker client environment. If you are creating FileMaker "context independent" scripts, such as those that use SQL, Execute Data API and others which don't rely on the current layout context, then an agent doesn't necessarily need the information from CONTEXT.json. Essentially, CONTEXT.json is just a list of the critical ingredients that an agent needs in order to improve the accuracy of the script it is creating for a given FileMaker file. It's import to understand that CONTEXT.json and the "context window" are two totally different things. At least if that is part of the confusion. Otherwise, if you can give a better description of the type of scripts you're creating then I may be able to address that within the agent's instructions. |
Beta Was this translation helpful? Give feedback.
When considering client development in FileMaker, most everything happens from the context of a given Layout. This layout is tied to various other Table Occurrences. This, by definition, is what, in FileMaker terms, is the "FileMaker Context" that can be seen. An AI agent, which has it's own use of the term context, (called the "context window" - when considering how much it can retain in it's "memory" (typically just files or sometimes a database of vectors), needs to know the critical underlying ID values of table occurrences, layouts and other scripts. This is the information stored within CONTEXT.json.
This all applies only if you're creating scripts for execution within the FileMaker…