Identity & workspace
What this is for. Workspace files are the agent’s long-lived prose: who they are, how they relate to the team, and how they should use tools — plus a Memory file for your own notes about the agent. This is deeper than the Configuration form. What EYAS remembers is not here: it records memory itself and shows it on the Memory page. When autonomy forbids self-update, changes to identity come through Forge instead of a silent rewrite.
When to use it
Section titled “When to use it”- You want to write (or restore) Who I am, My mission, escalation, and refusal rules.
- The agent needs guidance on the team (
AGENTS) or on tool policy (TOOLS). - A bad edit landed and you need History → Restore.
- You are reviewing a Forge soul proposal against the current IDENTITY.
Typical workflow
Section titled “Typical workflow”- Open Agents → the agent → tab Workspace — route
/agents/:id. - Pick a file (Who I am, Team description, Tools, Memory). Edit in Editor or check Preview.
- Use the IDENTITY section chips to jump to (or create) missing headings. Save.
- Open History if you need a snapshot. After restore, the file on disk should match that snapshot.
Features
Section titled “Features”Long-lived behaviour lives in markdown files under data/agents/<id>/, not only in SQL form fields.
File selector
Section titled “File selector”| File label | Meaning |
|---|---|
Who I am (IDENTITY) | Core identity narrative and mission sections |
Team description (AGENTS) | How this agent relates to the team |
Tools (TOOLS) | Tool usage guidance |
Memory (MEMORY) | Your own notes about this agent. EYAS does not send this file to the model, and agents cannot write it. What EYAS remembers is on the Memory page. |
Choosing Memory in the file picker shows that hint: Your own notes about this agent. EYAS does not send this file to the model, and agents cannot write it. What EYAS remembers is on the Memory page. You can still edit and save it, and view its history, as before.
What agents may edit themselves
Section titled “What agents may edit themselves”The workspace_append and workspace_edit tools edit only Team description (AGENTS.md) and Tools (TOOLS.md). Agents can no longer write the Memory file (MEMORY.md) or daily memory files (memory/YYYY-MM-DD.md): EYAS records memory automatically, and agents never write memory themselves.
Editor
Section titled “Editor”| Control | Meaning |
|---|---|
| Editor | Raw markdown edit mode |
| Preview | Rendered preview |
| Markdown content… | Editor placeholder |
| Save | Write file to disk/workspace store |
| (empty) | File has no content yet |
IDENTITY sections helper
Section titled “IDENTITY sections helper”Click a section chip to jump to or create a missing heading:
| Section | Purpose |
|---|---|
| Who I am | Self-description |
| My mission | Mission statement |
| Ongoing proactive duties | Background duties |
| When to escalate | Escalation rules |
| When to refuse | Hard refusal boundaries |
Hint: Click a section to add it if missing.
History panel
Section titled “History panel”| Control | Meaning |
|---|---|
| History | List of saved snapshots |
| View | Open snapshot comparison |
| Snapshot (date) vs Current version | Diff sides |
| Restore | Roll file back to snapshot |
| Empty | No saved history. |
Snapshot notice may say to restore then open in the editor to view full content.
Relation to Configuration & Forge
Section titled “Relation to Configuration & Forge”| Path | What changes |
|---|---|
| Configuration form | SQL-level name, model, tools list, budgets |
| Workspace files | Deep identity, mission, tool policy prose |
| Forge | Proposed identity/soul changes requiring approval |
When autonomy forbids direct identity self-update, agents must propose via Forge instead of rewriting IDENTITY themselves.