Setup for Senso's Shared Context path. It writes Start Here, the first document every agent on the team reads, at the root of the knowledge base. The user describes the organization, or the agent writes it from a project folder, a file, or the organization's own documents. Use when senso-shared-context sends the user here because the knowledge base is empty or has no Start Here, or when the user says "set up Shared Context" or "write our Start Here". Do not use for the Verification Loop setup (senso-verification-loop-setup). Do not use when the user names material to save (senso-context-layer).
npx @senso-ai/shipables install senso-ai/senso-shared-context-setupShared Context needs one document before it can work: Start Here. Every agent on the team reads it first. It says what the organization is about, what agents must know, and where things go. It is at the root of the knowledge base.
Setup is only this one document. Then senso-shared-context continues, and its first message
tells the user that setup is done.
Setup does not do the Verification Loop tasks: no industry, brand name, content type or brand kit.
senso whoami one time. If the router gave you the organization's name, use it and do
not run whoami. Say the name in a sentence. Do not show the other fields.senso-context-layer, also on an empty organization.senso kb stats --output json --quiet # total_files
If total_files is 0, go to step 2 and use Message A — empty knowledge base.
If total_files is more than 0, look for Start Here at the root by its name:
senso kb my-files --type content --limit 50 --output json --quiet | jq -c '{total, start: [.nodes[] | select(.name | ascii_downcase | gsub("[^a-z]"; "") | test("^starthere(md|txt)?$")) | {kb_node_id, name}]}'
This is the lookup from senso-context-layer → Find or browse, which owns it. If start is
empty and total is more than 50, use the second command there before you decide.
If you find Start Here, setup is not necessary. Load senso-shared-context.
If you do not find Start Here, go to step 2 and use Message B — documents, no Start Here.
Message A — empty knowledge base:
Shared Context is your team's knowledge base in Senso: one memory all your agents share. What one agent saves, every other agent can read — so one agent knows what the others know. Your knowledge base is empty, so let's start with Start Here, a short overview every agent reads first. Describe in a few lines what you're building, or point me at your project folder or a file and I'll write it from that.
Options: I'll describe it (Recommended) — a few lines on what you're building · Read my project folder — I'll look through it and write Start Here from what's there · Use a file I have — a plan or brief you've already written.
Message B — documents, no Start Here:
Shared Context is your team's knowledge base in Senso: one memory all your agents share. What one agent saves, every other agent can read — so one agent knows what the others know. Right now your knowledge base has no quick way for an agent to get context about your team — each one has to search through everything. Want me to create a Start Here, a short overview every agent reads first?
Options: Create it from what's here (Recommended) — I'll read your documents and write it · I'll describe it · Read my project folder · Use a file I have.
The picker's question is "You're on ." and then the message, word for word. Do not shorten, reorder or change it.
If the user came from senso-shared-context and selected Create Start Here, do not show
Message B. The user already agreed. Go to "Create it from what's here" and use the documents
that senso-shared-context already read.
"Create it from what's here":
references/create-start-here-from-documents.md before you do anything. Without it, you
will write Start Here from folder names only.senso-shared-context shows the user what you saved."I'll describe it": say "Go ahead — a few lines is plenty." Wait for the typed answer.
"Read my project folder":
package.json,
pyproject.toml) and the list of top-level files. Do not read all the files in the folder..env files, keys or credentials."Use a file I have": say "What's the path — or paste it here." Read all of the file.
This step is for I'll describe it, Read my project folder and Use a file I have. Show the full document:
Start Here
Owner: · Status: <approved | draft>
<what this organization is about — what is being built and for whom, their words or the folder's>
What agents should know: <their words, or what the folder or file says>
Where things go: <their words, if they gave any>
That's what I'd save at the top of your knowledge base. Right?
Options: Save it (Recommended) · Change something.
Rules for the document:
senso-context-layer → Add something after setup.After the user selects Save it, ask one typed question:
Whose name goes on it as owner? If it's someone else, it goes in as a draft for them to approve.
senso-context-layer → Add something → Text, notes, and markdown files —
create-raw.kb_folder_node_id to the kb_node_id from senso kb root. This saves it at the root, and
the module does not ask for a folder.senso-context-layer → After any write: wait until it is searchable, then do one search
with --no-gap-signals that finds it.Load senso-shared-context. Do not write a message here.
The first message of senso-shared-context tells the user that setup is done — "That's setup done
— Start Here is in, and every agent you connect reads it first" — and then gives the ending. See
senso-shared-context → When setup ran this session, the first message is the setup close
instead.
Keep these for that message: the owner's name, and which option the user selected.
senso-context-layer owns all of them.senso-shared-context.| The user wants | Skill |
|---|---|
| To save, find or organize named material | senso-context-layer |
| The Verification Loop, or its setup | senso-verification-loop |
| To get started, with no path selected | senso-quickstart |