Team Shared Library

  • Desktop, mobile and web
  • Pro, Team
View as Markdown

What it does

Anything set up at project level can be published to your team in one action and imported by every member: dev commands (the seed script, the migration runner), SSH hosts (staging, production, a jump box), database connections (engine, host, port, database, user, including ones reached through an SSH tunnel), prompts and skills. Publishing writes a self-contained copy: a teammate's edits never touch yours. No password is ever shared, by design rather than by setting: passwords, passphrases, private keys and tokens are stripped before anything is stored, and each member authenticates with their own credential on first use, kept in their own machine's vault.

Outside a team, a single resource can still be handed to one person through the in-app chat: drag an agent card, a dev command, an SSH connection, a prompt or a skill onto the open chat pop-up and send it; the recipient imports it in one click.

Where to find it

  • Publish: the Share with my team action on a dev command card or an SSH connection card in the dock, and in the Dev commands, SSH connections and Databases managers of the project ("Share these commands with your team").
  • Browse and import: Settings > Account > Team library ({count}), listing what the team published for the open project, each entry "by {name}" with Import / Imported and Remove from the library.
  • Chat sharing: open the chat pop-up and drag a shareable card onto it ("Drop to share"); the small share icon at the left of the chat composer shows a short demo.

How to use it

  1. Set the resource up in your project as usual.
  2. Click Share with my team: the entry appears in the team library of that project for every member ("Shared with your team").
  3. A teammate opens Settings > Account > Team library while the same project is open and clicks Import. The copy is theirs; for a connection they are asked for their own credential at first use.
  4. The publisher or a team admin can Remove from the library; imported copies are untouched.

Through the chat: with a conversation open, drop up to six resources onto the pop-up, add a message if you want, send. The recipient's bubble shows a card with Import; agents and commands need a project open on their side, prompts and skills go to the project library or the account library.

Settings

None.

Agent tools (MCP)

None. Once imported, the resources are reachable through the usual commands_*, ssh_*, db_*, prompts_* and skills_* tools like any local one.

Providers

All providers, no difference.

Mobile

The team library is browsable on the phone: entries show Shared by you / Shared by {author}, with Import and Unshare; importing writes through the connected desktop. Publishing is a desktop gesture. A chat message carrying a resource shows a compact card on the phone with the note "Import from AgentsRoom desktop".

Limits

  • The team library requires a Team plan or a free group of Pro accounts; without a team the panel reads "No team library".
  • Entries are per project: the library shown is the one of the open project.
  • Only the publisher or a team admin can remove an entry.
  • A library can be full for a project ("The team library is full for this project").
  • Credentials, key paths and local avatar files never travel; a shared SSH or database connection carries host and user only.
  • Chat sharing: the chat must be open to receive a drop, six resources per message.

Common questions

  • Will my teammate get my database password? No. Passwords cannot enter the library; they enter their own on first connection.
  • I edited an imported command, did I change the team's copy? No. Import makes a copy; edit freely.
  • I am Pro but see no team library. You need to be in a team: buy seats or create a free group of Pro accounts in Settings > Account.
  • How do I share one prompt with one person who is not in my team? Drag it onto the chat pop-up and send it.

Related