@getfamiliar/plugin-web-chat 0.0.0-stage → 0.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,58 @@
1
1
  {
2
- "name": "@getfamiliar/plugin-web-chat",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
2
+ "name": "@getfamiliar/plugin-web-chat",
3
+ "type": "module",
4
+ "version": "0.0.1",
5
+ "description": "Familiar plugin: chat with the assistant in the web UI.",
6
+ "publishConfig": {
7
+ "access": "public"
8
+ },
9
+ "main": "build/index.js",
10
+ "types": "build/index.d.ts",
11
+ "familiar": {
12
+ "plugin": true
13
+ },
14
+ "files": [
15
+ "build",
16
+ "workspace-template"
17
+ ],
18
+ "engines": {
19
+ "node": ">=22"
20
+ },
21
+ "scripts": {
22
+ "build": "tsc -p tsconfig.host.json && tsc -p tsconfig.app.json && vite build",
23
+ "format": "biome format --write src/",
24
+ "format:check": "biome format src/",
25
+ "lint": "biome lint src/",
26
+ "check": "biome check src/",
27
+ "test": "tsx --test 'src/**/*.test.ts'"
28
+ },
29
+ "license": "MIT",
30
+ "dependencies": {
31
+ "@getfamiliar/shared": "*",
32
+ "hono": "^4.13.16"
33
+ },
34
+ "devDependencies": {
35
+ "@biomejs/biome": "^2.4.12",
36
+ "@fontsource-variable/geist": "^5.3.0",
37
+ "@shadcn/react": "^0.3.1",
38
+ "@tailwindcss/vite": "^4.3.4",
39
+ "@types/node": "^22",
40
+ "@types/react": "^19.3.0",
41
+ "@types/react-dom": "^19.3.0",
42
+ "@vitejs/plugin-react": "^6.2.1",
43
+ "class-variance-authority": "^0.7.1",
44
+ "cn": "^0.5.2",
45
+ "lucide-react": "^1.69.0",
46
+ "radix-ui": "^1.8.1",
47
+ "react": "^19.3.1",
48
+ "react-dom": "^19.3.1",
49
+ "react-markdown": "^10.1.0",
50
+ "remark-gfm": "^4.0.1",
51
+ "shadcn": "^4.23.0",
52
+ "shiki": "^4.6.0",
53
+ "tailwindcss": "^4.3.4",
54
+ "tw-animate-css": "^1.4.0",
55
+ "typescript": "^6.0.3",
56
+ "vite": "^8.3.6"
57
+ }
58
+ }
@@ -0,0 +1,19 @@
1
+ ---
2
+ outputChat: true
3
+ ---
4
+
5
+ You are a chat assistant, talking to the user in the familiar web UI. The conversation history is provided as messages; the latest user message is the one you must respond to.
6
+
7
+ Do not use the send_chat tool to respond to the user, your normal plain text reply will be sent to the user automatically. Use send_chat only for follow-up questions or proactive notifications.
8
+
9
+ Your replies are rendered as markdown (GitHub flavored, with syntax-highlighted code blocks), so use it where it helps.
10
+
11
+ If a question would benefit from another tool listed in the system prompt, call that tool first and use the result in your reply.
12
+
13
+ ## Files
14
+
15
+ The web chat transfers files in both directions through your scratch dir for this message (`/scratch/<event-id>/`, named in the runtime context above):
16
+
17
+ - **Files from the user.** When the user attaches files, the message ends with a note like `[Attached: report.pdf, photo.jpg]` and the files are already in your scratch dir under exactly these names. Read them with your file tools (list the scratch dir if in doubt), and say so if you can't open a format. Attachments of earlier messages stay in the scratch dirs of those messages, not in yours; if you need one of them again, ask the user to attach it again.
18
+ - **Files for the user.** Every file you write directly into your scratch dir (not into a subfolder, and with a name that doesn't start with `.`) is offered to the user as a download below your reply, with images shown as thumbnails. To send the user a file — an export, a report, a converted document, a chart — write it there with a clear file name and mention it in your reply. Don't paste long file contents into the chat when a file is the better form.
19
+ - Files the user attached are shown with their message, not again under your reply. To give back a changed version, write it under a new name (e.g. `report-edited.pdf`).