# Externalize agent settings with SPEL

In addition to hardcoding your Agent properties within the annotation, we also support setting those through your application.properties file.  To set this up, just replace your @PeoplelogicAgent annotation with something similar:

```java
@PeoplelogicAgent(value="hrCoordinator", name = "${peoplelogic.agent.HRCoordinatorAgent.name}",
        tools = {"hr-coordinator-tools", "${peoplelogic.agent.HRCoordinatorAgent.tools:}"},
        persona = "${peoplelogic.agent.HRCoordinatorAgent.persona}", title = "${peoplelogic.agent.HRCoordinatorAgent.title}",
        avatar = "${peoplelogic.agent.HRCoordinatorAgent.avatar}", bio = "${peoplelogic.agent.HRCoordinatorAgent.bio}", shortBio = "${peoplelogic.agent.HRCoordinatorAgent.shortBio}")
public interface HRCoordinatorAgent extends WorkerAgent { }

```

Each of the values inside the strings like `${peoplelogic.agent.HRCoordinatorAgent.name}`  are properties.  Just replace HRCoordinatorAgent in the string with the simple name of your Agent (SampleAgent for example) and include the whole property in `application.properties`.  It will get picked up on startup of the SDK.


---

# Agent Instructions: 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:

```
GET https://docs.peoplelogic.dev/guides/getting-started-with-the-talent-agent-sdk/advanced/externalize-agent-settings-with-spel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.