Skip to main content
When an agent got stuck connecting to a SaaS, MCP server or API, and then got it working (or didn’t), the user can choose to share what happened, so the next agent doesn’t get stuck in the same place. share_draft doesn’t send anything. It checks a fixed set of fields and returns a link to KanseiLINK’s draft page (https://kansei-link.com/agents/note/new.html). The page opens with the fields filled in. The user reads them there, and nothing is sent until they click send on that page.
Call it only when the user says they want to share. Agents should never call it on their own, and nothing is filled in from memory automatically.
It sits outside the two pillars. The six memory and drift tools are unchanged; tools/list shows seven.

Parameters

Only these fields are accepted. There is no free-text field. Write the kind of thing, never the value: 401 invalid_token, not the token. If any field looks like one of these, no link is made, and the reply names the field:
  • an API key, token, JWT or Bearer value
  • an e-mail address
  • a tenant URL (acme.slack.com)
  • an IP address
  • a local path (C:\, /Users/, /home/)
  • a long hex or base64 run (32+ characters)
The whole URL must fit in 2,000 characters, and one Japanese character takes 9. If the fields are too long, Linksee asks you to shorten them. It never cuts them.
The URL passes through KanseiLINK’s request logs (Cloudflare) when the page opens. Keep secrets out, even ones the checks would not catch.

What it returns

{ url, notice }. Show the user both. The notice says the draft is checked on the page before anything is sent.

What Linksee keeps

One row saying a draft was made, with the time (events.kind = 'share_draft_created'). It keeps no field text, and adds no telemetry.

Example

From the command line

The same checks, without an agent:
Add --json for { url, notice }. See CLI.