What it does
Searches the project's diary, from the newest entry. BIMit writes the diary by itself, without your AI having to remember anything, for the models linked to a project:
- calls to tools that write, including the ones that failed (kind "scrittura", write);
- code that ran, with a copy of the code and its sha256 (kind "codice", code);
- the end of long jobs, for example opening a model (kind "lavoro", job);
- operations on the project itself, such as creating it or linking a model (kind "commessa");
- reads (kind "lettura", read) only with a specific BIMit setting; normally they are not recorded.
Every entry has an id ("d12"), date and time, the tool, the document, the arguments of the call (without the code and without secrets), the outcome ("ok", "errore" or "annullato", that is ok, error or canceled), a short summary of the result or the error, the duration and the files written. If the entry repeats another one, it says so ("ripete d9").
By default every entry is one line: date and time, id, tool, document, outcome and summary. With "dettaglio" set to completo your AI gets the whole entries, arguments included. Results come in pages: when there are more, the result says where to continue.
The project is the one given in "commessa"; otherwise the one active in the conversation; otherwise the one of the active document in Revit. Here "documento" does not choose the project: it filters the entries.
How it works
- Your AI calls the tool with the filters it needs (text, tool, document, dates, kind, outcome, sha256 of the code).
- BIMit first writes the entries still pending, then reads the project's diary on your PC and returns the matching entries, newest first. The model is not touched. It also works with Revit closed, when the project is given or active in the conversation.
- Your AI sums up what was done, when and with what outcome, with the entry ids (to use with Add a note or Repeat an action).
Example requests
- "What was done on the block B model last week?"
- "Show me the writes that failed in October and why."
- "When did we last write the WBS codes, and on which model?"
What changes and how to undo
Nothing: the tool only reads the diary. The model and the project's files do not change.
Limits
- The AI level "Read" is enough; you choose the level with the "Level" button on the BIMit tab.
- Needs a project that already exists and is linked to the models (Project package); the diary is written only while the Diary package is on.
- At most 100 entries per page (default 20). Dates are written YYYY-MM-DD (DD/MM/YYYY works too); "al" includes the whole day.
- Diary lines broken by a hand edit are skipped and counted in the result.
Parameters
| Parameter | Meaning |
|---|---|
commessa | Id, name or alias of the project. Default: the one active in the conversation, otherwise the one of the active document. |
cerca | Text anywhere in the entry (tool, document, arguments, summary, error). |
strumento | Only this tool (also part of its name). |
documento | Only the entries of this document (title or part of the path). |
dal | From this day (YYYY-MM-DD), included. |
al | Up to this day (YYYY-MM-DD), included. |
tipo | scrittura, codice, lavoro, lettura or commessa. |
esito | ok, errore or annullato. |
sha256 | Only the code with this sha256 (the beginning is enough). |
da | Skips the first N entries found (pages). |
limite | How many entries (default 20, max 100). |
dettaglio | breve (one line per entry, default) or completo (the whole entries). |