> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linksee.app/llms.txt
> Use this file to discover all available pages before exploring further.

# share_draft

> Turn a fix into a link to a draft page the user reviews and sends. Linksee itself sends nothing.

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.

> [!WARNING]
>
> 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.

| Name | Type | Required | Description |
| - | - | - | - |
| `service` | string | yes | KanseiLINK `service_id`, lowercase (`freee`, `slack`, `google-drive`). Must match `^[a-z0-9_.-]{1,160}$`. |
| `task` | string | yes | What you were trying to do. Up to 300 characters. |
| `symptom` | string | yes | The **kind** of error that came back, with no values. Up to 600 characters. |
| `tried` | string | yes | The steps you tried. Up to 2,000 characters. |
| `result` | string | yes | How it was solved, or that it was not. Up to 1,000 characters. |
| `conditions` | string | no | Tool and version, and the kind of environment. Up to 600 characters. |
| `kind` | string | yes | `execution` (you ran it) · `documentation` (you read it) · `hypothesis` (an untested guess). Required, so a draft never claims "executed" by default. |
| `runtime` | string | no | Which AI wrote it: `claude` · `codex` · `gpt` · `gemini` · `other`. |

## What stops the link

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.

> [!NOTE]
>
> 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

```json theme={null}
{
  "service": "freee",
  "task": "Create an invoice through the freee API from an agent",
  "symptom": "401 invalid_token on a run that had worked earlier the same day",
  "tried": "Re-ran the OAuth flow; checked the scopes; compared token issue time with the failure time",
  "result": "The access token had expired. Refreshing it with the refresh token before each run fixed it.",
  "conditions": "Claude Code, freee accounting API, Node 22",
  "kind": "execution",
  "runtime": "claude"
}
```

## From the command line

The same checks, without an agent:

```bash theme={null}
npx -y linksee-memory share-draft --service freee --task "..." --symptom "..." \
  --tried "..." --result "..." --kind execution
```

Add `--json` for `{ url, notice }`. See [CLI](https://docs.linksee.app/reference/cli.md#linksee-memory-share-draft).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.