Choose a workspace
Start from a saved local workspace preset so Dexly knows where your Codex task should run.
Dexly
Turn live browser context into local Codex tasks.
Dexly gives your local coding workflow the page context it needs: inspect the DOM, attach screenshots, refine the task, and stream the result back into a compact Chrome side panel.
Chrome side panelLocal Codex connectionHosted billing only
Workflow
How Dexly fits into the browser-to-code loop.
Dexly stays focused on moving the right browser context into the right local workspace instead of becoming a browser IDE.
Capture live browser context
Inspect the page, select DOM targets, or attach full-page, section, and selected-element captures.
Refine before sending
Adjust the selected targets, review the prompt enhancement preview, and keep only the context that matters.
Run through local Codex
Dexly opens or resumes a local Codex thread, then streams progress, approvals, and output in the side panel.
Features
Focused product surfaces for browser-assisted coding.
The shipped product is opinionated: tight browser context capture, one local Codex workflow, and a narrow hosted boundary.
Precise DOM inspect and selection
Use click inspect, drag-region selection, parent/child refinement, and multi-select without leaving the side panel.
Page and element captures
Attach full-page screenshots, dragged section captures, or one cropped image per selected element when visual context matters.
Prompt enhancement before send
Preview the exact effective prompt Dexly will send, including inferred intent and the ranked context it decided to include.
Live approvals and streamed output
Follow status, command output, file changes, and approval requests in a single conversation surface while the task runs.
Saved workspaces and thread continuity
Keep one active thread per workspace, reopen recent turns, and start a fresh thread only when you actually need it.
Hosted boundary kept narrow
Dexly’s hosted backend handles sign-in, entitlements, billing, and usage accounting while the browser-to-code workflow stays local.
Trust Boundary
Keep the coding workflow local. Keep the hosted layer narrow.
Prompts, screenshots, active page URLs and titles, selected browser page content, inspect and capture interaction data, local workspace files and paths, and Codex thread history do not live in Dexly's hosted billing backend.
What stays local
- Prompts and effective prompts
- Browser page context and selected DOM snippets
- Screenshots and selected-element images
- Local workspace files and absolute paths
- Codex thread history, transcript content, and reasoning
What the hosted backend handles
- Google sign-in and extension session exchange
- Plan entitlements and monthly usage accounting
- Stripe checkout, billing portal, and webhook processing
- Account state needed for billing and access control
- Support, privacy, and policy surfaces on one origin
FAQ
Questions people ask before they trust a browser extension with workflow context.
Dexly is designed so the answer is usually simple: local when it matters, hosted only where billing and identity require it.
What is Dexly?
Dexly is a Chrome side-panel extension that turns live browser context into local Codex tasks for a saved workspace.
Does Dexly send my prompts or screenshots to its hosted backend?
No. Dexly’s hosted backend is intentionally limited to sign-in, billing, entitlements, and usage accounting. Prompts, screenshots, DOM context, and local workspace data stay out of that hosted backend.
How does Dexly work with Codex?
Dexly connects directly to a local Codex app-server over WebSocket, starts or resumes a thread for the selected workspace, and streams the conversation back into the extension.
What can I capture from the browser?
Dexly supports DOM target selection, full-page screenshots, dragged section captures, and selected-element image attachments, depending on what context the task needs.