> ## Documentation Index
> Fetch the complete documentation index at: https://docs.joystream.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Organize and publish agents

> Move an agent to the team that owns the work, make it discoverable, and let other teams install it.

An agent usually starts in a personal workspace, because that's where someone had the idea. It shouldn't stay there.

## Move it to the team that owns the work

```bash theme={null}
jstm agent move failed-payment-digest --to acme-corp/finance
```

`move` transfers ownership. The original workspace no longer holds it.

Do this early. An agent in a personal workspace can't be shared, and it leaves when the person does.

To keep a copy where it is:

```bash theme={null}
jstm agent copy failed-payment-digest --to acme-corp/finance
```

`copy` is right when two teams want to evolve the same starting point in different directions. `move` is right when the agent has one owner and it isn't you.

## Make a variant

```bash theme={null}
jstm agent duplicate failed-payment-digest
```

Duplicating inside the same workspace gives you a starting point for a variant — a version for a different region, or a different set of policies — without disturbing the original.

## Make it discoverable

```bash theme={null}
jstm agent visibility failed-payment-digest ORG_VISIBLE
```

| Visibility    | Who can find it                   |
| ------------- | --------------------------------- |
| `PRIVATE`     | The owning workspace only         |
| `ORG_VISIBLE` | Any workspace in the organization |
| `PUBLIC`      | Beyond the organization           |

`ORG_VISIBLE` is what makes a good capability spread. Another team finds it, installs their own copy, and runs it with their own credentials. The original stays owned where it was built.

<Tip>
  Make an agent org-visible once it has earned production — not while it's still a draft. A discoverable agent that doesn't work costs the next team more time than it saves.
</Tip>

## Find and install someone else's

```bash theme={null}
jstm agent search invoice
jstm agent search --org acme-corp
jstm agent install acme-corp/finance/failed-payment-digest
```

Installing gives you your own installation in your active workspace. It runs with your credentials and appears in your installations:

```bash theme={null}
jstm agent installations
```

From there you can schedule it:

```bash theme={null}
jstm agent schedule set 8c41f2b9-… --cron "0 8 * * 1-5" --env dry_run
```

To remove it:

```bash theme={null}
jstm agent uninstall 8c41f2b9-… --yes
```

Uninstalling removes your installation. The original agent is untouched.

## Sharing with one person

Visibility is for capabilities the organization should reuse. To show one person one agent or one run, share it by email instead — see [Share agents and runs](/guides/share-agents-and-runs).

## Deleting

```bash theme={null}
jstm agent delete failed-payment-digest --yes
```

<Warning>
  Deleting removes the agent and its history. Before deleting, consider setting it to `PRIVATE`, or moving it to an archive workspace — the run history is often the most valuable part.
</Warning>

## See also

* [Visibility and discovery](/features/visibility-and-discovery)
* [`jstm agent` management commands](/cli/agent-manage)