Workspace

The workspace is an agent’s own file area on its endue Computer: a folder it can read and write, and where it runs programs. It is how an agent does work that needs somewhere to put things: checking out code, generating a report from data, keeping a scratch directory between conversations.

Where it lives

The workspace is on the agent’s endue Computer, so it is wherever that device is.

• On endue cloud, unless you chose otherwise. You do not create it up front. Ask an agent for work that needs a computer and it prepares one, telling you in the conversation while it does. Preparation takes a moment the first time. After that, the same workspace is there for the next conversation.
• On your own server, if you connected one for this agent. The folder is /var/lib/endue-computer/<agent-id>/workspace on that server.

The chat shows the preparation as its own step, so a slow first run is explained rather than mysterious.

What the agent can do in it

Read, search, write, edit, move, and copy files. Run programs, read their output, and keep programs running in the background.

Workspace tools do not ask on every call

Writing files and running programs on the agent’s endue Computer do not stop for approval. The boundary is the device itself: a machine on endue cloud that belongs to this agent, or the limits you set when you installed endue Computer on your own server.

Other actions still ask first: clicking, typing, and submitting in endue for Chrome, and connector operations that send or delete.

Looking inside

The Workspace section under Inventory in Agent Builder shows what is in there: the file tree, the contents of a file, and the processes currently running.

It is read-only. To change files, ask the agent.

The view does not refresh by itself, because the thing changing the files is the agent, not you. Refresh when you want the current state.

The endue Computer itself, with its status and where it runs, is under Resources › Devices in the same agent’s Agent Builder, not here.

Limits

• One workspace per agent, on its one endue Computer.
• On endue cloud, the files last as long as the device does. Deleting the device, or replacing it with your own server, deletes them. Keep results you need as outputs.
• If the endue Computer is on standby, the view says so, and it starts the next time the agent works. If your own server is off, the view says that too: start endue Computer on the server to see the files.
• The view lists and reads. It does not upload, edit, or delete.

Related

Devicesendue Computer and the other devices an agent works on.

Connect your own server or VMPut the workspace on a Linux machine you control.

OutputsWhere results belong once they are worth keeping.