Projects and agents
An agent is one workflow: a graph of nodes you build, run, and share. Your agents are listed in your workspace, each shown as a card with its thumbnail, name, description, and when it was last edited.Create an agent
Use the new agent tile or the create button to start a blank agent. Pleyor opens it in the studio so you can start adding nodes.
Open an agent
Click a card to open the agent’s detail view — a live preview of the workflow alongside its name, description, and the node types it uses. From there, open it in the studio to edit. The card’s menu also has a direct Open.
Rename, describe, and organize
Each agent card has a menu with the actions you need to keep things tidy:Rename
Edit the agent’s name inline. You can also rename and edit the description from the detail view.
Edit description
Add a short description so the agent’s purpose is clear at a glance.
Upload thumbnail
Replace the generated cover image with your own.
Clone
Duplicate an agent to start a variation without rebuilding from scratch.
Deleting an agent
Delete an agent from its card menu. You’re asked to confirm first.The asset library
Every output your agents generate lands in the asset library automatically — no manual saving. Each asset is tied to the run and agent that produced it, so you can always trace where a result came from.Browsing
The library groups assets onto shelves you can re-order with a single lens. Switching the lens regroups the same assets without losing any:| Lens | Groups assets by |
|---|---|
| Recent | When they were created |
| Chroma | Dominant color |
| Format | Image, video, or audio |
| Aspect | Aspect ratio |
- Filter by type — image, video, or audio.
- Search by title, hex color, or aspect ratio.
- Limit to a date window — the last 24 hours, 7 days, 30 days, or all time.
- Show only pinned assets.
- Open More filters to filter by agent or by tags.
Inspecting an asset
Click any asset to open it full-screen. The side panel shows its format, dimensions, aspect ratio, size, and creation date, plus its lineage: the source agent that made it, the prompt it came from, and where it’s been used. Use the arrow keys to move between assets andEsc to close.
Pinning and tagging
To keep your best results within reach, pin an asset (pressB in the full-screen view, or use the bookmark control). Pinned assets show up under the pinned filter.
Add tags to group assets across agents and runs — for example a campaign or theme name. Tags show up in More filters and in an asset’s metadata. You can tag several assets at once by selecting them and using the tag action in the selection bar.
Renaming an asset’s stored filename happens inside a workflow, not in the library. Use the Rename Asset node to attach a display name before export.
Trash and restore
Deleting an asset moves it to Trash rather than removing it immediately. Select one or more assets and use the remove action, or delete a single asset, and it’s soft-deleted. Open Trash from the library’s filter row to see what’s there. Each item shows how long it has left.Exporting
There are two ways to get results out of Pleyor: download them, or export them to Google Drive as part of a workflow.Downloading
Download a single asset from its full-screen view, or select several and download them from the selection bar. You can also copy an asset’s URL or use the share action to send a link.Bulk download currently saves the 10 most recent of your selection. To grab more, download in batches.
Export to Google Drive
To send outputs straight to a Drive folder when an agent runs, add a Google Drive Export node to the graph. Connect the assets you want to upload and a destination folder URL, pick your connected Google account, and the node uploads on each run. This is the way to make finished assets land where your team already works, without manual downloading.Next steps
Running agents
Batch over many inputs and pause runs for human review.
Sharing your work
Share a read-only link or deploy the agent as an app.
Credits
How runs consume credits and how to track spend.
Google Drive Export
Send outputs to a Drive folder on every run.