Agents now publish from the account that owns your work instead of asking

When someone has several Bisque accounts saved, an agent publishing an Artifact used to stop and ask which one. This pull request changes two skill files so the agent works out whose work it is first, and asks only when it truly can't tell.

Here is the line that came out. When several accounts are configured and none is pinned, ask which one. The caution made sense, because the Artifact lands in that account, and only that account can update or share it afterwards. That applied whenever several keys were saved and none was pinned.

The replacement tells the agent to use the account the user's Artifacts already live in. The condition is the same, several accounts and none pinned, but the action flips from asking to choosing. The new text gives its reason in one sentence: the question is whose work this is, not how many keys are saved.

The skill lists the evidence the agent should look at. First, the earlier Artifacts in this conversation or project. Second, the links the user shares. Third, what the list artifacts call returns for each saved key. When the user has consistently published from one account, routine work goes there without a question.

The question isn't gone. The skill keeps it for the case where both accounts hold recent Artifacts and the new one could belong to either. It also keeps it when there is no history to go on.

One sentence at the end of the paragraph has no exceptions. When the Artifact already exists, the agent uses the account that owns it. There is nothing to infer and nothing to ask.

The artifact comments skill gets the same change. Its original reason for asking was that your replies appear under that person's name. The old line asked which account. The new one uses the account that owns the Artifact, and asks only when more than one of the accounts can open it and none of them owns it.

The change is small. The artifacts skill gains ten lines and loses three. The comments skill gains five and loses two. The description only says Update artifacts skills, and the diff has no tests or before-and-after results. The reasoning is the text added to the files, which is also the part worth reviewing.

Since the change is wording, review means reading it as the agent will. The new rule leans on the phrase genuinely unclear, and the text gives two examples, both accounts holding recent Artifacts, or no history at all. Check that those cover the cases you care about. The rule itself fits in a sentence: use the account that owns the work, and ask only when ownership is genuinely unclear.