v0.7.18: landing, tools depth, media embeds in md editor, sonnet 5

.claude/commands/add-block.md

@@ -732,6 +732,13 @@ Please provide the SVG and I'll convert it to a React component.
 You can usually find this in the service's brand/press kit page, or copy it from their website.
 ```
 
+When converting the SVG: a **monochrome** logo (single white or black mark) must
+use `fill='currentColor'`, never a hardcoded `#fff`/`#000000`. Block icons render
+both inside their `bgColor` tile and "bare" on a neutral page (the home Suggested
+actions list) in light and dark mode; a hardcoded white/black mark goes invisible
+bare on the matching background. Multi-color brand logos keep their own fills.
+Verify with `bun run check:bare-icons`.
+
 ## Advanced Mode for Optional Fields
 
 Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. This includes:

.claude/commands/add-integration.md

@@ -279,6 +279,31 @@ Once the user provides the SVG:
 2. Create a React component that spreads props
 3. Ensure viewBox is preserved from the original SVG
 
+### Theme-safety (bare rendering) — REQUIRED
+
+The icon renders both inside its colored `bgColor` tile AND "bare" (no tile) on a
+neutral page — e.g. the home **Suggested actions** list — in both light and dark
+mode. A monochrome logo whose paths hardcode a single near-white or near-black
+fill is invisible bare on the matching background (white-on-white in light mode,
+black-on-black in dark mode).
+
+Rules when adding the SVG:
+
+- **Monochrome logos** (a single white or black mark): draw the shape with
+  `fill='currentColor'`, not `fill='#fff'` / `fill='#000000'`. It then inherits
+  white inside dark tiles, near-black inside light tiles (via
+  `getTileIconColorClass`), and the theme-aware `var(--text-icon)` bare — legible
+  everywhere. Do NOT set `iconColor` for these.
+- **Multi-color brand logos** (their own vivid fills): keep the hardcoded fills.
+  They read on any background. Only set `iconColor` (a vivid brand hex, never a
+  near-black/near-white tile color) if the bare icon should adopt a brand tint.
+- A large white shape with a tiny vivid accent (e.g. a logo where the body is the
+  white negative space) still vanishes bare — convert the body to `currentColor`.
+
+Verify with `bun run check:bare-icons` (also runs in CI). It flags purely
+monochrome hazards; for partial-accent logos, eyeball the suggested-actions list
+in both light and dark mode.
+
 ## Step 5: Create Triggers (Optional)
 
 If the service supports webhooks, create triggers using the generic `buildTriggerSubBlocks` helper.
@@ -466,6 +491,7 @@ If creating V2 versions (API-aligned outputs):
 - [ ] Asked user to provide SVG
 - [ ] Added icon to `components/icons.tsx`
 - [ ] Icon spreads props correctly
+- [ ] Monochrome marks use `fill='currentColor'` (not hardcoded white/black) so the icon renders bare in light AND dark mode — verified with `bun run check:bare-icons`
 
 ### Triggers (if service supports webhooks)
 - [ ] Created `triggers/{service}/` directory

.claude/skills/design-taste-frontend

@@ -0,0 +1 @@
+../../.agents/skills/design-taste-frontend

.claude/skills/emil-design-eng

@@ -0,0 +1 @@
+../../.agents/skills/emil-design-eng

.cursor/rules/constitution.mdc

@@ -1,6 +1,6 @@
 ---
 description: Sim product language, positioning, and tone guidelines
-globs: ["apps/sim/app/(landing)/**", "apps/sim/app/(home)/**", "apps/docs/**", "apps/sim/app/manifest.ts", "apps/sim/app/sitemap.ts", "apps/sim/app/robots.ts", "apps/sim/app/llms.txt/**", "apps/sim/app/llms-full.txt/**", "apps/sim/app/(landing)/**/structured-data*", "apps/docs/**/structured-data*", "**/metadata*", "**/seo*"]
+globs: ["apps/sim/app/(landing)/**", "apps/docs/**", "apps/sim/app/manifest.ts", "apps/sim/app/sitemap.ts", "apps/sim/app/robots.ts", "apps/sim/app/llms.txt/**", "apps/sim/app/llms-full.txt/**", "apps/sim/app/(landing)/**/structured-data*", "apps/docs/**/structured-data*", "**/metadata*", "**/seo*"]
 ---
 
 # Sim — Language & Positioning

.cursor/rules/landing-seo-geo.mdc

@@ -1,6 +1,6 @@
 ---
 description: SEO and GEO guidelines for the landing page
-globs: ["apps/sim/app/(home)/**/*.tsx"]
+globs: ["apps/sim/app/(landing)/**/*.tsx"]
 ---
 # Landing Page — SEO / GEO
 

.github/workflows/test-build.yml

@@ -125,6 +125,9 @@ jobs:
       - name: Client boundary import audit
         run: bun run check:client-boundary
 
+      - name: Bare-icon theme-safety audit
+        run: bun run check:bare-icons
+
       - name: Verify realtime prune graph
         run: bun run check:realtime-prune
 

README.md

@@ -12,7 +12,7 @@
 
 <p align="center">
   <a href="https://sim.ai" target="_blank" rel="noopener noreferrer">
-    <img src="apps/sim/public/static/readme-hero.gif" alt="Sim — your workflow agent for solving automations. Build, deploy, and manage AI agents visually, conversationally, or with code." width="100%"/>
+    <img src="apps/sim/public/static/readme-banner.png" alt="Sim — Integrate, Context, Build, and Monitor AI agents" width="100%"/>
   </a>
 </p>
 
@@ -35,7 +35,7 @@ Open [http://localhost:3000](http://localhost:3000)
 Docker must be installed and running. Use `-p, --port <port>` to run Sim on a different port, or `--no-pull` to skip pulling the latest Docker images.
 
 <p align="center">
-  <img src="apps/sim/public/static/readme-tour.gif" alt="How Sim works — Integrate, Context, Build, Monitor — shown end to end: start a chat to build an agent, connect Slack and other integrations, add a knowledge base, build the workflow visually, deploy it, and monitor runs in the logs" width="100%"/>
+  <img src="apps/sim/public/static/readme-platform.png" alt="The Sim platform — chat on the left, the visual workflow builder on the right" width="100%"/>
 </p>
 
 ## Capabilities
@@ -46,6 +46,33 @@ Docker must be installed and running. Use `-p, --port <port>` to run Sim on a di
 - Ingest files, knowledge bases, and structured table data
 - Monitor runs, logs, schedules, and workflow activity
 
+## One workspace, every surface
+
+<p align="center">Chat and workflows are just the start — tables, files, knowledge, and scheduled tasks all live in the same workspace.</p>
+
+<table>
+  <tr>
+    <td width="50%" valign="top">
+      <img src="apps/sim/public/static/readme-tables.png" alt="Tables in Sim — structured data your agents can query" width="100%"/>
+      <p align="center"><b>Tables</b> — a database, built in</p>
+    </td>
+    <td width="50%" valign="top">
+      <img src="apps/sim/public/static/readme-files.png" alt="Files in Sim — documents for your team and every agent" width="100%"/>
+      <p align="center"><b>Files</b> — one store for your team and every agent</p>
+    </td>
+  </tr>
+  <tr>
+    <td width="50%" valign="top">
+      <img src="apps/sim/public/static/readme-knowledge.png" alt="Knowledge bases in Sim — synced docs your agents can search" width="100%"/>
+      <p align="center"><b>Knowledge</b> — your agents' memory</p>
+    </td>
+    <td width="50%" valign="top">
+      <img src="apps/sim/public/static/readme-scheduled-tasks.png" alt="Scheduled tasks in Sim — recurring agent runs on a calendar" width="100%"/>
+      <p align="center"><b>Scheduled tasks</b> — runs on your schedule</p>
+    </td>
+  </tr>
+</table>
+
 ## Self-hosting
 
 ### Docker Compose
@@ -120,6 +147,9 @@ See the [environment variables reference](https://docs.sim.ai/self-hosting/envir
 
 ## Tech Stack
 
+<details>
+<summary>Next.js · Bun · PostgreSQL · Drizzle · Better Auth · Tailwind — and the rest of the stack</summary>
+
 - **Framework**: [Next.js](https://nextjs.org/) (App Router)
 - **Runtime**: [Bun](https://bun.sh/)
 - **Database**: PostgreSQL with [Drizzle ORM](https://orm.drizzle.team)
@@ -136,6 +166,8 @@ See the [environment variables reference](https://docs.sim.ai/self-hosting/envir
 - **Remote Code Execution**: [E2B](https://www.e2b.dev/)
 - **Isolated Code Execution**: [isolated-vm](https://github.com/laverdet/isolated-vm)
 
+</details>
+
 ## Contributing
 
 We welcome contributions! Please see our [Contributing Guide](.github/CONTRIBUTING.md) for details.

apps/docs/content/docs/en/integrations/asana.mdx

@@ -209,4 +209,187 @@ Add a comment (story) to an Asana task
 |   ↳ `gid` | string | Author GID |
 |   ↳ `name` | string | Author name |
 
+### `asana_create_subtask`
+
+Create a subtask under an existing Asana task
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `taskGid` | string | Yes | GID of the parent Asana task \(numeric string\) |
+| `name` | string | Yes | Name of the subtask |
+| `notes` | string | No | Notes or description for the subtask |
+| `assignee` | string | No | User GID to assign the subtask to |
+| `due_on` | string | No | Due date in YYYY-MM-DD format |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `ts` | string | Timestamp of the response |
+| `gid` | string | Subtask globally unique identifier |
+| `name` | string | Subtask name |
+| `notes` | string | Subtask notes or description |
+| `completed` | boolean | Whether the subtask is completed |
+| `created_at` | string | Subtask creation timestamp |
+| `permalink_url` | string | URL to the subtask in Asana |
+
+### `asana_delete_task`
+
+Delete an Asana task by its GID (moves it to the trash)
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `taskGid` | string | Yes | GID of the Asana task to delete \(numeric string\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `ts` | string | Timestamp of the response |
+| `gid` | string | GID of the deleted task |
+| `deleted` | boolean | Whether the task was deleted |
+
+### `asana_add_followers`
+
+Add one or more followers to an Asana task
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `taskGid` | string | Yes | GID of the Asana task \(numeric string\) |
+| `followers` | array | Yes | Array of user GIDs to add as followers to the task |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `ts` | string | Timestamp of the response |
+| `gid` | string | Task globally unique identifier |
+| `name` | string | Task name |
+| `followers` | array | Current followers on the task after the update |
+|   ↳ `gid` | string | Follower GID |
+|   ↳ `name` | string | Follower name |
+
+### `asana_create_project`
+
+Create a new project in an Asana workspace
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `workspace` | string | Yes | Asana workspace GID \(numeric string\) where the project will be created |
+| `name` | string | Yes | Name of the project |
+| `notes` | string | No | Notes or description for the project |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `ts` | string | Timestamp of the response |
+| `gid` | string | Project globally unique identifier |
+| `name` | string | Project name |
+| `notes` | string | Project notes or description |
+| `archived` | boolean | Whether the project is archived |
+| `color` | string | Project color |
+| `created_at` | string | Project creation timestamp |
+| `modified_at` | string | Project last modified timestamp |
+| `permalink_url` | string | URL to the project in Asana |
+
+### `asana_get_project`
+
+Retrieve a single Asana project by its GID
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `projectGid` | string | Yes | Asana project GID \(numeric string\) to retrieve |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `ts` | string | Timestamp of the response |
+| `gid` | string | Project globally unique identifier |
+| `name` | string | Project name |
+| `notes` | string | Project notes or description |
+| `archived` | boolean | Whether the project is archived |
+| `color` | string | Project color |
+| `created_at` | string | Project creation timestamp |
+| `modified_at` | string | Project last modified timestamp |
+| `permalink_url` | string | URL to the project in Asana |
+
+### `asana_list_workspaces`
+
+List all Asana workspaces and organizations the authenticated user belongs to
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `ts` | string | Timestamp of the response |
+| `workspaces` | array | Array of workspaces |
+|   ↳ `gid` | string | Workspace GID |
+|   ↳ `name` | string | Workspace name |
+|   ↳ `resource_type` | string | Resource type \(workspace\) |
+
+### `asana_create_section`
+
+Create a new section in an Asana project
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `projectGid` | string | Yes | GID of the Asana project \(numeric string\) to add the section to |
+| `name` | string | Yes | Name of the section |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `ts` | string | Timestamp of the response |
+| `gid` | string | Section globally unique identifier |
+| `name` | string | Section name |
+| `created_at` | string | Section creation timestamp |
+
+### `asana_list_sections`
+
+List all sections in an Asana project
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `projectGid` | string | Yes | GID of the Asana project \(numeric string\) to list sections from |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `ts` | string | Timestamp of the response |
+| `sections` | array | Array of sections in the project |
+|   ↳ `gid` | string | Section GID |
+|   ↳ `name` | string | Section name |
+|   ↳ `resource_type` | string | Resource type \(section\) |
+