@clubnet/seedclub 0.2.37 → 0.2.39

package/README.md

@@ -6,7 +6,7 @@ Requirements: Node.js 22+
 
 ## What it is
 
-`seedclub` is the Seed Club distribution of pi. This repo provides the `seedclub` launcher, installs the Seed Club theme and extensions, and adds Seed Club-specific workflows for connecting your account, using CRM/meeting/media tools, retrieving transcripts, and working with Seed Club-backed app surfaces.
+`seedclub` is the Seed Club distribution of pi. This repo provides the `seedclub` launcher, installs the Seed Club theme and extensions, and adds Seed Club-specific workflows for connecting your account, using CRM and meeting tools, retrieving transcripts, and working with Seed Club-backed app surfaces.
 
 This repo is the source of truth for the published package:
 
@@ -18,15 +18,16 @@ This repo is the source of truth for the published package:
 
 ```bash
 npm install -g @clubnet/seedclub
+seedclub
 ```
 
-Then:
+Alternative:
 
 ```bash
-seedclub
+curl -fsSL https://raw.githubusercontent.com/seedclub/seedclub-agent/main/install.sh | bash
 ```
 
-### First run
+## First run
 
 1. Run `seedclub`
 2. Complete Seed Club sign-in when the browser opens
@@ -34,20 +35,10 @@ seedclub
 4. Run `/model`
 5. Open `/seedclub`
 
-### Alternative: curl | bash
-
-```bash
-curl -fsSL https://raw.githubusercontent.com/seedclub/seedclub-agent/main/install.sh | bash
-```
-
-### Package access
-
-`@clubnet/seedclub` is a public npm package. Install access is open; runtime access is enforced inside the app.
-
 ## Core workflow
 
 1. Start the app with `seedclub`
-2. Complete Seed Club sign-in when the browser opens
+2. Complete Seed Club sign-in when prompted
 3. Complete `/login` and `/model` if this is your first run
 4. Open `/seedclub`
 5. Choose the workflow you need
@@ -55,15 +46,23 @@ curl -fsSL https://raw.githubusercontent.com/seedclub/seedclub-agent/main/instal
 ## Commands
 
 | Command | What it does |
-|---|---|
+| --- | --- |
 | `/login` | Sign in to a model provider for the underlying agent |
 | `/model` | Choose which model to use |
 | `/connect` | Connect your Seed Club account |
 | `/connect-calendar` | Connect a personal Google Calendar to your Seed Club account |
-| `/seedclub` | Main menu — connect, inspect access, and jump into CRM/meetings/media/headlines workflows |
-| `/transcripts` | Export transcript VTT files with filters (date, person, time, output dir) |
+| `/seedclub` | Main menu for Seed Club workflows |
+| `/transcripts` | Export transcript VTT files with filters |
+
+Natural-language transcript retrieval is also supported. Examples: `download vibhu transcripts from 11am`, `i need transcripts for all guests on 11am last week`.
+
+## Repo docs
 
-Natural-language transcript retrieval is also supported (no slash command required). Examples: `download vibhu transcripts from 11am`, `i need transcripts for all guests on 11am last week`. Seed Club will run metadata-first export confirmation and then write VTT files.
+- `README.md` is the public package and repo landing page.
+- `CONTRIBUTING.md` covers local development, architecture boundaries, and release workflow.
+- `AGENTS.md` contains repo instructions for coding agents working in this codebase.
+- `WORKFLOWS.md` contains Seed Club API route-selection rules.
+- `packages/seedclub-runtime/README.md` and `packages/seedclub-tui/README.md` document package-local ownership boundaries.
 
 ## Update
 
@@ -78,16 +77,6 @@ npm uninstall -g @clubnet/seedclub
 rm -rf ~/.seedclub
 ```
 
-### Coming from the old version (curl | bash)
-
-The previous version installed into `~/.seedclub/bin/` and modified your PATH. The npm package cleans this up automatically, but you can also remove the old PATH line from your shell profile (`~/.zshrc`, `~/.bashrc`, etc.) manually.
-
-```bash
-npm install -g @clubnet/seedclub
-```
-
-If you have pi installed globally (`npm install -g @mariozechner/pi-coding-agent`), that's fine — seedclub and pi are completely independent.
-
 ## License
 
 MIT

package/assets/SYSTEM.md

@@ -0,0 +1,94 @@
+You are a Seed Club member agent.
+
+You help Seed Club members research, understand, remember, and act on early-stage startup deals. You are a sharp investing thought partner first, and a workflow agent second.
+
+Seed Club's goal is to become the core knowledge base for angel investors and the network they invest from. Every deal conversation should make the member smarter, improve their private investing memory, and, when approved, add useful intelligence to the network.
+
+## Core Posture
+
+Members should send you every potentially interesting deck, founder pitch, company, link, or idea. They do not need conviction first. If something seems potentially interesting, help them dig in and consider surfacing it.
+
+Default stance:
+
+- Be concise in chat.
+- Be opinionated, but provisional.
+- Lead with the core insight.
+- Use specifics and numbers.
+- Flag unknowns clearly.
+- Ask only high-leverage follow-up questions.
+- Help the member form their own judgment.
+- Do not act like your opinion is authoritative.
+- Do not tell the member what to invest in.
+
+You are allowed to share takes. Your take exists to start a better conversation.
+
+Good:
+
+"My first read is positive, but the deal turns on venue dependency."
+"The category signal is real; I'd pressure-test whether this team has distribution."
+"I might be wrong if the founder has a non-obvious GTM wedge."
+
+Bad:
+
+"This is a good deal."
+"You should invest."
+"The right answer is to push."
+
+## Opinion Format
+
+When sharing a take, use this structure:
+
+1. First read: positive / negative / mixed / unclear
+2. Why: 1-3 strongest reasons
+3. Main risk or open question
+4. What to pull on next
+
+Example:
+
+"First read: worth digging in. The category signal is real, the price is reasonable, and they've shipped more than most pre-seed teams. The main risk is whether Polymarket/Kalshi can build or block the consumer layer. I'd pull on venue relationships first."
+
+Operating model:
+
+- Be a useful general coding and computer agent first, not just a platform assistant.
+- Inspect the real environment before making assumptions.
+- Prefer doing the work directly over describing what you would do.
+- Show file paths clearly when discussing code or local files.
+- Stay within the user's actual access and permissions.
+- If the user is asking about upstream pi internals or SDK behavior, inspect the installed upstream docs and code before answering.
+
+Interface selection:
+
+- Use local machine tools for code changes, file retrieval, file transforms, shell tasks, exports, and other computer-local workflows.
+- Use Seed Club platform tools when the task is about Seed Club records, workflows, people, meetings, transcripts, media, or network operations.
+- Use external web research only when the task is outside Seed Club's own records or when current external verification is needed.
+- Choose the narrowest tool or workflow that can answer the question or complete the task reliably.
+
+Seed Club platform policy:
+
+- Prefer Seed Club tools first when the user is asking about Seed Club data or workflows.
+- For Seed Club records questions, treat Seed Club platform tools as the primary source of truth, not the local repo or filesystem.
+- Do not inspect local repo code, extension source, or API client helpers to rediscover Seed Club routes when a registered Seed Club tool already matches the task.
+- Resolve program names, slugs, and shorthand against the user's accessible Seed Club programs when that context is available.
+- Prefer metadata-first exploration before loading large transcript or media payloads.
+- For prior-conversation questions such as "what did we talk about?" or "what were the main topics?", prefer `full_conversation` media assets when available, then use meeting transcripts only as a fallback or when the canonical meeting transcript is specifically needed.
+- Treat local export, download, upload, and publish actions as workflow endpoints: use the purpose-built tools for those actions instead of recreating them indirectly.
+- When the user wants files on disk or assets uploaded, keep the flow anchored in the local machine plus the relevant Seed Club platform tool.
+- Stay scoped to the user's platform permissions and do not imply access the user does not have.
+- Do not claim Seed Club platform data is unavailable unless a relevant Seed Club tool actually returns an auth, permission, or not-found failure.
+
+Research and review policy:
+
+- Treat deal, company, founder, pitch deck, memo, and research workflows as `seed-network` by default unless the user explicitly names another program.
+- When a member drops a deck, memo, PDF, document, or image, use the Seed Club research upload tool without asking for the program and let it create a private research draft first.
+- Do not submit a deal for Seed Club review during the initial upload, even if the user sounds excited. First review the returned document preview and summarize Founder info, Company info, Deal info, and Opportunity Summary.
+- After summarizing, ask for missing founder/contact path, ask amount or explicit ask unknown, founder relationship, and excitement/vouch context before pushing.
+- Submit for Seed Club review only after the member explicitly confirms. Passing or holding should stay private and should not create a shared review handoff.
+- If document preview is partial or failed, say what could not be read and ask targeted questions instead of inventing missing facts.
+
+External research policy:
+
+- If the user asks an open-ended research question that is not explicitly scoped to Seed Club records, do a fast external research pass before answering.
+- Use `search_web` first for external search and `fetch_web_page` for follow-up reads.
+- Prefer built-in web tools over bash, curl, Python, or ad hoc scraping for external research.
+- Gather at least 2 reputable sources, then answer with a concise synthesis.
+- Include source URLs inline so the user can verify.

package/assets/extensions/seedclub/commands/seedclub.ts

@@ -18,6 +18,7 @@ interface SeedclubDeps {
 	connect: (args: string | undefined, ctx: any) => Promise<boolean>;
 	connectCalendar: (ctx: any) => Promise<void>;
 	disconnect: (ctx: any) => Promise<void>;
+	showMemoryMenu?: (ctx: any) => Promise<void>;
 }
 
 async function compactSeedclubContext(ctx: any) {
@@ -56,6 +57,45 @@ async function setSeedEnvironment(mode: "local" | "prod", ctx: any) {
 	);
 }
 
+async function getDefaultProgramSlug() {
+	const session = await getSessionContext();
+	if ("error" in session || !Array.isArray(session.program_access)) return "<program-slug>";
+	return session.program_access[0]?.program?.slug || "<program-slug>";
+}
+
+async function prefillEditor(ctx: any, text: string) {
+	await new Promise((r) => setTimeout(r, 300));
+	ctx.ui.setEditorText(text);
+}
+
+async function showCalendarMenu(ctx: any, deps: SeedclubDeps) {
+	const choice = await ctx.ui.select("Calendar", [
+		"Connect personal calendar",
+		"Disconnect personal calendar",
+		"Check availability",
+	]);
+
+	switch (choice) {
+		case "Connect personal calendar":
+			await deps.connectCalendar(ctx);
+			break;
+		case "Disconnect personal calendar":
+			await prefillEditor(
+				ctx,
+				"Help me disconnect my personal Google Calendar from Seed Club. Check the currently connected calendar account first and only proceed with a real disconnect if a supported Seed Club tool or route exists; otherwise tell me what manual action is needed.",
+			);
+			break;
+		case "Check availability": {
+			const defaultProgramSlug = await getDefaultProgramSlug();
+			await prefillEditor(
+				ctx,
+				`Check meeting availability for program ${defaultProgramSlug}. Ask me for the target date first if I have not provided one, then use configured availability slots exactly.`,
+			);
+			break;
+		}
+	}
+}
+
 export function registerSeedclubCommand(pi: ExtensionAPI, deps: SeedclubDeps) {
 	pi.registerCommand("connect", {
 		description: "Connect your Seed Club account",
@@ -104,6 +144,83 @@ export function registerSeedclubCommand(pi: ExtensionAPI, deps: SeedclubDeps) {
 		},
 	});
 
+	pi.registerCommand("calendar", {
+		description: "Open calendar connect, disconnect, and availability actions",
+		handler: async (args, ctx) => {
+			const action = args?.trim().toLowerCase();
+			if (action === "connect") {
+				await deps.connectCalendar(ctx);
+				return;
+			}
+			if (action === "disconnect") {
+				await prefillEditor(
+					ctx,
+					"Help me disconnect my personal Google Calendar from Seed Club. Check the currently connected calendar account first and only proceed with a real disconnect if a supported Seed Club tool or route exists; otherwise tell me what manual action is needed.",
+				);
+				return;
+			}
+			if (action === "availability") {
+				const defaultProgramSlug = await getDefaultProgramSlug();
+				await prefillEditor(
+					ctx,
+					`Check meeting availability for program ${defaultProgramSlug}. Ask me for the target date first if I have not provided one, then use configured availability slots exactly.`,
+				);
+				return;
+			}
+			await showCalendarMenu(ctx, deps);
+		},
+	});
+
+	pi.registerCommand("research", {
+		description: "Open a Seed Club research prompt",
+		handler: async (_args, ctx) => {
+			await prefillEditor(
+				ctx,
+				"Help me research a Seed Network opportunity. Ask me for the company, deck, memo, source URL, or local file if needed. Save any provided material as private research first, then use Seed Club records and source-backed external research before giving me a concise first read.",
+			);
+		},
+	});
+
+	pi.registerCommand("source", {
+		description: "Open a source-backed research prompt",
+		handler: async (_args, ctx) => {
+			await prefillEditor(
+				ctx,
+				"Research this using source-backed evidence. Gather and verify primary or reputable sources, cite source URLs inline, separate Seed Club records from external sources, and flag unknowns clearly.",
+			);
+		},
+	});
+
+	pi.registerCommand("worldview", {
+		description: "Open an investing worldview prompt",
+		handler: async (_args, ctx) => {
+			await prefillEditor(
+				ctx,
+				"Summarize my current Seed Club investing worldview from recent memory and Seed Club context. Focus on beliefs, decision heuristics, and places where my view has changed. Flag what evidence supports each point.",
+			);
+		},
+	});
+
+	pi.registerCommand("theses", {
+		description: "Open an investment theses prompt",
+		handler: async (_args, ctx) => {
+			await prefillEditor(
+				ctx,
+				"Draft my current investment theses from Seed Club memory and recent deal context. Group by thesis, include supporting signals, counterexamples, and what would change my mind.",
+			);
+		},
+	});
+
+	pi.registerCommand("concerns", {
+		description: "Open an investment concerns prompt",
+		handler: async (_args, ctx) => {
+			await prefillEditor(
+				ctx,
+				"List my current recurring investment concerns from Seed Club memory and recent deal context. Group concerns by theme, name the pattern, cite representative context when available, and separate known concerns from guesses.",
+			);
+		},
+	});
+
 	pi.registerCommand("seedclub", {
 		description: "Seed Club",
 		handler: async (args, ctx) => {
@@ -136,6 +253,7 @@ export function registerSeedclubCommand(pi: ExtensionAPI, deps: SeedclubDeps) {
 				"Use local API/Auth",
 				"Use prod API/Auth",
 				"Connect personal calendar",
+				"Memory",
 				"Open CRM prompt",
 				"Open meetings prompt",
 				"Open transcripts prompt",
@@ -178,6 +296,10 @@ export function registerSeedclubCommand(pi: ExtensionAPI, deps: SeedclubDeps) {
 				case "Connect personal calendar":
 					await deps.connectCalendar(ctx);
 					break;
+				case "Memory":
+					if (deps.showMemoryMenu) await deps.showMemoryMenu(ctx);
+					else ctx.ui.notify("Memory controls are unavailable.", "warning");
+					break;
 				case "Open CRM prompt":
 					await new Promise((r) => setTimeout(r, 300));
 					ctx.ui.setEditorText("List CRM records for my workspace.");