User Guide

This guide covers the current AgentifUI interface. Your administrator chooses the available applications, sign-in methods and permissions. Button labels can differ with the selected language and site branding. Ask your administrator for the instance URL; a GitHub repository account does not automatically grant access to a separately deployed instance. For differences between application modes, see the compatibility reference. Ask the operator about their data policy; security and data handling explains the product’s general storage, external-service and deletion boundaries.

I want to…	Read
Sign in, register or reset a password	Access
Find the right Agent or model	Applications
Send messages, read results or understand task status	Conversations
Reopen, rename or delete saved conversations	History
Approve or reject an Agent’s requested action	Human confirmation
Use attachments or run a workflow	Application capabilities
Change my profile, language, theme or timezone	Personal settings

Open the instance’s normal HTTPS address and go to /login.
Use an enabled method: email/password, GitHub, organizational SSO or phone OTP. A missing button usually means that method is not enabled for this instance.
If registration is available, use /register and follow the verification email. Check the sender and destination before opening a link. Never send your password, reset link or verification code to support.
For a local password, use /forgot-password and open the reset email. After a successful reset, sign in again; previous sessions are revoked. For an SSO password, use your organization’s identity provider instead.

Email signup and password reset can be disabled by the operator. A generic reset response does not prove the email was delivered or that an account exists. Check spam and allow time for delivery; repeated requests are limited. If you normally use GitHub or SSO, continue using the original method: signing in through another provider with the same email can be restricted by account-linking policy.

2. Choose A Model Or An Application

The regular chat’s model selector lists configured, accessible Dify model entries.
The application list at /apps exposes configured applications, including LangChain Agents and Dify chatbot, chatflow, workflow and text-generation entries.
LangChain Agents are opened from the application list, not the Dify model selector. An empty selector does not necessarily mean no applications exist.
The list depends on your account, group membership, application visibility and whether the application/provider is enabled. A public application still requires an active signed-in account; it does not mean anonymous access.

If an expected entry is missing or shows No models available, check that you are in the intended entry point and ask the administrator to verify configuration and access. Users do not need an upstream Dify or LangChain service token.

Browse, Search And Favorite Applications

Open the application list. Search by application name, description or tags.
Use the category/tag filters to narrow the list. Clear both the search and category when investigating a missing application.
Switch between grid and list views if useful. Open an application card to enter its own conversation or execution page.
Use the card’s star control to add/remove a favorite. Favorites/common-app filtering and the sidebar provide shortcuts to frequently used applications. A favorite does not grant access or keep a disabled application available.

Favorites are retained in this browser’s local storage. Clearing site data or using another browser/device can change that list; it is not a guaranteed account-wide synchronized preference.

Understand The Application Types

Entry	Typical use	What you interact with
Regular model chat	General questions and follow-up conversation	Chat input and a configured Dify model selector
Dify chatbot or legacy Agent	A published conversational application	Messages, plus enabled application-specific controls
Dify chatflow	Conversation backed by a workflow	Chat and supported input fields; execution/node progress where available
Dify workflow	A task submitted with structured inputs	Input form, execution status, result and application execution history
Dify text generation	Generate text from a configured input form	Inputs, generated text and execution records
LangChain Agent	Conversation with a compatible externally hosted Agent	Shared chat/history, supported tool activities and optional native confirmation

An application’s name or tag is descriptive, not a guarantee of capability. For example, choosing an application called “Document Assistant” does not enable upload if its actual backend/profile does not support it.

3. Start And Continue A Conversation

Open the model or application you want to use.
Enter a question and submit once. Some Dify applications require additional input fields; fill the fields shown by that application.
Wait for the response and any execution/saving indicator to settle. Receiving streamed text alone is not proof the complete result has been saved.
For ordinary conversational applications, send the next question in the same conversation. Open the sidebar or history to return to an existing conversation.
After completion, refresh and reopen the conversation to check persisted history.

The shared Agent chat uses the normal product message components and history entry points. An application may show tool names and progress as activities; these are controlled summaries, not raw tool parameters or results and not permission to execute a tool in your browser.

When the interface reports incomplete saving or an unknown result, keep any important visible text until the issue is resolved. Use the available status/save retry to check the same run; it does not generate another response. If the state does not settle, contact the administrator rather than repeatedly submitting the question. Navigating away, closing the browser or losing the network does not prove the upstream task was cancelled.

Input And Message Actions

In the shared chat input, Enter submits when sending is available and Shift+Enter inserts a newline. Composition with an input method is not a request to submit. You can also use the send button. Empty input, an unfinished upload or an unresolved task may prevent sending; read the current status before trying again.

Use the actions actually present on a message:

Copy copies available message text. Browser clipboard permission and a secure context can affect whether copying succeeds.
Edit and Regenerate, where offered by the conversation path, prepare or request another answer. They are not a way to repair an incompletely saved run. Review what will be sent and any new usage before proceeding.
Useful/Not useful feedback is offered only on paths wired to feedback. Selecting feedback does not modify the answer or guarantee an upstream model will be retrained.
Suggested follow-up questions, when supplied, are shortcuts for another question. They are not steps the Agent has already performed.

Shared visual components do not mean every backend supports every action. In particular, the shared LangChain/negotiated Dify path does not inherit legacy regeneration or feedback merely because it renders the same message layout.

Read Rich Results

Messages can render supported Markdown, tables, mathematical notation and code blocks. Code blocks provide copy/export controls when available; exporting a code snippet downloads text, it does not execute the code. Review generated code before using it.

Some existing Dify responses include collapsible reasoning blocks or reference sources. Expand a reference to inspect the provided document/excerpt and available metadata. A displayed relevance score is not a factual-accuracy guarantee. These controls appear only when the response/path actually supplies the relevant data; they are not promised on all AG-UI or LangChain conversations.

Understand Execution And Saving Indicators

Displayed state	Meaning and next action
Preparing/running	The current request is being admitted or executed; wait instead of submitting duplicates
Waiting for confirmation	Read and answer the confirmation card; this is not a completed task
Saved	The current known result has been persisted; it can be reopened through history
Saving incomplete	Execution and saving differ; keep visible content and use the available status/save lookup
Interrupted/unknown	Completion or acceptance is not established; check status and ask support if unresolved
Failed	The request did not finish successfully; read the error before deciding whether a new request is appropriate

Exact labels vary by language and application. A save-status retry queries or persists the same known result; starting a new generation is a different action. Not every path displays all of these states.

4. Find And Manage History

Open History at /chat/history or select a conversation from the sidebar. The current history search filters conversation titles and available last-message previews; it is not a guaranteed full-text search of all messages. You can rename conversations and use the history selection controls to delete one or multiple entries after confirmation.

Sign in with the same account to see its saved history. Logging out does not delete saved conversations. After logging in again, reopen the history rather than assuming an empty new-chat page means your data disappeared.

Deleting a conversation removes it from the local product’s normal use. It does not promise erasure of upstream Agent memory, provider logs or backups. Ask the operator about retention requirements; do not use local deletion as evidence that an external system has erased its copy.

5. Respond To Human Confirmation

Only explicitly enabled compatible LangChain applications support the current human-input profile. Ordinary LangChain applications and Dify applications do not gain this feature automatically.

Start a task in the designated application and wait for a confirmation card.
Read its title, description and any expiration information. Decide whether the described action is appropriate; do not approve merely because the task paused.
Choose Approve or Reject, adding an optional comment if provided.
Submit once and wait for the resumed task’s status. A decision being accepted is not the same as the complete task finishing successfully.

Refreshing or reopening history displays the saved confirmation state; it does not submit a decision. A card may become unavailable because it expired, was already answered, is being submitted, or its outcome is not yet known. Check the current status instead of responding from multiple tabs. Revoked permissions can also prevent a response.

This profile supports one task per conversation. Start a new conversation for another task after the previous one finishes. Rejection is sent to the Agent as a decision; it does not prove that every upstream side effect was undone.

6. Files, Stopping And Other Capabilities

Use only the controls exposed by the selected application. Capabilities are not identical across backends:

Application path	Current boundary
Existing Dify modes	Input forms, attachments, speech and other controls depend on the mode and configuration; some file-preview and workflow follow-up operations are administrator-only
Dify shared AG-UI chatbot	Explicitly enabled text-only chat; no files, human confirmation or native stop/run-query capability on this path
Ordinary LangChain Agent	Text chat and supported tool activity summaries; no general file input, execution cancellation or durable stream recovery
LangChain human-input profile	Controlled approve/reject interaction, not arbitrary forms or a general approval workflow

A backend may have more features than AgentifUI exposes. A disabled or missing control is not fixed by adding a service token in the browser. A stopped display, network interruption and confirmed upstream cancellation are different states.

Attach A File On A Supported Dify Path

Open an application that exposes an attachment control or a file input field. Its configuration determines accepted file types, count and size.
Select the file and wait for upload to finish. Inspect the attachment preview and remove an incorrect selection before submitting. A selected local file is not yet a completed upload.
Submit the message/form only after required uploads and other fields are ready.
Use the response’s available attachment controls to view or download results. If preview is denied, do not try another user’s file ID or assume you can bypass the restriction with a direct service URL; ask the administrator.

The application, AgentifUI API, reverse proxy and upstream service can impose different limits. A file accepted by the browser can still be rejected during upload. Shared text-only Dify/LangChain chat does not currently expose general file handling. An export of displayed text/code is not a durable Agent-generated file artifact with a managed lifecycle.

Run A Workflow Or Text-Generation Application

Open the application from /apps, not the model selector. Review its input form: supported fields include text, paragraph, number, selection and configured file/file-list inputs. Complete required fields and wait for uploads.
Submit once. Workflow tracking can show node progress and execution state; text generation shows the generated content and available execution details.
Open the result viewer when available. Its copy/download controls export the displayed result: workflow output can be Markdown/JSON text and text-generation output can be a .txt download. This is not a universal export of conversation history, original uploaded files or an Agent’s external state.
Use that application’s execution-history panel to reopen saved records. It is separate from conversational history at /chat/history. Where selection deletion is offered, confirm the intended records before removing them.
Change the inputs and start a new execution for a new task. Reopening a record displays a saved result; it does not rerun the workflow.

On small screens, workflow views provide tabs for the form, tracker and history. If a workflow stop/detail or file-preview action is denied for an ordinary user, the current Dify proxy may intentionally restrict that operation to administrators. Do not interpret every disabled follow-up action as a failed task submission. The node tracker is a display of supported events, not a workflow editor.

7. Personal Settings And Sign-Out

Use /settings and its navigation to open the relevant page:

Page	Available use
`/settings/profile`	Inspect profile data, edit allowed display-name/username fields and manage the avatar
`/settings/appearance`	Select light/dark/system theme and the timezone used by supported date displays
`/settings/language`	Choose the interface language; the page reloads to apply the language cookie
`/settings/account`	Inspect account information and sign out; this is not a complete identity-provider account-management console

For profile changes, edit the enabled fields and save. Fields supplied by an external identity provider can be read-only; changing your local username does not change your organization’s account identifier. For an avatar, open the avatar dialog, select or drop an image, adjust the crop and confirm upload. Use its delete action to remove an existing avatar. File validation and storage errors are reported by the upload flow.

The current locale choices are English, Simplified/Traditional Chinese, Japanese, Spanish, Portuguese, French, German, Russian and Italian. Changing language affects the interface and available localized page copy, not automatic translation of Agent responses or previous messages. Theme/language/timezone preferences have browser-side storage behavior; do not assume every preference synchronizes across devices. A display-timezone change does not change an upstream task’s actual schedule or server timestamps.

Use the account sign-out control and confirm when requested, especially on a shared device. Logout does not delete saved history. Use the password-reset flow for a forgotten local password; the account page is not a universal password, email-address or SSO-account editor. Never share a signed-in browser session.

8. Common Problems

Symptom	What to do
Login returns an error or loops	Use the normal instance address and original sign-in method; report the time and sanitized error to the administrator
Registration/reset email is missing	Check spam and the address; wait before requesting again; ask support to check delivery without sharing the link
An application disappeared or returns 403	Ask the administrator to check account status, group access and application visibility
Busy or quota message	Wait for the existing task or ask about allowance; do not bypass it with duplicate requests
Text appeared but history is missing	Check the saving/status message and same-account history; report the conversation and time before deleting or regenerating
Confirmation is disabled	Check whether it expired or was already submitted; reload its state once and ask support if unresolved

When reporting a problem, include the application name, time, browser, short reproduction steps and any visible error/request identifier. Redact personal content and credentials from screenshots. Administrators can use the administrator guide and operations guide.