mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-08-28 05:25:33 +00:00
434c86e2c3
Keep docs asset URLs repo-root-relative and pass images as literal MDX children so Mintlify can compile them through OptimizedImage under the /docs mount. Mintlify's official guidance says: “Image paths are root-relative from your docs repository.” It also says relative paths such as `./screenshot.png` are unsupported. See [Image embeds](https://www.mintlify.com/docs/create/image-embeds). The existing `/images/...` paths were correct. The failure came from passing them through custom-component string props, which kept Mintlify from seeing those images during its MDX transform. - fix hero, building-block, and Slack avatar images - preserve Slack avatar clipping - normalize Hermes and Company Brain icon sizing Tested with Mintlify validation, broken-link checks, and browser checks across every changed route.
51 lines
2.1 KiB
Text
51 lines
2.1 KiB
Text
---
|
|
title: "Sandbox Debugging"
|
|
sidebarTitle: "Sandbox"
|
|
description: "Hand it a failing test — it runs the code in an isolated workspace and reports back"
|
|
icon: "terminal"
|
|
---
|
|
|
|
import { SlackThread, SlackMessage, Mention } from "/snippets/slack-message.mdx";
|
|
|
|
## The scenario
|
|
|
|
A test is failing and the stack trace alone isn't enough. You want Company Brain to actually run the code, not just describe what it *would* do.
|
|
|
|
## What happens
|
|
|
|
<SlackThread channel="#eng">
|
|
<SlackMessage self hasAvatar time="5:41 PM">
|
|
<img src="/images/company-brain/dhravya-slack-icon.jpg" alt="" />
|
|
<Mention>supermemory</Mention> the `permissions.lease` unit test is failing on main — can you reproduce and tell me why?
|
|
</SlackMessage>
|
|
<SlackMessage bot hasAvatar time="5:42 PM">
|
|
<img src="/images/company-brain/supermemory-slack-icon.png" alt="" />
|
|
Reproduced in a sandbox against `main`.
|
|
|
|
**Failure:** `permissions.lease` expects temporary access to expire in 15 minutes, but the fixture still asserts 30.
|
|
**Cause:** the default was shortened in `#1188`; the unit test wasn't updated.
|
|
**Fix:** point the assertion at the shared default so it can't drift again.
|
|
</SlackMessage>
|
|
</SlackThread>
|
|
|
|
## What's really going on
|
|
|
|
Company Brain spins up an **isolated workspace**, checks out what it needs, runs the command, and reads the output. It's not guessing from static code alone — it's executing.
|
|
|
|
Guardrails are intentional, so it's safe to hand real tasks to:
|
|
|
|
- No `git push`, no deploys
|
|
- No elevated privileges (`sudo` and similar are blocked)
|
|
- No reaching arbitrary internal network addresses
|
|
- No long-running dev servers
|
|
|
|
Think of it as a sealed workbench: useful for reproduce / inspect / explain loops, not for shipping changes on your behalf.
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Acting in tools" icon="wrench" href="/company-brain/use-cases/acting-in-tools">
|
|
When the next step is a Linear issue or a PR lookup.
|
|
</Card>
|
|
<Card title="What you can do" icon="sparkles" href="/company-brain/use-cases/overview">
|
|
All the scenario walkthroughs.
|
|
</Card>
|
|
</CardGroup>
|