Assistants

Create

Sidebar + → Create assistant. First-run onboarding writes a short bio and SOUL.md. Or open the in-app Marketplace to install starter assistants (coding, writing, learning, planning, translation, computer helper, and more), or paste a public GitHub / .okbot source.

Edit drawer

Edit-assistant tabs: Details / Tasks / Automation / Memory / Skills / Resources (squads omit Memory / Skills).

Details: name, description, avatar (3D bot-avatar or emoji), optional model override (provider + model; empty = global default); Advanced (Developer mode) can edit SOUL.md, global-skills toggle, and more
Tasks: long-running tasks in three columns — backlog (manual delete) / in progress / finished; see Evolution
Automation: that assistant’s schedules (view, pause, delete); see Evolution
Memory / Skills: per-assistant only; global memory lives under Settings → Global memory
Resources: per-assistant light library (below)

Resources library and notes

Under each assistant: resources.jsonl + resources/ for HTML notes (type=note), URLs (type=url), folder / file links, and ingested copies.

In chat you can ask to “note this / keep maintaining it”; built-in manage_note (on by default, usually auto-allowed) creates or updates the same note
URLs: when an assistant reply is persisted, http(s) links in it are indexed into the library (deduped by normalized URL; title from the markdown label when present, else hostname); the list shows the site favicon (globe fallback); open with the system / browser
Reply bubbles can attach a one-shot preview card (captured once when the session loads that message; no thumbnail on disk)
Resource lists paginate newest-first; previewable items (md / notes / code text / images) open in a fullscreen preview (images keep zoom; others can download); md / code reuse the chat bubble stack; notes use an editable iframe
The library is not dumped into model context by default; upgrades do not migrate ad-hoc files already sitting in resources/
Relative tool paths default under that assistant’s work root: library deliverables go in resources/…, throwaways in temp/…; the edit-page library lists / previews / deletes (new items mainly via chat and tools)
Boundary: timed / recurring → schedules; actionable checklists → long-running tasks; durable documents to keep → notes

Composer `@` mentions

Type @ in the composer to open grouped suggestions: Assistants / Squads, Automations (schedules), and Skills. ↑↓ to move, Enter / Tab to insert, Esc to dismiss. Inserted items appear as inline chips (delete as a whole); the send body keeps structured tokens so the model can resolve entities.

Automation and skill catalogs are scoped to the current session owner (for a squad: that squad’s schedules plus the union of members’ local skills) — not other members’ catalogs, and not global skills.

Mid-turn steer

While an assistant is busy, the composer stays editable. Sending again soft-steers the in-flight turn (cancels pending auto-continue and reopens the same active context with your new message). Use Stop separately to abort all in-flight turns for that owner; Stop keeps the mid-run checkpoint, so a later composer continue can resume from it (manual Stop is not silently auto-resumed). Mid-turn transient model / HTTP / network failures keep the checkpoint and retry that model segment in-turn (default 3 attempts including the first; settings.watchdog.transientRetries). A global Watchdog (on by default, ~30s) silently resumes when a run is gone or heartbeat-timed-out and a safe checkpoint remains; pending HITL, in-flight soft-steer, and Stop leftovers are excluded. Squad captain checkpoints are included in silent / cold auto-resume. Failed user messages can retry from the bubble.

In-chat emoji reactions

On an assistant bubble, hover More and pick an emoji: set / change quietly wakes the assistant (quote that message + emoji); tapping the same emoji again clears it without waking. Assistants can also react on a user bubble as a short acknowledgement. Reactions live on the message record — not a new timeline bubble.

Export / Import assistant

Export: edit-assistant drawer (top-right) → Export assistant → .okbot (unencrypted zip). Pack contains bot.json (name, description, full avatar fields) + optional SOUL.md + skills/.
Import: sidebar + → Import assistant, pick a .okbot or a folder with bot.json. Always creates a new assistant; does not change local model secrets.

No chat, memory, resources library, schedules, or secrets. Until a community marketplace is open, export/import and the in-app Marketplace are the main ways to share assistants.

Evolution and long-running tasks

After install or create, assistants use cross-session memory and post-turn Wrapping up; chats can also advance long-running task checklists, schedules, and notes. See Evolution.