Skip to main content

Assistant, missions & memory

When Personal assistant is enabled (PersonalAssistant:Enabled with Workforce), the WebApp’s default surface is a single owner-facing assistant backed by a private personal project and a Personal chief agent.

Assistant​

Open Personal → Assistant.

  • Chat with your chief; specialists may appear as named speakers when consulted.
  • Streaming shows model deltas and tool progress.
  • Edit or regenerate from a message to branch history; previous branches stay available.
  • Attach files (documents, images, audio within size limits); review transcripts before send.
  • Optional ask_user prompts collect choices without replacing approval cards.
  • Ask how a feature works and the assistant answers from this documentation, linking the page it used.
  • Ask it to raise a support ticket and it emails the Kroov support team for you, then gives you a reference such as NX-202608-0042. It confirms with you first, and you can ask it later which tickets you have open.
  • Export or delete conversations as needed.

The first authenticated visit provisions your personal project and chief automatically.

Connections and coding work​

  • For a non-obvious external app, the assistant searches Pipedream by your intent and only offers an app actually returned by the catalogue.
  • Ask the assistant to inspect, plan, or change one of your connected GitHub repositories. It uses the Kroov GitHub App (not Pipedream) to start a coding session.
  • Agent mode can edit code and open a pull request; Plan and Ask are read-only.
  • The session starts in the background. Its workspace stays open afterwards so you can inspect the files. When it finishes, the assistant is woken with the session report and replies in the same conversation (usage, pull-request, and session links).

Coding sessions are available only when the deployment enables both Agent Sessions and Kubernetes. Connect or update GitHub repository access from Connections.

Missions​

Open Personal → Missions for recurring outcomes proposed as complete blueprints.

  1. Review missing app connections first.
  2. Approve once to deploy the blueprint and related resources.
  3. Pause or resume active missions from the list.

Missions wrap the same underlying agents, grants, and triggers used in Studio — advanced users can still inspect them under Projects / Agents / Automations.

Memory​

Open Personal → Memory for global owner memory:

  • Browse items with source metadata, status, and confidence.
  • Edit, accept, or permanently delete entries.
  • Only verified channels (Web session, linked Telegram after the /start command, signed webhooks) can read or write memory — unverified external senders cannot. A native Telegram connection starts inbound listening at connect time; a Pipedream Telegram bot still deploys a hidden source when you link it.

Tips​

  • Keep Studio for advanced control; use Assistant for day-to-day outcomes.
  • Complete connection setup before expecting missions that need external apps.
  • Treat memory as durable personal context — delete entries you no longer want retained.