Jon Gottfried for The DEV Team

Posted on Mar 4 • Edited on Mar 6

Share, Embed, and Curate Agent Sessions on DEV [Beta]

#ai #forem #devto #gemini

Authors can now upload Agent Session transcripts to their DEV account. Those transcripts can be curated, sliced up, shared publicly, and embedded into posts. This is a beta feature, and we are actively looking for feedback!

Every day, more people are creating software for the first time. Some have long histories as developers, and some have never seen a line of code in their life. In most cases, they're using the same tooling - coding agents. And yet, as these tools become ubiquitous there are surprisingly few ways to share your workflows and results in a standardized way beyond screenshots. Each tool has its own share link generator, each tool outputs logs in a different format. There are a few nascent projects out there to help, but they generally exist as standalone utilities or don't solve the sharing problem explicitly in a way that works on DEV.

We decided to solve that problem by making it possible to upload your transcripts to DEV, automatically parse them into a standardized format, and embed whole or partial sessions into your posts in a way that fits naturally into technical writing.

Supported Platforms

To start with, our parser supports Gemini CLI, Codex, Claude Code, Pi, and GitHub Copilot CLI. If you use a different tool, you're encouraged to open a PR or Issue on Forem to add a new parser yourself or ask us to do so. As an example, you can check out how our Gemini CLI parser works in our GitHub commit:
https://github.com/forem/forem/commit/0230aa56c1b4e59480c1de95822824f62f95aaa4#diff-a096c013f50a6f14bf8c09ab7c693348b9b704adeb99517f6089a511d025daa0

Example Session

Here's a session from an example app I built using Gemini CLI for my pet guinea pig Pearl (obligatory pic in comments).

Wheeky Gemini App

You

build me a simple web app to let my guinea pig tell me what food it wants

Agent

Clarifying Application Needs / Defining Food Selection UI / Mapping Out The App's Flow

I'll build a vibrant, touch-friendly web app called "Pui Pui Picker" designed for guinea pigs (and their humans).

The Plan:

Scaffold: Create a React + TypeScript project using Vite.
Design: A "big button" interface with high-contrast colors and bouncy animations to make it engaging.
Features:
- Food Grid: Large cards for Hay, Carrots, Romaine, and Bell Peppers.
- Pui Pui Feedback: Visual and text-based "wheeking" feedback when an item is selected.
- History: A small "Last Requested" log to track what the piggie "chose."
Styling: Custom Vanilla CSS for a polished, modern look without external dependencies.

Does this sound like a good start for your guinea pig? Or should I add specific snacks they love?

I will start by scaffolding the project.

Agent

You

let's go simpler than vite and react

Agent

Seeking Simplification for App / Constructing the index.html

I'll create a single-file, vibrant, and touch-friendly HTML application called "The Wheeky Menu". It will use large, colorful buttons and bouncy animations—perfect for a guinea pig's "input" (or a human's finger).

The Plan:

Single File: Everything (HTML, CSS, JS) in index.html for instant loading.
Piggie-Centric UI:
- Large Interaction Zones: Easy-to-hit cards for Hay, Carrots, Peppers, and Lettuce.
- Visual Feedback: Cards will "pop" and flash when tapped.
Features:
- "Wheek!" Notification: A large visual alert showing what was picked.
- Order History: A simple log at the bottom to see what the piggie "requested" most.

I will now create the index.html file.

Agent

Input

{"content":"<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n    <meta charset=\"UTF-8\">\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no\...

Output

Successfully created and wrote to new file: /Users/jonmarkgo/Documents/GitHub/gemini-guinea-pig/index.html. Here is the updated code:
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
    <title>Wheeky Menu - Piggie Food Picker</title>
    <style>
        :root {
            --bg-color: #fdf6e3;
            --card-bg: #ffffff;
            --text-color: #5d4037;
            --accent-color: #ff8a65;
            --shadow: 0 8px 16px rgba(0,0,0,0.1);
            
            --color-hay: #fff176;
            --color-carrot: #ffb74d;
            --color-pepper: #ef5350;
            --color-lettuce: #81c784;
        }

        * {
            box-sizing: border-box;
            -webkit-tap-highlight-color: transparent;
        }

        body {
            font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
            background-color: var(--bg-color);
            color: var(--text-color);
            margin: 0;
            display: flex;
            flex-direction: column;
            align-items: center;
            min-height: 100vh;
            padding: 20px;
            overflow-x: hidden;
        }

        header {
            text-align: center;
            margin-bottom: 30px;
        }

        h1 {
            font-size: 2.5rem;
            margin: 0;
            color: var(--accent-color);
            text-shadow: 2px 2px 0px #fff;
        }

        p.subtitle {
            font-style: italic;
            margin-top: 5px;
            opacity: 0.8;
        }

        .grid {
            display: grid;
            grid-template-columns: repeat(2, 1fr);
            gap: 20px;
            width: 100%;
            max-width: 600px;
        }

        .food-card {
            background: var(--card-bg);
            border-radius: 24px;
            padding: 30px 10px;
            text-align: center;
            box-shadow: var(--shadow);
            cursor: pointer;
            transition: transform 0.1s, box-shadow 0.1s;
            border: 4px solid transparent;
            display: flex;
            flex-direction: column;
            align-items: center;
            justify-content: center;
            user-select: none;
        }

        .food-card:active {
            transform: scale(0.92);
            box-shadow: 0 2px 4px rgba(0,0,0,0.1);
        }

        .food-card .emoji {
            font-size: 4rem;
            margin-bottom: 10px;
        }

        .food-card .label {
            font-weight: bold;
            font-size: 1.2rem;
            text-transform: uppercase;
            letter-spacing: 1px;
        }

        /* Food Specific Borders */
        .card-hay { border-color: var(--color-hay); }
        .card-carrot { border-color: var(--color-carrot); }
        .card-pepper { border-color: var(--color-pepper); }
        .card-lettuce { border-color: var(--color-lettuce); }

        /* Announcement Overlay */
        #announcement {
            position: fixed;
            top: 50%;
            left: 50%;
            transform: translate(-50%, -50%) scale(0);
            background: white;
            padding: 40px;
            border-radius: 50%;
            box-shadow: 0 0 100px rgba(0,0,0,0.2);
            z-index: 100;
            text-align: center;
            pointer-events: none;
            transition: transform 0.3s cubic-bezier(0.175, 0.885, 0.32, 1.275);
            border: 10px solid var(--accent-color);
        }

        #announcement.show {
            transform: translate(-50%, -50%) scale(1);
        }

        #announcement h2 {
            margin: 0;
            font-size: 3rem;
        }

        /* History Log */
        .history {
            margin-top: 40px;
            width: 100%;
            max-width: 600px;
            background: rgba(255,255,255,0.5);
            padding: 20px;
            border-radius: 16px;
        }

        .history h3 {
            margin-top: 0;
            font-size: 1rem;
            opacity: 0.6;
            text-transform: uppercase;
        }

        #log-list {
            list-style: none;
            padding: 0;
            margin: 0;
            display: flex;
            flex-wrap: wrap;
            gap: 10px;
        }

        .log-item {
            background: white;
            padding: 5px 12px;
            border-radius: 20px;
            font-size: 0.9rem;
            box-shadow: 0 2px 4px rgba(0,0,0,0.05);
            animation: slideIn 0.3s ease-out;
        }

        @keyframes slideIn {
            from { opacity: 0; transform: translateY(10px); }
            to { opacity: 1; transform: translateY(0); }
        }

        @media (max-width: 400px) {
            .grid { grid-template-columns: 1fr; }
            h1 { font-size: 1.8rem; }
        }
    </style>
</head>
<body>

    <header>
        <h1>WHEEKY MENU</h1>
        <p class="subtitle">Let the piggie decide!</p>
    </header>

    <div class="grid">
        <div class="food-card card-hay" onclick="makeRequest('HAY', '🌾')">
            <span class="emoji">🌾</span>
            <span class="label">Hay</span>
        </div>
        <div class="food-card card-carrot" onclick="makeRequest('CARROT', '🥕')">
            <span class="emoji">🥕</span>
            <span class="label">Carrot</span>
        </div>
        <div class="food-card card-pepper" onclick="makeRequest('PEPPER', '🫑')">
            <span class="emoji">🫑</span>
            <span class="label">Pepper</span>
        </div>
        <div class="food-card card-lettuce" onclick="makeRequest('LETTUCE', '🥬')">
            <span class="emoji">🥬</span>
            <span class="label">Lettuce</span>
        </div>
    </div>

    <div id="announcement">
        <h2 id="announcement-text">WHEEK!</h2>
    </div>

    <div class="history">
        <h3>Request History</h3>
        <div id="log-list">
            <!-- History items will appear here -->
        </div>
    </div>

    <script>
        const announcement = document.getElementById('announcement');
        const announcementText = document.getElementById('announcement-text');
        const logList = document.getElementById('log-list');
        let timer;

        function makeRequest(food, emoji) {
            // Show announcement
            announcementText.innerHTML = `${emoji}<br>WHEEK!<br>${food}`;
            announcement.classList.add('show');

            // Add to history
            const item = document.createElement('div');
            item.className = 'log-item';
            const time = new Date().toLocaleTimeString([], { hour: '2-digit', minute: '2-digit' });
            item.textContent = `${time}: ${emoji} ${food}`;
            logList.prepend(item);

            // Keep only last 10
            if (logList.children.length > 10) {
                logList.removeChild(logList.lastChild);
            }

            // Hide announcement after delay
            clearTimeout(timer);
            timer = setTimeout(() => {
                announcement.classList.remove('show');
            }, 1500);

            // Optional: Simple Vibration for mobile
            if (navigator.vibrate) {
                navigator.vibrate(100);
            }
        }
    </script>
</body>
</html>

Agent

Constructing The Interface / Refining The UX Design

The "Wheeky Menu" is ready! It's a single-file web app with large, high-contrast buttons designed for easy "selection" (by snout or finger).

How to use:

Open the file: You can open index.html directly in any web browser.
Piggie Input: Place your tablet or phone on the floor or near the cage. When your guinea pig taps or "boops" a card:
- A large "WHEEK!" announcement pops up.
- The request is added to the Request History at the bottom (so you can see what they picked if you step away).
- On mobile devices, it will provide a small vibration (haptic feedback) when touched.

I've used high-contrast colors and bouncy animations to make it visually stimulating. Enjoy the wheeking!

You

Find the current Gemini CLI session log file. Look in ~/.gemini/sessions/ for the most recently modified .json or .jsonl file.

Then run the devto command to upload it:

Error: No file specified. Use --auto or provide a file path.\nRun 'devto --help' for usage.
[Shell command 'devto --yes --tool gemini_cli --title "" "$(ls -t ~/.gemini/sessions//*.json ~/.gemini/sessions//*.jsonl 2>/dev/null | head -1)"' exited with code 1]

If devto is not installed, use curl directly:

jq: Bad JSON in --rawfile body : Could not open : No such file or directory
[Shell command 'TMPJSON=$(mktemp) && jq -n --arg title "" --rawfile body "$(ls -t ~/.gemini/sessions//*.json ~/.gemini/sessions//*.jsonl 2>/dev/null | head -1)" '{title: $title, tool_name: "gemini_cli", body: $body}' > "$TMPJSON" && curl -s -X POST "${DEVTO_HOST:-https://dev.to}/api/agent_sessions" -H "Content-Type: application/json" -H "Accept: application/vnd.forem.api-v1+json" -H "api-key: $DEVTO_API_KEY" -d @"$TMPJSON" && rm -f "$TMPJSON"' exited with code 2]

After uploading, display the URL of the created session to the user.

Agent

Examining Upload Strategies / Implementing Dev Upload Skill

I will activate the dev-upload skill to securely and efficiently upload your session log to DEV.to.

Agent

Input

{
  "name": "dev-upload"
}

Output

<activated_skill name="dev-upload">
  <instructions>
    # Upload Session to DEV

Upload the current session transcript to [DEV](https://dev.to) as an Agent Session.

## Steps

### 1. Find the transcript

Find the current session's transcript file — the most recently modified `.jsonl` file:
- Claude Code: `~/.claude/projects/` (recursive)
- Codex: `~/.codex/sessions/`
- Gemini CLI: `~/.gemini/sessions/`
- GitHub Copilot: `~/.copilot/`
- Pi: `~/.pi/sessions/`

Use the agent's own session context if available to identify the exact path.

### 2. Load config and check for API key

Load all config in a single bash call:

```bash
if [ -f ~/.config/devto/config ]; then source ~/.config/devto/config; fi
API_KEY="${DEVTO_API_KEY:-${API_KEY:-}}"
HOST="${DEVTO_HOST:-https://dev.to}"
echo "API_KEY=${API_KEY:+SET}"
echo "HOST=$HOST"
```

If no key is found:
1. Tell the user they need a DEV API key and link them to https://dev.to/settings/extensions to generate one.
2. Ask the user to paste their key here in the chat.
3. Once they provide it, save it (along with the host) so they never have to do this again:

```bash
mkdir -p ~/.config/devto
cat > ~/.config/devto/config <<'CONF'
DEVTO_API_KEY="THE_KEY_THEY_GAVE_YOU"
DEVTO_HOST="https://dev.to"
CONF
```

4. Then continue with the upload. Do NOT stop or ask the user to run commands themselves.

### 3. Upload

Do the entire upload in a single bash call. Replace TRANSCRIPT, TITLE, HOST, and API_KEY with actual values:

```bash
set -e
TRANSCRIPT="/path/to/session.jsonl"
TITLE="the session title"
HOST="https://dev.to"
API_KEY="the-key"

TMPJSON=$(mktemp)
trap "rm -f '$TMPJSON'" EXIT

jq -n \
  --arg title "$TITLE" \
  --arg tool_name "auto" \
  --rawfile body "$TRANSCRIPT" \
  '{title: $title, tool_name: $tool_name, body: $body}' > "$TMPJSON"

RESPONSE=$(curl -s -w "\n%{http_code}" \
  -X POST "$HOST/api/agent_sessions" \
  -H "Content-Type: application/json" \
  -H "Accept: application/vnd.forem.api-v1+json" \
  -H "api-key: $API_KEY" \
  -d @"$TMPJSON")

HTTP_CODE=$(echo "$RESPONSE" | tail -1)
BODY=$(echo "$RESPONSE" | sed '$d')

if [ "$HTTP_CODE" = "201" ]; then
  URL=$(echo "$BODY" | jq -r '.url // empty')
  SLUG=$(echo "$BODY" | jq -r '.slug // empty')
  echo "Uploaded successfully!"
  echo "URL: ${URL:-$HOST/agent_sessions/$SLUG}"
else
  echo "Upload failed (HTTP $HTTP_CODE)"
  echo "$BODY" | jq -r '.error // .' 2>/dev/null || echo "$BODY"
fi
```

### 4. Show result

Display the session URL to the user on success. On failure, show the error message and suggest fixes.

## Notes

- If the user provided a title argument, use it. Otherwise generate one from the conversation context.
- The server auto-detects the tool from the transcript content when `tool_name` is `"auto"`.
- Uploads are **private (unlisted) by default**.
- The server applies automatic redaction of common secrets (API keys, tokens, passwords).
- Always substitute actual values into the bash script — do not rely on environment variables being set in the agent's shell.
  </instructions>

  <available_resources>
    Showing up to 200 items (files + folders).

/Users/jonmarkgo/.agents/skills/dev-upload/
├───SKILL.md
└───scripts/
    └───forem-upload
  </available_resources>
</activated_skill>

Agent

Defining the Upload Process / Analyzing the Configuration Steps

I'll locate your most recent session log and check for a DEV.to API key to begin the upload.

Agent

Searching the File System / Refining the Search Strategy

I'll look for the session log again, including both .json and .jsonl files across all session subdirectories.

Agent

Exploring the Directory

I'll list the contents of ~/.gemini/sessions/ to find the exact session log files.

Agent

Examining Session Locations / Inspecting Gemini Directory Contents

I'll list the contents of the ~/.gemini/ directory to locate the session logs.

Agent

Checking the History

I'll list the contents of ~/.gemini/history/ to find the session log.

Agent

Examining Project Location

I'll list the contents of ~/.gemini/history/gemini-guinea-pig/ to find the current session's log.

Agent

Beginning File Enumeration

I'll list all files in ~/.gemini/history/gemini-guinea-pig/ to find the session log.

Agent

Pinpointing the Missing Path / Re-evaluating the Scope

I'll list the contents of ~/.gemini/tmp/gemini-guinea-pig/ to find the session log.

Agent

Investigating Log Location

I'll read the first 10 lines of logs.json to see if it's the session log.

Agent

Investigating the Discrepancy / Unraveling File Paths

I'll look for any other directories starting with 's' in ~/.gemini/ to find the sessions folder.

Agent

Examining Possible Locations

I'll list all directories starting with .gemini in my home directory to find the session logs.

Agent

Searching for Session Logs / Identifying Alternative Locations

I'll search for all .json and .jsonl files in ~/.gemini/ to find the correct session log.

Agent

Input

{
  "description": "Searching recursively for .json and .jsonl files in the ~/.gemini directory.",
  "command": "find ~/.gemini/ -name \"*.json\" -o -name \"*.jsonl\" | head -n 20"
}

Output

Output: /Users/jonmarkgo/.gemini/google_accounts.json
/Users/jonmarkgo/.gemini/state.json
/Users/jonmarkgo/.gemini/oauth_creds.json
/Users/jonmarkgo/.gemini/settings.json
/Users/jonmarkgo/.gemini/projects.json
/Users/jonmarkgo/.gemini/trustedFolders.json
/Users/jonmarkgo/.gemini/antigravity/mcp_config.json
/Users/jonmarkgo/.gemini/mcp-oauth-tokens-v2.json
/Users/jonmarkgo/.gemini/tmp/08d27515e40a8c790d53798895cf6650d5843987a3978f7ef5be01987a09b3e1/logs.json
/Users/jonmarkgo/.gemini/tmp/a9c39dae5288a24cdef1cf1d8c6bc99a5cf8b751707de794545fc5f5986be7b2/logs.json
/Users/jonmarkgo/.gemini/tmp/dd9dc36095d552fc5d0c79d94e889e2c50c1b76a76ea3f41ac6b22dd6076ce19/logs.json
/Users/jonmarkgo/.gemini/tmp/dd9dc36095d552fc5d0c79d94e889e2c50c1b76a76ea3f41ac6b22dd6076ce19/chats/session-2025-12-04T21-23-e153598e.json
/Users/jonmarkgo/.gemini/tmp/gemini-guinea-pig/logs.json
/Users/jonmarkgo/.gemini/tmp/gemini-guinea-pig/chats/session-2026-03-04T01-15-295d2fe2.json
/Users/jonmarkgo/.gemini/tmp/gemini-guinea-pig/chats/session-2026-03-04T12-42-295d2fe2.json
/Users/jonmarkgo/.gemini/tmp/79261791c475d806f2ff6cdf73b50843055032e35b2854d7e91e3a92762f2e96/logs.json
/Users/jonmarkgo/.gemini/tmp/79261791c475d806f2ff6cdf73b50843055032e35b2854d7e91e3a92762f2e96/chats/session-2025-12-06T18-02-b9fe7181.json
/Users/jonmarkgo/.gemini/tmp/79261791c475d806f2ff6cdf73b50843055032e35b2854d7e91e3a92762f2e96/chats/session-2025-11-18T16-06-1f38a3eb.json
/Users/jonmarkgo/.gemini/tmp/79261791c475d806f2ff6cdf73b50843055032e35b2854d7e91e3a92762f2e96/chats/session-2025-11-18T18-32-22205976.json
/Users/jonmarkgo/.gemini/tmp/79261791c475d806f2ff6cdf73b50843055032e35b2854d7e91e3a92762f2e96/chats/session-2025-11-18T16-52-0863224c.json
Process Group PGID: 76229

Agent

Analyzing File Locations / Pinpointing Key Files

I'll select the latest session log from ~/.gemini/tmp/gemini-guinea-pig/chats/ and upload it to DEV.to using the discovered session file and your API key.

Agent

Reviewing the Upload Outcome / Confirming the URL Delivery

The session transcript has been successfully uploaded to DEV.to. You can view it here:

Session URL: https://dev.to/agent_sessions/wheeky-menu-piggie-food-picker-popwfq

Let's check out how the upload, curation, and embedding workflow works.

Upload a Session

First, you need to upload a session. You can drag and drop your session transcripts via your browser on the Agent Sessions page. We will soon be launching a CLI and Agent skill to give you a slash command for uploads as well.

Curate a Session

Once you upload the session, you curate which pieces of the session transcript get saved on DEV as part of your whole-session embed. You can mass enable/disable different pieces of your transcript, as shown here.

Slice Up a Session

If you don't want to embed your whole session (even in curated form) you can also use the Slice tool to create a sub-transcript that can include any and all parts of a session. You can have multiple Slices per session, if you want to break up your prompt and embed it in different places in your post.

Once you've curated which pieces of your session transcript you want to save on DEV (in whole or as part of a slice), you Save & Upload it so you can start embedding or sharing it.

Share a Session

Lastly, to make this utility more generally useful beyond DEV, you can also share curated Agent Sessions publicly by using the Make Public button. See my session here.

Note: Please be very cognizant of what potentially sensitive data/keys might be in your transcripts. We have a redaction layer built in to the parser, but it is not going to catch every edge case. Do not upload sessions or data that you do not own, or that may open you up to security vulnerabilities.

We look forward to seeing what you build and share with this new feature. Happy hacking!

Top comments (19)

Daniel Nwaneri • Mar 5 • Edited

The slice-before-upload gap @pascal_cescato_692b7a8a20 identified is the right one. for embedding in technical writing, the useful unit is usually a specific exchange. The moment the agent made the wrong decision or the prompt that finally produced the right output. uploading a full session to get access to two minutes of it adds friction that'll stop most writers from using the feature at all.

Building something adjacent — a browser extension for capturing Claude conversations with semantic search and MCP access. The portable conversation artifact problem is the same one you're solving here, different layer.
will test with a Claude Code session.

Jon Gottfried The DEV Team • Mar 5

Will see what we can do here :)

Jon Gottfried The DEV Team • Mar 6

Based on your and Pascal's feedback I just shipped a major refactor to handle more of the curation/processing on the client side and remove the 10MB limit as a result. Curious to hear your thoughts!

Daniel Nwaneri • Mar 6

That's a fast turnaround. will test with a Claude Code session next week and report back.
Removing the 10MB limit by moving curation client-side is the right architectural call. The constraint was in the wrong place. The useful unit for embedding in technical writing is a specific exchange, not a full session, so client-side selection before upload makes more sense than upload-then-slice anyway.

Pascal CESCATO • Mar 4

It's an awesome feature! I've discover it this afternoon, and tested… I'm found of!

Jon Gottfried The DEV Team • Mar 4

Awesome - have you used it in a post yet? Would love to check it out if so

Pascal CESCATO • Mar 4

Unfortunately not yet. This feature arrived a bit too late for the article where I could have used it… and my sessions (GitHub Copilot CLI) exceed the 10MB limit. That said, it's definitely on my radar for a future article!

Jon Gottfried The DEV Team • Mar 4

Do you think that limit will generally be too low?

Pascal CESCATO • Mar 4

The limit itself may not be the core issue — if I had known about it from the start, I would have managed my sessions differently: intermediate saves, one session per feature. The real pain was discovering it after the fact, with a session already too large to use.

Also, for an article, you wouldn't embed a full 10MB session anyway — you'd want a meaningful excerpt. So the real need might be less about raising the limit and more about having a way to extract or slice a specific part of a session. Which, coincidentally, might be my next little experimentation… 😄

Jon Gottfried The DEV Team • Mar 4

Good point. We have a slice feature but it's post upload. Maybe there's a way to move it earlier in the process

Pascal CESCATO • Mar 4

Exactly — the slices feature is great, but it's a post-upload tool. If the session exceeds 10MB, you never get past the upload step, so slicing never becomes an option. Moving that capability earlier in the process would be the key!

Jon Gottfried The DEV Team • Mar 6

Just shipped a major refactor to handle more of the curation/processing on the client side and remove the 10MB limit as a result. Curious to hear your thoughts!

Pascal CESCATO • Mar 6

I just tried, works fine! So I've included some exchanges with Github Copilot CLI here: dev.to/pascal_cescato_692b7a8a20/a.... Thanks @jonmarkgo!

Jon Gottfried The DEV Team • Mar 6

Love it!

Yanko Alexandrov • Mar 6

This is exciting! Agent session sharing could be huge for collaborative debugging. I run multi-agent systems where sub-agents handle different tasks and being able to share a specific agent's session with a teammate would save hours of 'let me explain what happened'. Will this support embedding in external docs?

Jon Gottfried The DEV Team • Mar 6

External embedding is not supporting by default, but happy to look into that if you want to open a feature request Issue on GitHub github.com/forem/forem/issues