# Work with engineering data

Use an agent to explore the model and carry out reviewed engineering changes.

Source: https://docs.openeng.io/agents/work-with-data/

The object agent helps with everyday work in the model: finding information, following connections and preparing changes.

## Open the object agent

Select your project and branch, then choose **Open agent**, the spinner button in the workspace. On an engineering type page this opens the object agent. The **Types / Change set** workspace instead opens the ontology agent.

Type your request in **Message the agent** and choose **Send message**. The conversation shows its activity and results. For a proposed change, inspect the plan and choose **Approve plan** or **Reject plan**. Use the branch selector to inspect the branch the run writes to.

**Expected result:** a read question produces an answer from accessible objects; an approved change produces confirmed results on its working branch. Choose **Stop agent** to ask a running agent to stop, then inspect the work already confirmed.

## Ask a connected question

For example:

> Which requirements in the cooling subsystem have no verification link?

Or:

> Show me the requirements and risks connected to this part, including each risk's severity and likelihood.

The agent uses the live type catalogue and the objects you can access. A question can follow relationships across the different tools built on that model.

## Ask for a change

Describe the intended outcome:

> Add a requirement for coolant temperature monitoring, connect it to the cooling subsystem, and show me the proposed changes.

The agent can explore the model and branches before approval. Object writes require an approved plan. Inspect what it proposes, then approve or ask for a revision.

## Follow the work

After approval, the agent applies the plan on an unprotected branch. Its activity and results appear in the conversation. The active branch identifies the design state you are inspecting.

You can stop the agent and inspect the changes already made. Stopping a run does not erase committed work.

## Review the result

Read the branch diff and check the affected objects and relationships. Ask for another iteration if needed.

A person submits and merges the proposed work. Agent assistance follows the same [change-control workflow](https://docs.openeng.io/guides/change-control.md) as other engineering changes.

## Permissions travel with the work

An agent acts on behalf of a person. Its tools are limited by the person's permissions and its approved authority. The audit trail records the person and the agent run.