Opens the session: signs in to the store under the user’s login and tells the agent everything it needs to know about the session in one answer. Which store and which login the server signs in under — “Sign-in, Rights, License”.
Not required: a login that has been granted nothing has to sign in too, to learn what it may do.
None: the store and the login are worked out without the agent.
Two blocks: first the session’s data in JSON, then the text.
{
"store": {"name": "shop.example.com", "url": "https://shop.example.com",
"folder": "D:\\Melbis\\shop.example.com", "pinned": false},
"user": {"id": 5, "login": "manager", "name": "Irina",
"options": {"LANG": "ru"}, "from": "program"},
"group": {"id": 2, "skey": "MANAGER", "name": "Managers", "options": {}},
"demo": false,
"folder": "D:\\Melbis\\shop.example.com\\mcp\\claude-code",
"build": {"current": "6.5.1.545", "previous": "6.5.1.544"},
"memory": {"notes": 3, "critical": 1},
"tools": 16,
"tasks": {"waiting": [{"state": "kNew", "name": "New", "count": 2}],
"given": [{"state": "kAccept", "name": "Accepted", "count": 1}]},
"granted": ["session_init", "session_connect", "session_rules_accept", "shop_page", "shop_run", "engine_map_tree"]
}| Field | What it is |
|---|---|
store |
the store: the name from the program’s list of stores, the address,
the folder on the computer; pinned — whether the server is
pinned to it |
user |
the user: the number, the login, the name, the parameters;
from — where the login came from: program —
from the running program, settings — from the saved
settings |
group |
the user’s group: the number, skey, the name, the
parameters; null if there is no group |
demo |
the store works in demo mode, without a license |
folder |
the agent’s working folder in the store folder |
build |
the build of the program: the current one and the one the agent
worked with in this store last time; an empty previous —
the first session |
memory |
how many notes the agent can see and how many of them are critical;
null — there is no right to read the memory |
tools |
how many AI tools the store has; null — there is no
right to their list |
tasks |
the scheduler’s open tasks by state, two lists: waiting
— the move is the user’s (“New”, “Reassigned”, “Requires clarification”,
“Completed” — handed in to them as the creator), given —
the ones they have given to others, in all the open states; closed ones
are not counted; null — the user has no right to the
scheduler |
granted |
the MCP tools granted to this login |
The parameters are the options the owner sets in the
“Users and Access Rights” window, on the
“User Options” and “Group Options” tabs (in the language your program
runs in the captions may differ). The set takes in the parameters with a
filled-in key (skey). A value from a list comes with its
own key, and with its name when it has no key; free input comes as text.
An empty set is {}.
First — only what this very case calls for:
Then — the rules of the session: what the fields of the data mean, who the agent is in the store and whom it works with, the order of work, the sources, the store’s memory, the server, the computer and the store’s local folder.
The project map is not loaded at sign-in: each of its parts the agent requests with its own tool, when it is needed.
A repeated call opens the session anew: the list of rights, the accepted rules and the critical notes that have been read are reset.
| Answer | When | What to do |
|---|---|---|
NO_STORE: |
no store has ever been opened in the program on this computer | open a store in the program |
NO_SUCH_STORE: |
the server is pinned to a folder that is not in the program’s list
of stores, or no folder is given after --store |
fix the server’s configuration in the agent application, or open this store in the program once |
NO_SHOP_INI: |
Shop.ini cannot be read in the store folder |
check the store folder |
NO_SETTINGS: |
there is nowhere for the password to come from: the program is not running on this store or did not answer, and the password is not saved. The text names what exactly the server saw. The second case is the program running on this store, but with its connection currently without a password | start the program on this store, open the store in it again, or turn on “store passwords” in the connection settings; in the second case — enter the password on the “Connection Parameters” tab of the “Connection” window and save |
Refusals of the license, the password, the address, the versions and the backup window come from the store and happen with any tool — “Answers and Refusals”.