# Different prompts per deployment **URL:** \ **Category:** Feature Requests\ **Created:** [September 3, 2026, 6:35pm UTC](https://community.pickaxe.co/t/different-prompts-per-deployment/8804 "2026-09-03T18:35:37Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![gotinternetmarketing](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/gotinternetmarketing/32/6587_2.png) [@gotinternetmarketing](https://community.pickaxe.co/u/gotinternetmarketing)\ **Post date:** [September 3, 2026, 6:35pm UTC](https://community.pickaxe.co/t/different-prompts-per-deployment/8804/1 "2026-09-03T18:35:37Z")
Feature request: Different prompts per deployment. Right now, I understand that I can create multiple deployments of the same Pickaxe with different usage limits, but not different prompts. It would be very useful if each deployment could have its own prompt settings. Example: - Public deployment: preview output only - Member deployment: full output - Internal deployment: admin/testing output This would reduce the need to duplicate and maintain multiple versions of the same tool. ---
**Author:** ![lindsay\_support](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/lindsay_support/32/4508_2.png) [@lindsay\_support](https://community.pickaxe.co/u/lindsay_support)\ **Post date:** [September 16, 2026, 8:22pm UTC](https://community.pickaxe.co/t/different-prompts-per-deployment/8804/2 "2026-09-16T20:22:37Z")
Hi @gotinternetmarketing ! The best way to accomplish this is to duplicate your tools and create deployments for the duplicates. Prompts are linked to your agents, not to your deployments - so this reorganization would not be possible for us on the backend. I hope that makes sense! ---
**Author:** ![lindsay\_support](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/lindsay_support/32/4508_2.png) [@lindsay\_support](https://community.pickaxe.co/u/lindsay_support)\ **Post date:** [September 16, 2026, 8:22pm UTC](https://community.pickaxe.co/t/different-prompts-per-deployment/8804/3 "2026-09-16T20:22:41Z")