workspace-course-topics

Create a Matsya session for your ballpark work

Timing: Assigned in Class 11, due before Class 12 — see run manifest (#132) and Assignments for Class 12.

Scope: This assignment is only about named Matsya sessions (--session / session= in Python): what they do on the server, how to use one stable name on every Matsya call for your ballpark, and how to prove it. It does not repeat billing or matsya configure—that is Configure Matsya with your Anthropic key (#131).

Prerequisites: #131 complete and a successful matsya "What is Dolo Plus?" (or equivalent) from your machine.

Goal

Use one stable session name on every Matsya call for this ballpark so the server can chain context across turns and staff can review the thread. This is not Cursor’s chat memory: Matsya still does not read your repo (Class 11 summary — Topic 3). --session is how prior Matsya Q&A are retained on Matsya’s side (README — sessions, Data logging and consent).

Operational caveat: Very long sessions may slow down or time out; start a new session name or run a stateless call without --session for that step if needed.

What to do

1. Pick a session name

Choose a stable string, e.g. topics2026-<your-ballpark-slug>. Use letters, numbers, hyphens; avoid spaces. You will reuse it on every Matsya invocation for this course ballpark until you deliberately start fresh.

2. Two Matsya turns (same --session)

From a terminal (ballpark root is fine):

matsya "I am using a named session for my Topics ballpark dynamic program work." --session YOUR_SESSION_NAME
matsya "Referring to our previous exchange: confirm you have session context and list one thing we are set up to do next." --session YOUR_SESSION_NAME

(You may shorten the wording; keep the same --session value.)

Then:

matsya sessions
matsya sessions --show YOUR_SESSION_NAME

3. Wire Cursor / Claude Code

Add a standing instruction so any agent-run matsya includes your flag, e.g.: Whenever you run matsya for this repo, append --session YOUR_SESSION_NAME. Optionally record the string in docs/matsya-session.txt (or similar) so you do not typo it.

Details of the Python API (ask(..., session="...")) are in the Matsya README — Python API.

Deliverables

  1. Session name (the string only—no tokens).
  2. Workflow note — 3–5 sentences on how you ensure every Matsya call for this ballpark uses that name (terminal habit, agent rule, file in repo, or mix).
  3. Redacted output from matsya sessions or matsya sessions --show <name> showing your session. (Staff can read the full server session; you do not submit a separate prompt log.)

References