Send a user message to the agent in a session
Sessions
Send a user message to the agent in a session
Sends a new message from the user to the coding agent working in the session. The message is stored as a session event with the user_message type, then the agent either starts processing it immediately or the message is queued if the agent is already busy.
Required API key scopes: any of sessions:write, sessions:all, all:write, all:all.
POST
Send a user message to the agent in a session
Authorizations
Path Parameters
Minimum string length:
1Response
Default Response
Available options:
user_message, agent_message, system_message, session_finished, session_closed, merge_request_merged, merge_request_closed, agent_file_tree_browse, agent_file_read, agent_file_edit, agent_file_create, agent_file_remove, agent_file_move, agent_file_copy, agent_file_read_range, agent_read_around_match, agent_search_files, agent_search_files_v2, agent_plan_execution_update, agent_ask_user, user_ask_user_response, agent_branch_diff, agent_uncommitted_changes, agent_conflict_state, agent_check_target_branch_mergeability, agent_merge_remote_branch, agent_pull_from_remote, agent_push_to_remote, agent_abort_conflict_resolution, agent_rollback_uncommitted_changes, agent_http_request, agent_web_browse, agent_run_repository_command, agent_alert_created A message sent by the user to the agent within a session. This is the payload created by the send message endpoint.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
- Option 12
- Option 13
- Option 14
- Option 15
- Option 16
- Option 17
- Option 18
- Option 19
- Option 20
- Option 21
- Option 22
- Option 23
- Option 24
- Option 25
- Option 26
- Option 27
- Option 28
- Option 29
- Option 30
- Option 31
- Option 32
- Option 33
- Option 34
Available options:
completed, queued, processing, canceled