MyChatBot agent plugin v0.13.0

Added

• Who answers a chat, in two Sales tools (activation). chat_set_mode
  switches one chat between the AI and a person exactly as the dashboard's AI
  switch does, and takes it out of the Needs-attention queue.
  chat_bulk_return_to_ai gives chats stuck with a manager back to the AI,
  chosen by assistant, channel, and how long nobody on the team has written:
  a dry run first (the default) lists the chats with a preview_token, then
  the same call with dry_run: false, those chat_ids, and the token changes
  exactly them, at most 100 per call. The assistant's own unanswered
  escalations and spam stay with the manager unless asked otherwise.
• channel_get_health (read): each channel's on/off state and why, its
  assistant's state, when a customer last wrote and when the business last
  answered, open disconnect alerts, and Personal WhatsApp's stored sign-in
  state, from stored data only. Credentials are never shown.
• assistant_set_pipeline (configuration): the pipeline an assistant files its
  leads in, as the dashboard's Lead Management card sets it; leads already
  filed are not moved.
• assistant_update_settings takes three more keys: allow_ai_postpone_messages,
  hide_calculus, and send_google_docs_as_attachments.
• Sales 180 -> 184, bundled 235 -> 239. crm-and-sales-operations owns the chat
  mode tools and the pipeline; channels-and-integrations owns channel health;
  operation maps regenerated; skill validation also checks chat_* references.

MyChatBot agent plugin v0.12.0

Added

• The built-in Calendar's setup, in twelve Sales tools. Reads:
  calendar_get_settings (every calendar, or one) and
  calendar_get_staff_hours. Configuration: calendar_update_settings
  (timezone, default duration, business hours, currency, booking
  instructions), calendar_set_staff_hours (the whole week, with the bookings
  to come that fall outside), calendar_staff_update, and
  calendar_service_update. Activation: calendar_staff_create and
  calendar_service_create; the assistant can book them at once. Destructive:
  calendar_staff_delete and calendar_service_delete (refused while bookings
  are to come), and calendar_booking_update (move, cancel, complete).
  Customer-data write: calendar_booking_create. Every write previews before
  confirm=true. Bookings are not notified to the customer.
• Sales 168 -> 180, bundled 223 -> 235. crm-and-sales-operations owns the
  twelve and gains a calendar setup section; skill validation also checks
  calendar_* references.

MyChatBot agent plugin v0.11.0

Added

• integration_setup_link: the dashboard link that opens one integration card
  (a CRM by key or sign-in, Spreadsheet Orders, Google Calendar, Custom MCP, the
  built-in Calendar) on one assistant, and whether the plan or another
  integration on the assistant blocks it. Keys and sign-ins are entered there
  only, never through a tool.
• integration_verify: one read with an integration's stored credentials,
  changing nothing about it (a Custom MCP server that signs in may renew its
  own token, as a chat does). A Custom MCP server lists its tools; KeyCRM, Hubspot,
  Sitniks, NetHunt and Monday answer with the stored key; Spreadsheet Orders,
  Product Spreadsheet and Business Documents open their Google files; Google
  Calendar's connection is active. It returns ok, or what the owner fixes in
  the dashboard. It never returns a key or a token.
• integration_attach and integration_detach: put a connected CRM, Custom MCP
  server, Spreadsheet Orders or Google Calendar on another assistant (with the
  dashboard's plan gate and its one-CRM and calendar rules), or take one off an
  assistant and keep it. Both preview before confirm=true.
• custom_mcp_create: connect a Custom MCP server by its https URL. A server
  that answers is connected with its tools; one that needs headers is saved
  with no tools on, for the owner to finish in the dashboard; one that asks for
  a sign-in is left to the dashboard. Header values are never passed, and a URL
  that looks like it carries a key is refused (the dashboard takes it). Pro
  plan or higher.
• custom_mcp_set_tools: choose which of a server's tools its assistants use,
  as the dashboard's tool picker does.
• The two reads are read-only (integration_verify is open world). Attaching,
  creating a server and switching its tools on are activation; detaching is
  destructive. Sales 162 -> 168, bundled 217 -> 223.
• channels-and-integrations covers the setup link, the check, attaching and
  detaching, and Custom MCP servers, including which customer data an attached
  CRM or server receives. The plugin's skill validation now also
  checks references to integration_* and custom_* operations.

Changed

• The plugin's homepage and documentation links point at the docs' new MCP
  section (https://docs.mychatbot.app/mcp/claude-code-plugin); the old
  /agents/claude-code-plugin address redirects there.

MyChatBot agent plugin v0.10.0

Added

• create_integration_trigger and delete_integration_trigger: add a webhook
  trigger to an assistant's Trigger Outreach automation (the automation is
  created and linked when the assistant has none) or delete one, each with a
  preview before confirm=true. Creating returns the trigger's webhook URL, a
  credential to give only to the system that will call it. Deleting stops the
  URL for good (a new trigger gets a new one) and drops its queued sends; leads
  it captured stay. Edit a trigger with update_integration_trigger.
• list_social_posts: the newest posts of the Instagram account or Facebook
  page connected to an assistant, with whether its Keyword Responder watches
  each one.
• set_keyword_responder: create or change an assistant's Keyword Responder
  (keywords, watched posts, the public reply, the DM). Added posts are checked
  with Meta first. It answers comments as soon as it is saved.
• set_lead_form_instant_outreach: create or change a Lead Form Instant
  Outreach automation (the sender of the lead-form emails, collect-only or
  collect-and-outreach, channels, instruction, funnel status, send schedule).
  The assistant needs its mailbox connected. It runs as soon as it is saved.
• Creating a trigger, the Keyword Responder and Lead Form Instant Outreach are
  activation: each goes live when saved, and messages people in its outreach
  modes (capture-only and collect-only only capture leads). Deleting a trigger
  is destructive. Sales 157 -> 162, bundled
  212 -> 217.

MyChatBot agent plugin v0.9.0

Added

• automation_set_paused: pause or resume one Sales automation without
  deleting it (Trigger Outreach, Instagram/Facebook Keyword Responder, Lead
  Forms, Lead Form Instant Outreach), with a preview before confirm=true.
  Settings, webhook URLs, and assistant links stay. While paused, sends already
  queued are dropped and nobody is messaged; a paused Lead Forms automation
  still captures leads into the CRM, while Trigger Outreach and Lead Form
  Instant Outreach capture nothing. Nothing is replayed on resume. Kinds that do
  not read the switch are refused.
• assistant_attach_follow_up and assistant_detach_follow_up: attach a
  postponed follow-up to an assistant (a live one then arms for that
  assistant's matching chats on their next message or status change; a draft
  waits until published) or detach it, keeping the sequence. Chats already
  part-way through a sequence keep their queued steps until it is unpublished.
  Both preview before confirm=true.
• The bundled catalog grows from 209 to 212 tools (157 Sales).
  automation_set_paused and assistant_attach_follow_up are activation;
  assistant_detach_follow_up is destructive, like the other removals.
• routines-and-automations covers the pause switch and what a pause loses;
  outreach-and-followups covers attaching and detaching follow-ups.

MyChatBot agent plugin v0.8.0

Added

• Lead structure tools: list_managers (the team a lead can be assigned to),
  the custom lead-field list (list_lead_fields, lead_field_create,
  lead_field_update, and lead_field_delete, which keeps the values already
  on leads and needs confirm: true after its dry run), funnel_status_update
  (rename, recolor, or move a status; a rename also renames it on its leads
  and lists the settings that still name the old status, so it is classed
  destructive),
  list_duplicate_clients, client_merge (the dashboard's merge, with a dry
  run), and client_bulk_update (status, labels, or manager for many leads,
  with a dry run, a sample, and the dashboard's count check; never a delete).
• Knowledge tools: add_document_knowledge (a PDF, DOCX, TXT, or CSV file from
  an https link, up to 25 MB, fetched from public addresses only),
  list_knowledge_sources (indexing status, documents, and the assistants
  that use each group), refresh_knowledge_source, and
  test_knowledge_search (what an assistant's knowledge retrieves for a
  question; knowledge searches only).
• assistant_get_model: the model an assistant answers with, where it comes
  from, its price per 100 messages, and the selectable models at the same
  price.
• The bundled catalog grows from 195 to 209 tools (154 Sales).
• crm-and-sales-operations covers the team, lead fields, status updates and
  the settings a rename leaves behind, duplicates and merges (propose the phone
  owner as the target), and bulk changes (what a filter selects, the status
  hand-back effect; dry run, exact approval, then the same call with
  expected_count and the preview_token). business-knowledge covers
  documents by link (one at a time, 30 per source, direct file links),
  source status, re-indexing, and the search test. build-sales-assistant
  reads the model and its price before a model change, and asks the owner to
  check the price of a model outside the same-price list.

MyChatBot agent plugin v0.7.0

Added

• API Actions and channel options are public Sales tools (they were available
  only to MyChatBot's support routine): api_action_create,
  api_action_update, api_action_attach, and set_channel_options. The owner
  sets the endpoint URL and customer-details sharing; header values (API keys)
  stay dashboard-only, and an action with header values keeps its server
  (scheme, host, and port).
• Assistant setup tools: assistant_get_settings and
  assistant_update_settings (manager mode, hand-off, auto-return,
  end-of-conversation, link handling, reply language, web search, and
  communication guidelines, checked as the dashboard checks them, with
  before/after and dry_run), assistant_get_working_hours and
  assistant_set_working_hours, assistant_get_flight_control, control numbers
  (assistant_list_control_numbers, assistant_add_control_number,
  assistant_remove_control_number), and live notes
  (assistant_list_live_notes, assistant_add_live_note,
  assistant_remove_live_note). The bundled catalog grows from 180 to 195
  tools (140 Sales).
• build-sales-assistant covers settings (activation approval for web search,
  communication guidelines and manager mode), Work Hours (an activation: the
  assistant then switches itself on and off), Flight Control (a person connects
  the Telegram group), control numbers (only a number the owner gave,
  notes-only by default, what each access group exposes), live notes, and the
  price of a model change.
• channels-and-integrations covers API actions (activation on create and
  attach, customer-details sharing named explicitly, header values
  dashboard-only) and channel options (dry run to read the current values).

MyChatBot agent plugin v0.6.0

Added

• Eight Sales tools for editing long instructions and skills safely:
  assistant_view_instructions, assistant_patch_instructions,
  assistant_list_instruction_versions, assistant_restore_instructions,
  assistant_view_skill, assistant_patch_skill,
  assistant_list_skill_versions, and assistant_restore_skill. Views and
  version lists are reads; patches and restores are reversible configuration
  writes. The bundled catalog grows from 172 to 180 tools (125 Sales).
• build-sales-assistant teaches the edit loop: read the outline, patch with
  dry_run, apply with expected_version, re-test privately, and restore the
  previous version when a change makes the assistant worse. It names the live
  effects (a save is live at once; flagged text switches the assistant off) and
  stops instead of falling back to a full replacement when skill history is
  unavailable.

Changed

• test-and-evaluate routes fixes to existing instruction or skill text
  through the patch flow instead of full replacements.

MyChatBot agent plugin v0.5.2

Changed

• sell-shopify-store passes assistant_id when it creates the feed and reads
  attached_assistants / attach_note from the result. The api no longer
  attaches a new knowledge base to every assistant without one (api#2146):
  only the named assistant, or the only blank one when none is named.

MyChatBot agent plugin v0.5.1

Changed

• sell-shopify-store passes fast_start: true for a new store and tells the
  owner the first 250 products are searchable within a couple of minutes, with
  the rest of the catalog syncing right after.
• sell-shopify-store warns that creating a feed also attaches its knowledge
  base to every assistant with no knowledge base yet, so it reads
  list_assistants and names those assistants in the proposal.
• sell-shopify-store explains one checkout link per store when an assistant
  uses catalogs from two Shopify stores, and that the assistant asks for the
  variant instead of picking one.
• Shopify limitations no longer depend on /products.json: password-protected
  stores, headless storefronts (use the *.myshopify.com address), and the
  Google Shopping feed app fallback without checkout links.