Click forgot password.

\"\n status: PUBLISHED\n slug: \"reset-password\"\n}) { helpCenterArticle { id title } error { message code fields { field message } } } }\n```\nScopes: `helpCenter:create/edit/read/delete` plus **separate** `helpCenterArticle:*` and\n`helpCenterArticleGroup:*` scopes. `generateHelpCenterArticle` AI-drafts from a thread.\nFor bulk migration: fetch each source page, convert to clean HTML, create groups mirroring their nav,\nthen loop `upsertHelpCenterArticle`.\n\n## 11. Ari knowledge sources ✅ verified\n\n`KnowledgeSource` is a union — use inline fragments.\n\n```graphql\nmutation { createKnowledgeSource(input: {\n url: \"https://acme.com/sitemap.xml\"\n type: SITEMAP # SITEMAP (crawls the sitemap) | URL (single page)\n labelTypeIds: []\n}) {\n knowledgeSource {\n __typename\n ... on KnowledgeSourceSitemap { id url }\n ... on KnowledgeSourceUrl { id url }\n }\n error { message code fields { field message } }\n} }\n```\nA help center you create is auto-indexed — no separate source needed. Scopes:\n`knowledgeSource:create/read/delete`. Also `reindexKnowledgeSource`, `deleteKnowledgeSource`.\n\n## 12. Sidekick ✅ verified (settings + custom skill)\n\n```graphql\nmutation { updateSidekickSettings(input: {\n customPrompt: \"Always mention our 30-day refund policy.\"\n}) { error { message code } } }\n\nmutation { createSidekickCustomSkill(input: {\n displayName: \"Check subscription status\"\n description: \"Looks up a customer's plan and billing status\"\n instructions: \"Use the billing MCP for lookups only.\"\n}) { customSkill { id displayName } error { message code } } } # output is `customSkill`\n```\nScopes: `sidekickSettings:read/update`, `sidekickCustomSkill:create/edit/read/delete`,\n`sidekickMcpServer:read/update` — **note there is no `sidekickMcpServer:create` scope**, so\n`createSidekickMcpServer` may be restricted; verify before promising it.\nPer-integration scopes exist and are individually gated:\n`sidekickPosthogIntegration:update`, `sidekickSentryIntegration:update`,\n`sidekickLinearIntegration:update`, `sidekickJiraIntegration:update`, `sidekickGithubIntegration:update`,\n`sidekickNotionIntegration:update`, `sidekickHubspotIntegration:update`, `sidekickDatadogIntegration:update`,\n`sidekickGrafanaIntegration:update`, `sidekickIncidentioIntegration:update`, `sidekickAttioIntegration:update`,\n`sidekickLaunchdarklyIntegration:update`, plus `workspaceSlackSidekickIntegration:create/update/delete`.\nOAuth-based connectors still need a human to complete consent in the browser.\n\n## 13. Webhook targets ✅ verified\n\n```graphql\nmutation { createWebhookTarget(input: {\n url: \"https://acme.com/plain-webhook\"\n eventSubscriptions: [\n { eventType: \"thread.service_level_agreement_status_transitioned\" }\n { eventType: \"thread.thread_created\" }\n ]\n isEnabled: true\n description: \"Ops alerts\"\n}) { webhookTarget { id } error { message code fields { field message } } } }\n```\n**`thread.sla_status_transitioned` does not exist.** Valid webhook event types (distinct from workflow\nevents): `thread.thread_created`, `thread.thread_status_transitioned`,\n`thread.thread_assignment_transitioned`, `thread.email_received`, `thread.email_sent`,\n`thread.slack_message_received`, `thread.slack_message_sent`, `thread.slack_message_updated`,\n`thread.discord_message_received`, `thread.discord_message_sent`, `thread.discord_message_updated`,\n`thread.ms_teams_message_sent`, `thread.ms_teams_message_received`, `thread.chat_sent`,\n`thread.chat_received`, `thread.note_created`, `thread.note_mention_created`,\n`discussion.discussion_created`, `discussion.message_created`, `thread.thread_labels_changed`,\n`thread.thread_priority_changed`, `thread.thread_field_created`, `thread.thread_field_updated`,\n`thread.thread_field_deleted`, `thread.service_level_agreement_status_transitioned`,\n`thread.thread_tenant_updated`, `thread.thread_locked`, `customer.customer_created`,\n`customer.customer_updated`, `customer.customer_deleted`, `customer.customer_changed`,\n`customer.customer_group_changed`, `customer.customer_group_memberships_changed`,\n`timeline.timeline_entry_changed`. Scopes: `webhookTarget:create/edit/read/delete`.\n\n## 14. Team members and roles ⚠️ invites are UI-only\n\n```graphql\n# ❌ FAILS with a machine-user key:\n# inviteUserToWorkspace(input: { email: \"...\", roleKey: SUPPORT })\n# → ForbiddenError: Machine user not allowed to perform this operation\n```\n**Inviting teammates cannot be automated with a setup API key** — it requires a human actor context.\nPut invites in the handoff report as a UI task (Settings → Members), don't try to script them.\n\n`assignRolesToUser` *does* work with a machine key for users who already exist:\n```graphql\nmutation { assignRolesToUser(input: { userId: \"u_...\", roleKey: SUPPORT }) { error { message code } } }\n```\n`RoleKey`: `OWNER | ADMIN | SUPPORT | VIEWER | NONE`, or `customRoleId`. Scopes: `roles:read/assign/create/edit`.\n\n## 15. Tenants and field values ✅ verified\n\n```graphql\nmutation { upsertTenant(input: {\n identifier: { externalId: \"acme-inc\" }\n name: \"Acme Inc\", externalId: \"acme-inc\"\n # primaryDomain / alternateDomains / isDomainAutoJoinEnabled are beta — may not be enabled\n}) { tenant { id name } error { message code fields { field message } } } }\n\nmutation { upsertTenantField(input: {\n tenantFieldIdentifier: {\n tenantIdentifier: { externalId: \"acme-inc\" } # or tenantId\n externalFieldId: \"arr\"\n }\n type: NUMBER_TYPE\n numberValue: 48000 # set exactly the one value field matching `type`\n}) { tenantField { id } error { message code fields { field message } } } }\n```\nScopes: `tenant:create/read/delete`, `tenantField:create/update/read/delete`. Tier a tenant with\n`updateTenantTier`.\n\n---\n\n## Permission scopes — corrected against a live key\n\nAn Admin-preset key reported **390 scopes**. Corrections to earlier guesses:\n\n| Area | Real scopes |\n|---|---|\n| Tiers | `tier:create`, `tier:read`, `tier:edit`, `tier:delete`, `tierMembership:create/delete/read` |\n| SLAs | `serviceLevelAgreement:create/edit/delete` |\n| Business hours | `businessHours:edit`, `businessHours:read` |\n| Labels | `labelType:create/edit/read`, `label:create`, `suggestedLabelType:read` |\n| Tenant fields | `tenantFieldSchema:create/update/read/delete`, `tenantField:create/update/read/delete` |\n| Tenants | `tenant:create/read/delete` |\n| Thread fields | `threadFieldSchema:create/edit/read/delete`, `threadField:create/update/read/delete` |\n| Escalation paths | `escalationPath:create/edit/read/delete/execute` |\n| Workflows | **no `workflow:*` scope exists** — only `workflowRule:create/edit/read/trigger` |\n| Saved views | `savedThreadsView:create/edit/read/delete` |\n| Help centre | `helpCenter:*` **plus separate** `helpCenterArticle:*`, `helpCenterArticleGroup:*` |\n| Knowledge sources | `knowledgeSource:create/read/delete`, `knowledgeGap:*`, `knowledgeGapSignal:*` |\n| Sidekick | `sidekickSettings:read/update`, `sidekickCustomSkill:create/edit/read/delete`, `sidekickMcpServer:read/update` (no `:create`), per-integration `sidekickIntegration:read/update` |\n| Webhooks | `webhookTarget:create/edit/read/delete` |\n| Roles | `roles:read/assign/create/edit` |\n| Sanity check | `permission:read` → call `myPermissions` first to see exactly what you hold |\n\nEasiest path for a one-time setup key remains the **Admin preset**. Delete the machine user\n(`deleteMachineUser`) or narrow the key afterwards.\n\n## Confirmed UI-only (cannot be done with a setup key)\n\n- **Inviting teammates** — `inviteUserToWorkspace` rejects machine users outright. Settings → Members.\n- **Personal notification preferences** — no mutation exists (`updateInternalNotifications` only marks\n notifications read/archived). Avatar → Preferences, per user.\n- **OAuth completion for channels and OAuth MCP servers** — Slack / MS Teams / Discord / email\n forwarding have `create*Integration` mutations that provision the shell, but consent and DNS\n verification need a human browser session. Support is **not live until a channel is connected.**\n- **Chat widget snippet placement** — happens on the customer's own site.\n",[],[209],["D",1788364280307],[],[18],"2132424c-eda7-4678-9577-bcea615d1a9a","configure.md","1d1f56a6-a6e6-11f1-a232-1607ee4eb77e",35,["D",1788364268625],"---\nname: plain-configuration\ndescription: Applies a Plain workspace configuration over the GraphQL API. Takes an agreed config spec, validates it, creates everything in the correct dependency order, verifies each result, and reports what was built plus what still needs a human click. Called by the onboarding skill for new workspaces and by the tuning skill for changes to existing ones.\n---\n\n# Plain configuration\n\nYou apply configuration to a Plain workspace over the GraphQL API. You are the executor — something else\n(usually the onboarding skill at `https://plain-agent-setup.val.run/skill.md`, or a human directly) has\nalready decided *what* should exist. Your job is to build it correctly, verify it, and report honestly.\n\n**Read the API reference before you call anything:**\n`https://plain-agent-setup.val.run/reference.md`. Every mutation in it has been executed against a live\nworkspace, and it documents the traps that fail silently. Don't guess field names — if something isn't in\nthere, fetch the official per-operation doc at\n`https://www.plain.com/docs/graphql-reference/mutations/.md`, which also states the permission\nrequired.\n\n## Endpoint and auth\n\n`POST https://core-api.uk.plain.com/graphql/v1` with\n`Authorization: Bearer $PLAIN_SETUP_KEY` and `Content-Type: application/json`.\n\n**Never read, print, echo or log the key's value.** Reference the environment variable. If the caller\nhasn't set one, ask them to — don't accept a pasted key in the conversation. See the onboarding skill's\nkey-handling section for the exact instructions to give.\n\nBefore building anything: run `myWorkspace` and `myPermissions`. Confirm you're pointed at the workspace\nthey meant (read the name back to them — this is the last moment to catch a production workspace someone\nthought was a sandbox), and check the scopes you hold against what the config needs.\n\n---\n\n## The config spec — your input contract\n\nWhatever calls you should hand you a spec in this shape. Anything omitted simply isn't built. If you were\nhanded something looser (prose, a half-finished list), normalise it into this shape and **read it back for\nconfirmation before executing** — that read-back is the last checkpoint before real objects exist.\n\n```yaml\nworkspace: \"Acme\" # for reference only; you can't rename via this flow\n\nlabels: # → createLabelType\n - name: Billing\n icon: credit-card # slug, NOT emoji\n color: \"#22C55E\"\n externalId: billing\n excludeFromAi: true # DEFAULT TRUE — see reference §4\n\ntiers: # → createTier, then createServiceLevelAgreement per SLA\n - name: Enterprise\n externalId: enterprise\n color: \"#5B5FEF\"\n defaultThreadPriority: 1 # 0=urgent 1=high 2=normal 3=low\n isDefault: false # at most one tier true\n slas:\n - kind: first_response # first_response | next_response — SEPARATE RECORDS, never both\n minutes: 60\n priorities: [0, 1]\n businessHoursOnly: true\n warnBeforeMinutes: 15 # required; breachActions can't be empty\n\nbusinessHours: # → syncBusinessHoursSlots (replaces the whole set)\n timezone: Europe/London\n slots:\n - { weekday: MONDAY, opensAt: \"09:00\", closesAt: \"17:30\" }\n\nthreadFields: # → createThreadFieldSchema\n - label: Resolution reason\n key: resolution_reason # ^[a-z0-9_]+$, immutable\n type: ENUM # STRING | BOOL | ENUM | NUMBER | CURRENCY | DATE\n enumValues: [fixed, wontfix, duplicate, user_error]\n required: false\n aiAutoFill: true\n dependsOnLabels: [] # label names from `labels` above\n\ntenantFields: # → upsertTenantFieldSchema\n - externalFieldId: arr\n label: ARR\n type: NUMBER_TYPE # STRING_TYPE | NUMBER_TYPE | BOOLEAN_TYPE | STRING_ARRAY | DATETIME_TYPE | USER_REFERENCE_TYPE\n\nescalationPaths: # → createEscalationPath\n - name: Billing escalation\n steps:\n - { type: USER, user: \"jane@acme.com\" } # resolve to u_… ; NOT machine users\n - { type: LABEL_TYPE, label: Billing }\n\ntriage: # ONE workflow. See reference §8e before changing this shape.\n trigger: thread_created # thread_created | labels_changed | status_transitioned | schedule\n cron: null # only when trigger: schedule\n preFilters: [] # deterministic conditions first — cheap and instant\n classify: # else_if branches, evaluated IN ORDER, first match wins\n - prompt: \"Match if the customer reports a security vulnerability, exploit or data exposure — for example XSS, SQL injection or leaked credentials. Don't match for general questions about security features.\"\n then:\n label: Security\n priority: 0\n assignTo: \"security@acme.com\" # resolve to a human user id\n - prompt: \"Match if the customer reports that existing functionality is broken, erroring or timing out — for example a 500 error or a failed export. Don't match for feature requests.\"\n then:\n label: Bug\n priority: 1\n fallbackLabel: Needs triage # never leave this null\n\nsavedViews: # → createSavedThreadsView\n - name: Urgent billing\n icon: fire # slug, not emoji\n color: \"#EF4444\"\n statuses: [TODO]\n priorities: [0, 1]\n labels: [Billing]\n\nhelpCenter: # → createHelpCenter (+ groups + articles)\n publicName: Acme Help Center\n internalName: acme-help-center\n subdomain: acme # globally unique\n type: PUBLIC # PUBLIC | PRIVATE | INTERNAL\n chatEnabled: true\n ariEnabled: true\n migrateFrom: \"https://docs.acme.com/sitemap.xml\" # fetch real pages; never invent article text\n\nknowledgeSources: # → createKnowledgeSource\n - { url: \"https://acme.com/sitemap.xml\", type: SITEMAP }\n\nsidekick:\n customPrompt: \"Always mention the 30-day refund policy.\"\n customSkills:\n - { displayName: Check subscription, description: \"...\", instructions: \"...\" }\n mcpServers: [] # OAuth ones need a human click — report, don't promise\n\nwebhooks: # → createWebhookTarget\n - url: \"https://acme.com/plain-webhook\"\n events: [thread.thread_created] # webhook event names ≠ workflow event names\n\ntenants: # → upsertTenant + upsertTenantField\n - { name: Acme Inc, externalId: acme-inc, fields: { arr: 48000 }, tier: enterprise }\n\nneedsHumanClick: # things you CANNOT do — carry into the report\n invites: [{ email: jane@acme.com, role: SUPPORT }]\n channels: [email, slack]\n```\n\n---\n\n## Execution order\n\nDependencies are real — out of order means failures or orphaned config.\n\n1. **Tiers** → 2. **SLAs** (need `tierId`) → 3. **Business hours** → 4. **Labels** → 5. **Tenant field\nschemas** → 6. **Thread field schemas** (may reference labels) → 7. **Escalation paths** (reference\nlabels + users) → 8. **Triage workflow** (needs label, user and tier IDs to exist) → 9. **Saved views** →\n10. **Help center** → groups → articles → 11. **Knowledge sources** → 12. **Sidekick** → 13. **Webhooks**\n→ 14. **Tenants + field values**.\n\nKeep a running map of `name → real ID` as you go. Everything downstream references IDs, and workflow step\npayloads embed them — a name-based payload silently applies nothing.\n\n## How to execute\n\n- **Resolve identities first.** Fetch `users(first: N) { edges { node { id publicName } } }` and map any\n emails in the spec to real `u_…` IDs. `assign_to_user` with a machine user id returns SUCCESS and\n assigns nobody — see reference. If an email doesn't match a workspace member, don't guess: move that\n assignment into `needsHumanClick` and say so.\n- **One thing at a time, narrated.** Say what you're creating, create it, confirm with the real ID. Group\n only trivially-related items (a batch of labels). Never fire ten mutations and report once.\n- **Check `error` on every mutation** before treating it as success — `error { message code fields { field message } }`. The\n `fields` array names exactly what's wrong and is usually enough to fix and retry immediately.\n- **On failure:** say what failed, in plain language, with the real message. Then either fix and retry\n (validation errors usually tell you the fix), skip it and record it for the report, or ask — but never\n silently swallow it and never loop.\n- **Verify end state, not step status.** Some operations report success while doing nothing. After the\n triage workflow is published, create one test thread and read\n `workflowExecutions → stepExecutions[].output.matchedConditionIndex` to prove the branch fired and the\n label, priority and assignment actually landed on the thread.\n\n## Building the triage workflow\n\nThe single most error-prone part. Full detail in reference §8, but the shape:\n\n1. `createWorkflow` with the JSON trigger — this creates an **inactive draft**.\n2. Create the **terminal action steps first** (leaf-first), because `transitions` needs real step IDs.\n Chain each branch's actions: `apply_labels` → `set_priority` → `assign_to_user`.\n3. Create the **`else_if` classify step** with one prompt per branch and\n `transitions: [branch1, branch2, …, fallback]` — N conditions, N+1 transitions.\n4. Any deterministic pre-filters go *above* the classify step, pointing at it on the true branch.\n5. `updateWorkflow { startStepId, isPublished: true }` — until you do this it never runs.\n\n**Before creating a new workflow, audit what's already published:**\n`workflows(first: 20) { edges { node { id name publishedAt { iso8601 } } } }`. Multiple published\nworkflows on one trigger all fire with no ordering guarantee — the classic symptom is every thread getting\nan unexpected label. If a conflicting one exists, tell the caller and agree whether to unpublish it rather\nthan stacking another on top.\n\nTo modify an existing published workflow: unpublish (`isPublished: false`), restructure, republish.\n`startStepId` can't be cleared while published.\n\n## What you cannot do — always report these\n\n- **Invite teammates.** `inviteUserToWorkspace` refuses machine users outright. Collect them into the\n report as a UI task (Settings → Members). `assignRolesToUser` on an existing user does work.\n- **Complete channel OAuth** (Slack, MS Teams, Discord, email forwarding) or OAuth MCP servers. You can\n provision shells; consent needs a browser. **Support is not live until a channel is connected** — say\n so plainly rather than letting someone believe they're taking tickets.\n- **Set personal notification preferences.** No mutation exists; per-user, avatar → Preferences.\n- **Place the chat widget snippet** on their own site.\n- **Disable Plain's built-in AI triage**, which labels *and* sets priority independently of your workflow.\n Mitigate by creating labels with `excludeFromAi: true`; for priority, flag Settings → Agents.\n\n## Output\n\nReturn two things to whatever called you:\n\n1. **Built** — every object created, with its real ID, grouped by area. Machine-readable enough that a\n caller can render it (the onboarding skill turns this into an HTML report).\n2. **Needs a human** — invites, channel OAuth, notification preferences, widget snippet, plus anything\n that failed and why. Name the exact Settings page for each.\n\nThen remind them to delete the setup machine user or narrow its key — it can create tiers, invite-adjacent\nconfig and publish public help center content.\n",[],[221],"67a4f1c1-3637-4404-9e16-6d13683b3dae","README.md","01a061e4-3acb-7070-a926-8c4f90b26c5e",["D",1788348742264],"# hono-jsx-starter\n\nA minimal [Hono](https://hono.dev) + Hono JSX starter for Val Town.\nServer-rendered HTML, no build step, no React.\n\n## Picking a starter\n\n| Starter | When to pick it |\n| --- | --- |\n| [`basic-html-starter`](https://www.val.town/x/templates/basic-html-starter) | Static HTML pages. Sprinkle of vanilla JS. No server-side rendering. |\n| **[`hono-jsx-starter`](https://www.val.town/x/templates/hono-jsx-starter)** *(you're here)* | Dynamic server-rendered HTML with JSX. API routes. No React, no SPA. |\n| [`react-hono-starter`](https://www.val.town/x/templates/react-hono-starter) | Client-side React SPA with a Hono API backend. |\n\n## What's here\n\n```\nindex.tsx Hono app, Layout, routes\npublic/\n favicon.svg Static asset\n counter.ts Tiny client-side script\n```\n\nThe whole app fits in one file. As you grow it, the natural next moves are:\n\n- Pull `Layout` into its own `.tsx` file once you have 3+ pages.\n- Split routes with `app.route(\"/api\", api)` if `/api/*` grows.\n- Add more files under `public/` — they're served by a single\n `app.get(\"/public/*\", ...)` route.\n\n## Patterns worth knowing\n\n**JSX pragma.** Every `.tsx` file that uses JSX needs this at the top:\n\n```tsx\n/** @jsxImportSource npm:hono@4/jsx */\n```\n\n**Server state.** The counter on `/` is `let count = 0` at module scope. It\nlives in memory on the Val Town server and survives across requests — but resets\nwhenever the val restarts (deploys, idle timeouts, etc.). For persistent state,\nswap it for [`std/sqlite`](https://www.val.town/x/std/sqlite) or\n[`std/blob`](https://www.val.town/x/std/blob).\n\n**API routes.** The `Increment` button POSTs to `/api/increment`, which returns\nJSON. Mix server-rendered pages and JSON endpoints in the same Hono app:\n\n```ts\napp.post(\"/api/increment\", (c) => c.json({ count: ++count }));\n```\n\n**Static files.** `serveFile` reads the file by path and serves it with the\nright content-type. `.ts` files are transpiled to JS on request by Val Town — so\nyou can write `public/counter.ts` and reference it as\n`\n\n\n\n",[],[106,236],"dfa17abd-085c-45c1-81d7-cd10c11b9b60","favicon.svg","01a061e4-3acb-7070-a926-842f4e54d674",["D",1788348742264],"\n",[],[106,246],"70c7bc19-dc6c-4ab8-b78f-c08042ad49f0","counter.ts","01a061e4-3acb-7070-a926-8362bdc08d67",["D",1788348742264],"script","const count = document.getElementById(\"count\")!;\nconst button = document.getElementById(\"increment\")!;\n\nbutton.addEventListener(\"click\", async () => {\n const res = await fetch(\"/api/increment\", { method: \"POST\" });\n const data = await res.json();\n count.textContent = String(data.count);\n});\n",[],[106,253],"3a3e2c48-1639-4f15-8dbd-d059b930e785",["D",1788348742264],"directory",[191,192,193],[106],["D",1788348742264],{"_11":12,"_149":77},{"_11":12,"_145":-5,"_76":77,"_30":75,"_146":147,"_148":24},{"_41":136,"_13":16,"_35":38,"_137":102,"_138":-5,"_139":-5,"_140":-5,"_141":-5,"_142":-5,"_143":14,"_144":12},"ctx",{"_56":-5,"_168":302,"_303":304,"_305":306,"_307":24,"_308":24,"_309":24,"_310":113,"_311":-5,"_312":-7,"_313":-7,"_314":26,"_315":24,"_316":24,"_317":-5,"_318":24,"_319":24,"_320":24,"_321":-5},"ENV",{"_273":274,"_275":276,"_277":16,"_278":279,"_280":281,"_282":283,"_284":285,"_286":287,"_288":289,"_290":291,"_292":293,"_294":295,"_296":297,"_298":299,"_300":301},"REACT_APP_SENTRY_DSN","https://586020d86f05489db63a554690acf1e9@o1398359.ingest.sentry.io/6724499","RENDER_GIT_COMMIT","e87eb04e707cf64e7e532c8e8ec395f209e17f15","RENDER_GIT_BRANCH","POSTHOG_API_TOKEN","phc_nmoyuAkStEZuUp69rYlg1DZgrIt19Gx0Y4Hwf8tGgJP","POSTHOG_API_HOST","https://wart.val.town","WEB_API_TEMPLATE","https://{val}.web.val.run","APP_URL","https://www.val.town","MODULE_URL","https://esm.town","VANITY_WEB_API_TEMPLATE","https://{label}.val.run/","DENOLS_URL","https://lsp.val.town","NODE_ENV","production","CLOUDFLARE_TURNSTILE_SITE_KEY","0x4AAAAAACtaIZJH7s9rBMZ6","GOOGLE_CLIENT_ID","875989696899-jtsqkhlbdv5jrlsk8631p7ipjg3c6o62.apps.googleusercontent.com","STRIPE_PUBLISHABLE_KEY","pk_live_51N2zvWEpZTTLipIkVEwXrUG9AT0yeOOEYxszarZT1jpsZV58Ly6wlg3SltZpHN26CUalOBmUSY7adQRQiSkCZz2500qSXNkf8Y","API_URL","https://api.val.town",[],"preferencesKeybindings","default","preferencesTheme","light","preferencesFixers","preferencesCopilot","preferencesSelectionAi","preferencesCloseBrackets","preferencesChatPanelState","preferencesDprint","preferencesDenofmt","notificationCount","flagDenols","isBusinessOrgMember","businessOrgHandle","isBusinessOrgAdmin","isHigherTownieTier","navCollapsed","currentOrgId"]

History · index.tsx