Chat App
The chat app lets organization members talk to their agents without the console. Use the same 2kw account to ask questions, attach files, and review tool approvals in a dedicated chat interface.
Sign in
Open the chat app
Go to chat.2kw.ai and sign in with the same 2kw account you use for the console.
Choose an organization
Select the organization whose agents you want to use. The organization picker keeps your chats in the right workspace when you belong to more than one organization.
The app supports light and dark themes and a mobile layout, so you can use it from a desktop browser or your phone.
Start a chat
Pick an agent and send your first message. Only agents with a published version appear in the picker. An agent that has been created but has no published version is not ready to chat with yet.
If you manage agents in the console, use Open in chat at the top of the agent's page (on every tab) or in the agents list's actions menu. It opens a new browser tab with that agent already selected. For an unpublished agent, publish a version first.
The link has this form, with your organization slug and agent ID:
https://chat.2kw.ai/{org}/new?agent=<id>
See Agents for creating an agent and publishing its instructions, model, and tools as a version.
Conversations
Your sidebar is a personal list of conversations you started in the selected organization. Select a conversation to resume it and continue from its history. You can also delete conversations you no longer need.
Answers support Markdown formatting and citations. Follow a citation when you want to inspect the source behind an answer.
These conversations are the same /v1/conversations objects exposed by the API.
The chat app provides an interface to that history; it does not keep a separate
copy of the conversation outside the platform.
A personal sidebar
The sidebar shows your own conversations. Organization roles still determine access through other platform interfaces; the User role is restricted to its own conversations.
Attachments
Add files using the attachment control in the message composer. The attached files appear alongside your message, giving the agent material to work with as part of the conversation.
For example, attach a document and ask the agent to summarize it or answer questions about its contents. Review the selected files before sending your message so the agent receives the context you intended.
Approvals
When a tool call needs a human decision, the chat displays an approval card. Review the requested action before choosing a decision:
- Allow once permits this tool call.
- Allow for this chat remembers the decision for this conversation.
- Deny rejects the tool call.
You can include an optional note with your decision to give the agent context. For example, explain why you denied an action or what should change before the agent tries again.
Destructive tools need a fresh decision
Allow for this chat is never offered for destructive tools. Remembered decisions apply to the current conversation, not to every chat with the agent.
Decided requests stay visible in the conversation so you can review what was requested and how you responded.
A request for a tool of a connector names the server it belongs to, for example "on erp". It is decided the same way, and an approved call runs with the connection of the person whose message led to it.
Conversation modes
The mode chip in the composer, next to the attachment control, sets how much the agent may do in this conversation before it needs you. Open it to pick a mode:
| Mode | What the agent may do |
|---|---|
| Plan | Read only. Anything that could change something is refused. |
| Ask | No automatic approver. Calls that need approval wait for you. |
| Auto | An automatic approver decides where this agent allows it; the rest wait for you. |
A mode only narrows what the agent's author allowed. No mode lets the agent do more: a tool the author blocked stays blocked in every mode.
The mode belongs to the conversation. It is stored with the chat, so resuming a conversation brings its mode back. A new pick applies from your next message or approval; a call that is already running keeps the mode it started with.
Which modes the chip offers, and which one a new chat starts in, is set by the agent's author under Conversation modes in the agent's settings in the console. Without that setting the chip offers Plan and Ask, and a new chat starts in Ask. When the agent offers a single mode and the chat is already in it, the chip is hidden.
Plan
When the agent tries a call that Plan does not allow, the call is refused and the agent is told so. Below the answer, each refused call is marked Blocked in plan mode with a Switch to Ask button, or Switch to Auto when the agent does not offer Ask. Switching sends nothing by itself: send your message again to let the agent retry.
Modes and approvals
- Ask shows an approval card for every call that needs approval, including calls an automatic approver would decide in Auto. A call you allowed with Allow for this chat keeps running without asking again.
- Auto lets the agent's automatic approver decide the calls its author lets it decide. Every other call that needs approval shows a card, as in Ask.
- Plan lets you allow only a read-only call. For any other call, and for every connector call, both Allow buttons are disabled and the card says why. The card's Switch to Ask (or Switch to Auto) button leaves plan mode so you can allow the call. Deny works in every mode.
For how modes work in the API, the CLI and the embedded chat panel, see Conversation Mode in the agent documentation.
Connectors
Some agents use a server that acts as you, such as your company's ERP, and need your own sign-in there. You connect such a server once, then decide which agents may use the connection and what they may do with it.
Open Connectors from the user menu, or go to
https://chat.2kw.ai/connectors, which opens the page of your active
organization.
Your connections lists the servers you are connected to: the host, how it
is reached (direct), Active or Needs reconnect, and since when you are
connected. Reconnect signs you in again when the connection needs it.
Disconnect asks for a confirmation, then removes the connection and every
agent's access to it; you sign in again to use it.
Under each connection are the agents that use the server:
- Allow lets that agent act as you on the server. Connecting alone does not.
- Allow again appears when a new version of the agent also reaches other destinations. The row names them, and the agent cannot use the connection until you allow it again.
- Permissions lists the server's tools for that agent. You can set each one to Needs approval or Blocked to make it stricter than the agent's author set it, never looser; a level the author ruled out cannot be chosen. The change applies from the agent's next answer.
- Revoke takes the agent's access away. Your connection stays, and Allow gives the access back.
Available lists the servers your organization's agents use that you have not connected. Connect opens the server's sign-in page in a new tab, and the page updates when you are done. Connecting here stores the connection only: allow each agent afterwards. A server that needs no sign-in says so; agents use it without one.
Connecting from a chat
When an agent needs a server you have not connected, have not allowed it to use, or whose connection has expired, the chat pauses and shows a card: "Agent wants to act as you in host".
- Connect or Reconnect opens the server's sign-in page in a new tab. If the browser blocks the tab, the card shows a link instead. Connecting from the card also allows this agent.
- Allow appears when you are connected already. If the agent now also reaches other destinations, the card lists them.
- Continue appears while a sign-in is under way. Use it if the chat did not notice that you finished.
- Not now goes on without the server. The agent is told you did not connect; after two refusals in one conversation it stops asking there.
The chat continues once every server on the card is answered. You can also type a message instead: the agent then goes on without the connection. While a chat waits, the sidebar marks it Needs you: connect ….
Every sign-in, including one started from the console's agent editor, returns
to https://chat.2kw.ai/connectors/callback. That page completes the
connection, tells the chat or the Connectors page, and closes itself, or says
"Connected. Return to the app." when the browser does not let it close. A
sign-in started from the console sends you back to the console. The page needs
you signed in to the organization you started from.
Roles
Organization Owner, Admin, and Member roles can use the chat app as well as their existing console access.
The User role is for chat-only members. Users can talk to published agents and see only their own conversations; they do not get the console's agent management interface.
To invite a chat-only member, open your organization in the console, go to the Members page, and invite them with the User role. They sign in to the chat app with their own 2kw account.
Limits
- Answers do not stream yet. The response appears after the agent finishes producing it.
- Each conversation uses one agent. To talk to a different agent, start a new chat and pick that agent.