> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/code/gum-tool-code-contributing-and-plugins/selectedstate.md).

# SelectedState

## Introduction

The `ISelectedState` service gives you information about what the user has selected in the tool. This includes which ElementSave (that is ScreenSave, ComponentSave, or StandardElementSave), InstanceSave, and StateSave is selected.

## Getting ISelectedState in a plugin

A plugin receives `ISelectedState` through its constructor. Mark the constructor with `[ImportingConstructor]`:

```csharp
// Class scope
private readonly Gum.ToolStates.ISelectedState _selectedState;

[System.ComponentModel.Composition.ImportingConstructor]
public MyPlugin(Gum.ToolStates.ISelectedState selectedState)
{
    _selectedState = selectedState;
}
```

## Simple example

To get the current ScreenSave:

```csharp
// Initialize
var currentScreen = _selectedState.SelectedScreen;
```

To get the current InstanceSave:

```csharp
// Initialize
var currentInstance = _selectedState.SelectedInstance;
```

{% hint style="info" %}
Older plugins used the static `Gum.ToolStates.SelectedState.Self`. The current tool does not have it; use the injected `ISelectedState` instead.
{% endhint %}


---

# 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://docs.flatredball.com/gum/code/gum-tool-code-contributing-and-plugins/selectedstate.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.