Desktop app · local-first

The agent workbench
for your codebase

Plan with one model, delegate to the right agent, run repeatable workflows, and keep every diff, approval, question, and deliverable in one desktop workspace.

Download Shrevix Explore the docs

Use signed-in Codex Local or connect your models · keep work in one desktop workspace

Repository-aware workspace search× Chat conversation× workspace-search-plan.md×

Alexnow · plan

Create a plan to make workspace search return matching repositories too. Keep it local and keyboard-first. Do not implement anything yet.

✦ Shrevixthinking

I’ll inspect the current palette, reuse the existing repository snapshot, and make the reviewable plan explicit about ranking, keyboard behaviour, and tests.

Tasks1 / 4

Creating a reviewable implementation plan before making changes.

✓ Trace command-palette search sources

Draft repository-aware result design

Add keyboard coverage

Implement after approval

▤

workspace-search-plan.mdDocument · v1 · just now · view in Artifacts

›

✦ Shrevixplan ready

Plan ready for review

Keep navigation results first and add repository hits below.
Reuse in-memory snapshots, so each query stays local and instant.
Preserve arrow-key selection and add focused tests.

Alexreview comment

I left a comment on the plan’s result-ranking step. Please resolve it, update the plan, and let me review the revision before implementation.

read fileworkspace-search-plan.md

write fileworkspace-search-plan.md

workspace-search-plan.md+8−1

42 Keep navigation results in their current group.+43 Debounce repository matching and retain branch metadata.

▤

workspace-search-plan.mdDocument · v2 · revised from your comment

›

✦ Shrevixupdated plan

Updated. Repository results now follow the existing debounce, include the default branch, and have keyboard coverage in the plan. Ready for implementation when you are.

Alexnow

Plan looks good. Implement it, show me the diff for approval, generate a short implementation note, and run the targeted tests.

⌘Delegated→frontend-devcommand palette implementation working

read filedesktop/src/layout/shell/command-palette.tsx

search codeworkspaceSnapshot · repositorySnapshot · debounce

3 matching sources in the command palette and workspace snapshot helpers.show more

write filedesktop/src/layout/shell/command-palette.tsx

command-palette.tsx+22−2

61 const commands = navigationResults(query);+62 const repositories = repositoryResults(query, snapshots);

Approval· write filewaiting for you

Approve this operation

Review the exact operation before allowing Shrevix to continue.

command-palette.tsx+22−2

61 const commands = navigationResults(query);+62 const workspaces = debouncedWorkspaceSearch(query);+63 const repositories = repositoryResults(query, snapshots);+64 return [...commands, ...workspaces, ...repositories];

Reason for denial (optional)

write filedesktop/src/test/command-palette.test.tsx

run testsnpm test -- command-palette

12 passed · repository grouping, debounce, and keyboard selection verified.

▤

workspace-search-implementation.mdDocument · created from this conversation · view in Artifacts

›

✦ Shrevixcomplete

Implemented the approved workspace search flow. Repository matches now respect the existing debounce, show the default branch, support keyboard selection, and pass all targeted tests. I also added the implementation note to Artifacts.

24.2s · Codex Local · GPT-5.6 Sol · 2 files changed · 12 tests passed

Repository-aware workspace search

PLANworkspace-search-plan·shrevix·v1

Outcome

Let people discover matching repositories from the workspace search flow without changing the command palette’s keyboard-first behaviour.

Implementation plan

Keep navigation and session results in their existing groups.
Reuse the in-memory repository snapshot to add repository matches below workspace results.
Use the existing debounce, show each repository’s default branch, and preserve arrow-key selection.
Add focused tests for grouping, branch metadata, and keyboard navigation.

Verification

Run the command-palette test slice and confirm no new source is queried while the user types.

Subscription, built-in, and compatible providers Claude through OpenRouter · custom OpenAI-compatible endpoints

Codex Local DeepSeek GLM Kimi NVIDIA OpenRouter OpenCode Zen Ollama LM Studio

01 Product surface

More than a chat window.

Shrevix now covers the whole loop: start a task, route it, inspect the work, answer interruptions, review changes, and keep the useful output.

Live conversations

Thinking, tool calls, questions, approvals, context, token usage, and the final response update in one transcript. Long sessions load the latest work first and fetch history as you need it.

Sessions · Needs you

Agents that delegate clearly

Choose an agent explicitly or let a lead route the task. Independent work runs in parallel, and each delegated run opens as its own conversation without leaking child tool noise into the parent.

List · Org structure

Repeatable workflows

Compose LLM, agent, code, and tool nodes with inputs, triggers, definition-of-done checks, and human gates.

Runs · Comparison

Context that compounds

Import reusable skills, search local knowledge semantically, and attach files, documents, sessions, or agents to a turn.

Skills · Knowledge

A real coding workbench

Browser-style tabs keep conversations, editable files, terminals, diffs, and documents together. Quick Open, content search, source/preview, and file operations stay inside the attached worktree.

⌘P · ⌘⇧F · Terminals

Deliverables with provenance

Store documents, images, PDFs, audio, video, tables, and presentations locally. Organise them in folders, edit Markdown inline, version each change, and jump back to the session that created them.

Documents · Artifacts

02 How it works

From install to reviewed work in three steps.

STEP 01

Install the desktop app

Install the desktop build from your Shrevix access channel, sign in, then choose a connected provider or a discovered local model.

STEP 02

Connect your codebase

Open a local repository or connect one, then create an isolated workspace when a task needs its own branch, ports, and services.

STEP 03

Ask, route, and review

Start from the dashboard or an agent. Follow delegated conversations, answer the Needs you queue, inspect the diff, and keep the resulting artifacts.

03 Connections

Connect the sources your team already uses.

Bring the developer tools, product systems, and data sources that matter to a task into the same workspace. Choose the tools each connection can expose, then use them from conversations, agents, and workflows.

OAuth connections for services such as GitHub, GitLab, Linear, Slack, Notion, Figma, and more
MCP connections for local tools, browser automation, databases, and compatible servers
Selective access keeps only the enabled capabilities available to Shrevix

Explore connections and permissions →

Connections OAuth · MCP

GitHub repositories and pull requests Dev

GitLab merge requests and pipelines Dev

Linear issues, projects, and cycles Dev

Sentry errors, traces, and releases Dev

Slack channels, messages, and users Product

Notion workspace documentation Product

Figma files and design context Product

Google Workspace Drive, Gmail, and Calendar Product

Supabase projects and databases Data

Stripe customers, payments, and events Product

Vercel deployments and build logs Dev

Custom MCP local and compatible servers MCP

04 Agents

Delegation you can actually follow.

Browse agents as a clean team list or switch to organisation structure. Leads can inspect the roster and delegate to a suitable specialist; explicit agent requests become routing requirements.

Each delegated run opens as its own conversation
The parent shows one clear delegation event, not every child tool call
Live state, permissions, model, charter, and recent work stay visible

Read about agents and delegation →

Delegated fullstack-dev complete

Implement the repository safeguards and run the focused checks.

Child conversation · 8 messages Open conversation ↗

05 Workbench

Every surface shares the same workspace.

Chrome-style tabs grow and shrink together across conversations, files, code, terminals, diffs, and Documents. The active repository or workspace is always explicit.

Open, edit, rename, copy, move, or delete files from File explorer
Use Quick Open, workspace search, find/replace, and Markdown source or preview without leaving the tab
Keep named terminal sessions below the file surface they belong to
Writes render as code diffs at the approval point
Context and token telemetry update while a turn is running

Explore the chat workbench →

Shrevix workbench with equal-width browser tabs and a code diff

06 Workflows

Repeat the process, not the prompt.

Durable workflows combine agents, models, code, and external tools with visible inputs, triggers, singleton policies, and human checkpoints.

Build or edit workflows in the visual builder
Resume paused runs from the dashboard's Needs you queue
Compare runs and inspect generated documents without losing context
Local triggers run while the desktop app is open; one missed schedule is recovered after wake

Read the workflow guide →

Shrevix workflow library with active and draft workflows

07 Documents

Every deliverable, in context.

Documents is a unified local artifact library: authored Markdown, images, diagrams, PDFs, audio, video, presentations, spreadsheets, and tables.

Search, filter, create folders, drag artifacts into them, import, and export
Edit Markdown inline with source and preview, then save a named version
Preview supported text, media, PDF, and spreadsheet formats inline
Open presentations and other formats in an installed desktop app
Open the source session that produced an artifact

See documents and artifacts →

Shrevix Documents with folders, artifact types, provenance, and version state

08 Knowledge

Local retrieval with visible sources.

Ingest policies, runbooks, specs, and repository docs. Shrevix computes embeddings locally, ranks semantic matches, and sends only the selected context to the active model.

Global and repository-scoped documents
Semantic search across chunks and sources
Search results identify their source document and passage
The agent is instructed to cite those sources in its answer

Set up knowledge →

Chat · knowledge scope: global

What's our refund SLA?

Refunds are processed within 5 business days of approval. Requests past 30 days route to manual review. refunds.md §2 policy/sla.md

top matches returned · source passages remain inspectable

09 Control

Approval stays at the point of action.

In Approval mode, mutating tools pause exactly where they were requested. A write shows its diff once, resolved approvals collapse cleanly, and failures or denials remain visible.

Plan mode blocks local file writes and shell commands
Approval mode gates writes, commands, and MCP calls by default
Bypass mode is an explicit, visible choice
MCP policies can explicitly allowlist selected tools

write filecore/auth.py waiting for approval

def refresh(self, token: Token) -> Token:

- return self._client.refresh(token)

+ if token.expires_in() < self.margin:

+ return self._client.refresh(token)

return token

Approve Deny the run resumes from this point

10 Built on open standards

MCP · standard mcpServers config LSP · jedi, tsserver, rust-analyzer, gopls OAuth · PKCE where supported · protected local storage LiteLLM · remote routing + compatible endpoints Tauri · native desktop shell

11 Desktop access

Bring the workbench to your desktop.

Install the app, sign in, connect your model and codebase, and start from the same dashboard you saw above.

Download Shrevix Explore documentation