Skip to content

docs: tweaks to prompt creation and quickstart #873

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

madams0013
Copy link
Contributor

No description provided.

Copy link

vercel bot commented Jun 24, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
langsmith-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 24, 2025 10:29pm

@@ -49,16 +49,14 @@ Click "Start" to run the prompt.

## Save your prompt

To save your prompt, click the "Save" button, name your prompt, and decide if you want it to be "private" or "public".
Private prompts are only visible to your workspace, while public prompts are discoverable to anyone.
To save your prompt, click the "Save" button and name your prompt.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To save your prompt, click the "Save" button and name your prompt.
To save your prompt, give it a unique name and click the "Save" button. By default, prompts are only accessible in the workspace they were created in.


Prompts default to private and are only visible to your workspace, while public prompts are discoverable to anyone. You can make your prompt public by clicking the "Make public" button at the top of the prompt page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Prompts default to private and are only visible to your workspace, while public prompts are discoverable to anyone. You can make your prompt public by clicking the "Make public" button at the top of the prompt page.


Prompts default to private and are only visible to your workspace, while public prompts are discoverable to anyone. You can make your prompt public by clicking the "Make public" button at the top of the prompt page.
:::tip Public Prompts
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
:::tip Public Prompts


Prompts default to private and are only visible to your workspace, while public prompts are discoverable to anyone. You can make your prompt public by clicking the "Make public" button at the top of the prompt page.
:::tip Public Prompts
The first time you create a public prompt, you'll be asked to set a LangChain Hub handle. All your public prompts will be linked to this handle. In a shared workspace, this handle will be set for the whole workspace.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The first time you create a public prompt, you'll be asked to set a LangChain Hub handle. All your public prompts will be linked to this handle. In a shared workspace, this handle will be set for the whole workspace.


Prompts default to private and are only visible to your workspace, while public prompts are discoverable to anyone. You can make your prompt public by clicking the "Make public" button at the top of the prompt page.
:::tip Public Prompts
The first time you create a public prompt, you'll be asked to set a LangChain Hub handle. All your public prompts will be linked to this handle. In a shared workspace, this handle will be set for the whole workspace.
:::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
:::

:::tip Public Prompts
The first time you create a public prompt, you'll be asked to set a LangChain Hub handle. All your public prompts will be linked to this handle. In a shared workspace, this handle will be set for the whole workspace.
:::

![](./static/create_a_prompt/public_handle.png)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
![](./static/create_a_prompt/public_handle.png)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would simplify and remove public prompts from here

@@ -44,6 +44,8 @@ If you are interested in testing how your prompt performs over a dataset instead

One you have run some tests and made your desired changes to your prompt you can click the “Save” button to save your prompt for future use.

Prompts default to being private, which means they are only visible to your workspace. You can make your prompt public by clicking the "Make public" button at the top of the prompt page to share it with the LangChain Community via the [LangChain Hub](../how_to_guides/langchain_hub).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Prompts default to being private, which means they are only visible to your workspace. You can make your prompt public by clicking the "Make public" button at the top of the prompt page to share it with the LangChain Community via the [LangChain Hub](../how_to_guides/langchain_hub).
Prompts default to being private, which means they are only visible to your workspace.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, remove public prompts. there really isnt a good reason for most ppl to be using

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants