> For the complete documentation index, see [llms.txt](https://saveenr.gitbook.io/visiopowershell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saveenr.gitbook.io/visiopowershell/visiops_v3/basics/context-sensitivity.md).

# Context-sensitivity

### Introduction

For most VisioPS cmdlets you never need to identify the target of the operation.

For example, the `Set-VisioText` cmdlet works against the selected shapes in the active document. If no shapes are selected, then nothing happens. 

```
Set-VisioText -Text "Hello World"
```

The ability for cmdlets to target the appropriate objects based on context dramatically simplifies automating Visio with VisioPS. 

### Overriding context sensitivity

Sometimes its more convenient to explicitly identify the targets of a cmdlet. Depending on the cmdlet, the following parameters will be available:

* `-Documents`
* `-Pages`
* `-Shapes`


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://saveenr.gitbook.io/visiopowershell/visiops_v3/basics/context-sensitivity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.