DEV Community: Jon Gottfried

DEV (and Forem) have supported RSS feed imports for a long time. They are the primary way to automatically syndicate posts from an external blog into the DEV community, complete with proper canonical URL referencing to preserve your SEO ranking. Historically, each user was limited to one RSS feed that they could sync to DEV.

Let's check out the brand new upgraded functionality. If you head over to the RSS Import Feeds page under your Dashboard, you can add your first RSS feed from your (or your team's) external blog.

As part of the import process, you can set which organization on DEV these imported articles will be associated with. You can also set a default author. If the author of the imported post does not have an account on DEV, the article will be listed under your default author instead.

You still have the same two options as before, to Mark the RSS source as canonical URL by default (which we recommend doing for SEO purposes, unless you are fully moving your blog to DEV and shutting down the old version). You can also Replace self-referential links with DEV Community-specific links - this option will update URLs inline to point to the imported version of an article on DEV instead of the original version. This is useful if you're migrating your entire blog onto DEV.

Once you've added your Feed Source, a background job gets queued up to import your posts. Just refresh the page a few minutes later to see the status. If it was successful, you'll see a list of imported drafts under your Import History. You can also see which articles were skipped or errored out. If there's no new articles at all, it will be shown under the routine checks dropdown at the bottom of the page.

Go through each edited article, edit the draft, and publish your post. In some situations you may need to publish it by modifying the markdown published tag to be set to true instead of false. Saving it will then publish the post.

On published posts with canonical links, you'll see a linkback on the post author line.

We look forward to seeing y'all syndicate your blogs into the DEV community and to any feature feedback you have here!

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

Jon Gottfried — Wed, 04 Mar 2026 20:19:27 +0000

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

▸ Shell {"command":"npm create vite@latest . -- --template react-ts && npm install","...

Input

{
  "command": "npm create vite@latest . -- --template react-ts && npm install",
  "description": "Scaffolding the React TypeScript project using Vite and installing dependencies."
}

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

▸ WriteFile {"content":"<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"...

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

▸ Activate Skill {"name":"dev-upload"}

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

▸ Shell {"description":"Locating the most recent session log and checking for a DEV.t...

Input

{"description":"Locating the most recent session log and checking for a DEV.to API key.","command":"# Find the most recent session log\nTRANSCRIPT=$(ls -t ~/.gemini/sessions/*.jsonl 2>/dev/null | head...

Output

Output: TRANSCRIPT=
API_KEY=SET
HOST=https://dev.to
Process Group PGID: 73065

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

▸ Shell {"command":"# Find the most recent session log\nTRANSCRIPT=$(ls -t ~/.gemini/...

Input

{"command":"# Find the most recent session log\nTRANSCRIPT=$(ls -t ~/.gemini/sessions/**/*.json ~/.gemini/sessions/**/*.jsonl 2>/dev/null | head -1)\necho \"TRANSCRIPT=$TRANSCRIPT\"","description":"Se...

Output

Output: TRANSCRIPT=
Process Group PGID: 73508

Agent

Exploring the Directory

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

Agent

▸ Shell {"command":"ls -R ~/.gemini/sessions/ | head -n 20","description":"Listing th...

Input

{
  "command": "ls -R ~/.gemini/sessions/ | head -n 20",
  "description": "Listing the contents of the Gemini CLI sessions directory."
}

Output

Output: ls: /Users/jonmarkgo/.gemini/sessions/: No such file or directory
Process Group PGID: 73515

Agent

Examining Session Locations / Inspecting Gemini Directory Contents

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

Agent

▸ Shell {"command":"ls -F ~/.gemini/","description":"Listing the contents of the ~/.g...

Input

{
  "command": "ls -F ~/.gemini/",
  "description": "Listing the contents of the ~/.gemini directory."
}

Output

Output: antigravity/                    google_accounts.json            mcp-oauth-tokens-v2.json        settings.json                   tmp/
commands/                       history/                        oauth_creds.json                settings.json.orig              trustedFolders.json
GEMINI.md                       installation_id                 projects.json                   state.json                      user_id
Process Group PGID: 73530

Agent

Checking the History

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

Agent

▸ Shell {"command":"ls -F ~/.gemini/history/ | head -n 20","description":"Listing the...

Input

{
  "command": "ls -F ~/.gemini/history/ | head -n 20",
  "description": "Listing the contents of the ~/.gemini/history directory."
}

Output

Output: cookieparser/
gemini-dog-app/
gemini-guinea-pig/
mlh-core/
Process Group PGID: 73565

Agent

Examining Project Location

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

Agent

▸ Shell {"command":"ls -t ~/.gemini/history/gemini-guinea-pig/*.jsonl 2>/dev/null | h...

Input

{
  "command": "ls -t ~/.gemini/history/gemini-guinea-pig/*.jsonl 2>/dev/null | head -1",
  "description": "Searching for the most recent session log in the history directory."
}

Output

Output: (empty)
Process Group PGID: 74637

Agent

Beginning File Enumeration

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

Agent

▸ Shell {"command":"ls -R ~/.gemini/history/gemini-guinea-pig/ | head -n 100","descri...

Input

{
  "command": "ls -R ~/.gemini/history/gemini-guinea-pig/ | head -n 100",
  "description": "Listing all files in the history folder to locate the log file."
}

Output

Output: (empty)
Process Group PGID: 75100

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

▸ Shell {"command":"ls -F ~/.gemini/tmp/gemini-guinea-pig/ | head -n 20","description...

Input

{
  "command": "ls -F ~/.gemini/tmp/gemini-guinea-pig/ | head -n 20",
  "description": "Listing the contents of the ~/.gemini/tmp/gemini-guinea-pig directory."
}

Output

Output: chats/
logs.json
Process Group PGID: 75368

Agent

Investigating Log Location

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

Agent

▸ Shell {"command":"head -n 10 ~/.gemini/tmp/gemini-guinea-pig/logs.json","descriptio...

Input

{
  "command": "head -n 10 ~/.gemini/tmp/gemini-guinea-pig/logs.json",
  "description": "Reading the beginning of logs.json to confirm its format."
}

Output

Output: [
  {
    "sessionId": "295d2fe2-6276-49c4-9229-db8a61d33f2a",
    "messageId": 0,
    "type": "user",
    "message": "build me a simple web app to let my guinea pig tell me what food it wants",
    "timestamp": "2026-03-04T01:15:24.210Z"
  },
  {
    "sessionId": "295d2fe2-6276-49c4-9229-db8a61d33f2a",
Process Group PGID: 75447

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

▸ Shell {"command":"ls -d ~/.gemini/s*","description":"Listing directories in ~/.gemi...

Input

{
  "command": "ls -d ~/.gemini/s*",
  "description": "Listing directories in ~/.gemini that start with 's'."
}

Output

Output: /Users/jonmarkgo/.gemini/settings.json          /Users/jonmarkgo/.gemini/settings.json.orig     /Users/jonmarkgo/.gemini/state.json
Process Group PGID: 75492

Agent

Examining Possible Locations

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

Agent

▸ Shell {"command":"ls -d ~/.gemini*","description":"Listing all directories and file...

Input

{
  "command": "ls -d ~/.gemini*",
  "description": "Listing all directories and files that start with .gemini in the home folder."
}

Output

Output: /Users/jonmarkgo/.gemini
Process Group PGID: 75500

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

▸ Shell {"description":"Searching recursively for .json and .jsonl files in the ~/.ge...

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

▸ Shell {"description":"Uploading the session transcript to DEV.to.","command":"set -...

Input

{"description":"Uploading the session transcript to DEV.to.","command":"set -e\nTRANSCRIPT=$(ls -t ~/.gemini/tmp/gemini-guinea-pig/chats/session-2026-03-04*.json 2>/dev/null | head -1)\nTITLE=\"Wheeky...

Output

Output: Uploaded successfully!
URL: https://dev.to/agent_sessions/wheeky-menu-piggie-food-picker-popwfq
Exit Code: 1
Process Group PGID: 76267

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!

Upgraded embed experience and new embed types in DEV posts

Jon Gottfried — Fri, 27 Feb 2026 14:29:22 +0000

When you paste a URL into your DEV post, if it is embeddable, you now get a handy little tooltip to generate your liquid tag for you using a new universal embed tag:

Also - You can now embed new types of projects directly in your DEV posts. We now support Lovable, Bolt.new, Warp blocks, HuggingFace Spaces, and the HuggingFace Dataset Viewer. These are in addition to our widely used Cloud Run embed feature that launched recently!

Here's a few example projects to show you how it works:
Lovable:
{% embed https://iconstack.lovable.app/ %}

HuggingFace Spaces:
{% embed https://huggingface.co/spaces/KittenML/KittenTTS-Demo %}

HuggingFace Datasets:
{% embed https://huggingface.co/datasets/openfoodfacts/product-database %}

Warp Block Sharing:
{% embed https://app.warp.dev/block/JjdoVfeKebVSw8wiykuDag %}

Bolt.new:
{% embed https://ai-dashboard-with-da-z516.bolt.host/ %}

We hope you enjoy - and if you have any ideas or feature requests for more embeds feel free to post them in the comments.

The Future of Software Has a Lot More Builders. They’re Going to Need a Home.

Jon Gottfried — Wed, 18 Feb 2026 14:00:30 +0000

I have some big news to share today: Major League Hacking has acquired DEV (dev.to), the developer community platform where millions of developers share technical knowledge, learn from each other, and grow together.

This is one of the biggest moves in MLH's 12-year history, and it's been a long time coming.

When @ben, @jess, and @peter started DEV almost a decade ago, they wanted to build something the internet didn't have enough of: a developer community built on generosity instead of gatekeeping. A place where people didn’t just ask questions, but actually helped each other. Over the years, DEV grew into a community of more than 3 million developers learning in public, sharing expert advice, and supporting one another in their journeys. It's become one of the most trusted spaces in tech, and anyone who's spent time on the platform knows why. The culture Ben, Jess, and Peter built is special.

At MLH, we've been building something complementary. Our developer programs (like the Hackathon League, the MLH Fellowship, and much more) are where developers learn by doing: picking up a tool, creating something real with it, breaking it, trying again. Between our in-person events and programs, MLH has served more than 1.5 million developers across nearly 100 countries.

If DEV is the library, MLH is the lab. One is where knowledge gets shared, organized, and preserved. The other is where you get your hands dirty and prove you can actually build. Together, MLH and DEV will reach approximately 5 million developers worldwide. These two community-first platforms have been orbiting each other for years, and we're thrilled to finally bring them together.

Why Now Is The Right Time To Combine MLH & DEV’s Powers

If you've spent years honing your craft as a developer, the value of your skills has grown exponentially over the last year. The judgment, taste, and architectural thinking you've built over a career are exactly the skills that matter most when AI can handle the boilerplate. The ceiling on what you can build has never been higher.

At the same time, the floor is rising. People who never would have written a line of code (or called themself a developer) are building real software with AI. More software creators, building more things, tackling more problems. The craft of software development isn't shrinking. It's expanding. The number of people who can build software is about to grow by an order of magnitude.

But when everyone can build, the skills that matter change. AI generates the bricks, but you still have to build the house. Taste, judgment, knowing what to build, which tools to trust, how to evaluate whether the output is actually good. Those skills don't come from a tutorial. They develop by building real things alongside other people.

And traditional institutions can't keep up. By the time a curriculum gets approved, the technology is already six months out of date. The old developer infrastructure was built for a world where people needed answers to technical questions. AI commoditized that. But the need for a developer community didn't disappear. It shifted. People don't need a database of answers anymore. They need somewhere to develop judgment and learn and build alongside others in a trusted space.

Together, MLH and DEV are building the core community infrastructure of the next era of technology.

What's Changing (And What's Not) For Both Communities

DEV will continue to be the community its members know and trust.
The culture that Ben, Jess, and Peter built is exactly why we wanted to do this, and we're committed to protecting it. We're here to invest in DEV and help it grow, not to change what makes it special.

Forem, the open source software that powers DEV, will also continue to evolve. This acquisition actually helps clarify the relationship between the organization and the software. We're working toward a structure that supports Forem's independence so it can serve the broader open source community on its own terms. More on that soon.

What IS changing is that MLH and DEV can now do things together that neither could do alone. The lab and the library, connected. You experiment with a new platform or tool at an MLH hackathon. You write about what you learned on DEV. That knowledge becomes searchable, permanent, useful to the next person.

Whether you're shipping your first project or you're a senior engineer picking up AI skills for the first time, you're welcome here. In the AI era, everyone is a beginner again at some point. MLH and DEV, together, are the place where that's not just okay, but encouraged.

Looking Forward To A Future of Software Creators

The world is about to have a lot more builders. They're going to need a place to learn, to experiment, to develop taste and judgment, and to find their aspirational figures and their collaborators. That's what MLH and DEV are building together.

Thank you and congratulations to Ben, Jess, Peter, and everyone who built DEV into the community it is today. And thank you to our MLH community for continuing to show up, build things, and support each other. You're the reason we get to do this work.

Happy Hacking,
Jon, Swift, and the entire MLH+DEV team

P.S. If you want to learn more about the acquisition or the future of MLH and DEV, my co-founder and our CEO Swift will be hosting an Ask Me Anything (AMA) with me (Jon) and the DEV founders (Peter, Ben, and Jess) on MLH’s Twitch channel on February 19 at 11:30am ET. We'll be answering questions from the community live. We hope to see you there!