Agents can now set an expiry date and draw on Whiteboards

1 day ago

This pull request teaches agents two new things about Artifacts. They can make one expire on a date, and they can work on a Whiteboard alongside people. Both arrive as new text in the skill file that agents read before they touch an Artifact. The pull request body is just its title, so everything here comes from the diff.

Ask about this presentation

Chapters

  1. 0:00The change
  2. 0:20What it touches
  3. 0:39Expiry parameters
  4. 1:00What expiry does
  5. 1:19Rules for agents
  6. 1:37Whiteboards
  7. 1:54Reading and editing boards
  8. 2:19Evidence and limits
  9. 2:43What to do with it
Show transcript
  1. This pull request teaches agents two new things about Artifacts. They can make one expire on a date, and they can work on a Whiteboard alongside people. Both arrive as new text in the skill file that agents read before they touch an Artifact. The pull request body is just its title, so everything here comes from the diff.

    Slide text
    Artifacts skill update

    Agents can now set an expiry date and draw on Whiteboards

    Two additions to the instructions agents follow for Artifacts.

  2. The whole change sits in one markdown file, SKILL.md, in the artifacts skill. It adds twenty lines and replaces one. Expiry goes into the delete section, Whiteboards becomes a new section eight, and the old Pin heading is the single replaced line, because Pin moves down to section nine.

    Slide text
    One file

    skills/artifacts/
    SKILL.md

    +20 lines added: expiry and Whiteboards
    −1 line replaced: the Pin heading, now section 9
  3. When a user wants something gone later, the skill now tells the agent how to say so. Pass expires_in_days on create or update, in an update call that has no content. Or pass expires_at for a set moment. Setting expires_at to null cancels it. The examples in the skill are keeping something for a month, or a poll that runs a week.

    Slide text
    New in the delete section

    Say when it goes away.

    expires_in_days "keep this for a month", a poll that runs a week
    expires_at a set moment
    expires_at: null cancels it
  4. The skill says an expired Artifact is deleted the same way delete_artifact deletes it. Within a day of the date, it moves to the owner's Trash. It sits there for 30 days. After that, every version, every comment and every file is gone. The owner gets a month to change their mind.

    Slide text

    Expiry is delete, on a timer.

    Expiry date within a day of it
    Trash 30 days in the owner's Trash
    Gone every version, comment and file
  5. Deleting data is the risky part, so the skill adds guardrails. An agent sets an expiry only when the user asks, and the skill says that without one an Artifact is kept. Only the owner can set or cancel an expiry. And whenever the agent sets one, it tells the user the date.

    Slide text

    Three rules keep agents from surprising people.

    Only when the user asks without an expiry, an Artifact is kept
    Only the owner sets or cancels an expiry
    Tell the user the date
  6. Whiteboards are a new kind of Artifact. An agent makes one with create_artifact, and gives it no content. The board.shapes field starts it off with frames, stickies, boxes and arrows. The spec value that marks it as a Whiteboard is bisque-canvas slash v1.

    Slide text
    New section 8

    A Whiteboard is an Artifact people and agents draw on together.

    frames stickies boxes arrows

    spec: "bisque-canvas/v1"

  7. Two tools do the work. The read board tool returns the board as structure, with its frames, its shapes and what each arrow connects. The skill says to read it before changing anything or answering a comment about it. The edit board tool adds, moves, restyles or removes shapes, keyed by ids the agent chooses. It only touches shapes the agent drew. Shapes people drew are theirs, so the agent reads them and leaves them alone.

    Slide text

    Read the board first, then edit only your own shapes.

    read_board structure: frames, shapes, and what each arrow connects
    edit_board add, move, restyle or remove shapes, keyed by ids you choose

    Shapes people drew are read, never changed.

  8. There are no before and after numbers here, because the change is instructions for agents rather than code that runs. The author's description reads, update artifacts skills, followed by a pointer to the contributing guide. The pull request doesn't include tests and has no review comments, and it hasn't merged. So the question to settle is whether the new text matches how the tools really behave.

    Slide text
    What the pull request carries

    The evidence is the diff, and the body is one line.

    "Update artifacts skills"

    Open: the pull request has no tests or comments, and it isn't merged yet.

  9. Since the change is only text, review it as text. Check the expiry numbers and the Trash window against what the service does, and check that the Whiteboard tools behave as described. Once it merges, agents can set an expiry date and draw on Whiteboards. The pull request is number six in the artifacts repository.

    Slide text
    Review it for wording

    Agents can now set an expiry date and draw on Whiteboards.

    github.com/bisque-cloud/artifacts/pull/6

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