> For the complete documentation index, see [llms.txt](https://operations.clausebase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://operations.clausebase.com/updates-november-2024/2-november-2024.md).

# 2 November 2024

## Individual proxy clauses

<mark style="background-color:orange;">New feature</mark> In ClauseBuddy, it is now possible to create a "proxy" to an individual clause, i.e. similar to a shortcut to a file in Windows that allows you to easily navigate to a certain file from within a different folder.&#x20;

Applied to the legal world, this would for example allow you to create a generic confidentiality-clause that would not only be stored inside of a generic folder with all types of confidentiality clauses, but also (through proxies) inside of a folder regarding *additional obligations for vendors*, inside of a folder regarding *compliance*, inside of a folder regarding *obligations that survive the contract*, etc.&#x20;

Previously, it was already possible to create a proxy *folder* (through the *Manage-folders* administration module). However, it was not possible to create proxies to an individual clause

<figure><img src="https://1414353930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc1g6bv00az2hAVxclF4w%2Fuploads%2FmLjPsPEGIqAKNiyZMhMd%2Fimage.png?alt=media&amp;token=1f1e4fc4-57eb-41df-bb64-ef7a76d85672" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://operations.clausebase.com/updates-november-2024/2-november-2024.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.