Orca v1.4.268 runs bots on Cursor, GitHub Copilot and Hermes

1 day ago

Orca v1.4.268 lets bots run on Cursor, GitHub Copilot and Hermes, takes images and files in bot chats, group chats and item comments, and gives agents scheduled Slack posts, pins, canvases and lists. Orca also does less work in the background, and chats cut by a crash or restart can continue.

Ask about this presentation

Chapters

  1. 0:00Orca bots run on Cursor, GitHub Copilot and Hermes
  2. 0:10Send images and files to a bot
  3. 0:19Schedule, pin and make canvases in Slack
  4. 0:31Orca does less in the background
  5. 0:42Workers and chats recover
  6. 0:51Run bots on Cursor, Copilot or Hermes? Update.
Show transcript
  1. Orca bots now run on Cursor, GitHub Copilot and Hermes. Each one receives the bot's identity and rules in a file that agent already reads. OpenCode 2.x bots get their standing instructions too.

    Slide text
    Orca

    Orca bots now run on Cursor, GitHub Copilot and Hermes

    Cursor
    an always-applied rule carries the bot’s identity and rules
    GitHub Copilot
    an instructions file in a folder Copilot is pointed at
    Hermes
    a .hermes.md file in the bot’s home folder
    OpenCode 2.x
    bots now get their standing instructions
  2. Bots now take images and files: in a bot chat, a group chat, or an item comment, even on a paired computer. An image on a Slack request reaches the agent as an image.

    Slide text
    Orca
    Where
    bot chats, group chats and item comments
    Paired computer
    files reach a bot running on another machine
    Slack
    an image on a request reaches the agent as an image
    An Orca bot group chat: an attached sidebar mockup with the message Compare this layout with the current sidebar, the bot Scout's reply about the sidebar, and a composer holding image #1 for @Forge
  3. From the command line, agents can now schedule a Slack post for later. New commands pin messages, make canvases and task lists, and cancel scheduled posts. A Slack app installed earlier needs new permissions first.

    Slide text
    Orca

    Agents can schedule Slack posts and make canvases

    $ orca slack post <place> <text> --at +2h
    pin
    pins a message to its channel, or unpins it
    canvas · list
    a canvas from Markdown, or a shared task list
    scheduled
    lists the posts scheduled with --at, or cancels one

    Works only with an Orca cloud that supports these commands; any other refuses and posts nothing. A Slack app installed before now needs new permissions for pins, canvases and lists.

  4. Orca now does less in the background. Credential reads leave the main thread, Claude and Codex hook events start one fewer process, and automatic heap profiles are gone. A nearly full disk now gets a cleanup suggestion.

    Slide text
    Orca

    Orca does less work in the background

    Credentials
    files are read and written off the main thread
    Hooks
    one fewer process per Claude notify event and Codex hook event
    Heap profiles
    no longer taken automatically
    Full disk
    under 10 GB free, Orca points you to Workspace Cleanup
  5. A chat cut off by a crash or a restart can now continue. A worker's final report wakes the agent that started it, and a worker's name in chat opens that worker.

    Slide text
    Orca

    Workers and chats survive a crash

    Crash or restart
    an interrupted chat continues, on headless and paired servers too
    Final report
    wakes the managed agent that started the worker
    Worker names
    chips in chat that open the worker
  6. I would say yes, update, if you want bots on Cursor, GitHub Copilot or Hermes. The limits: Orca Bots is still a beta, and phone changes wait for a matching mobile build.

    Slide text
    Orca

    Run bots on Cursor, GitHub Copilot or Hermes? Update.

    Orca Bots is still a beta. Phone changes need a matching mobile build. Every change is in the release notes.

What happened in AI today, in your inbox

One short email each evening. Read it and you’re caught up.

Built with ❤️ in New York