Make CoPilot an Interactive Programmer

Created By
BetterThanTomorrowa year ago
VS Code AI Agent Interactive Programming. Tools for CoPIlot and other assistants. Can also be used asan MCP server.
Overview

What is Calva Backseat Driver?

Calva Backseat Driver is a VS Code extension that transforms AI coding assistants into interactive programming partners by providing them access to the Clojure REPL, allowing for real-time code evaluation and feedback.

How to use Calva Backseat Driver?

To use Calva Backseat Driver, install it from the VS Code Extensions pane, connect it to your Clojure project, and optionally enable REPL evaluation powers in the settings.

Key features of Calva Backseat Driver?

  • Evaluate Clojure code in real-time using the REPL.
  • Symbol info lookup for documentation and argument information.
  • Integration with clojuredocs.org for additional resources.
  • Optional MCP server for AI assistants to interact with the REPL.

Use cases of Calva Backseat Driver?

  1. Enhancing AI coding assistants to provide accurate code suggestions based on real-time execution.
  2. Debugging Clojure applications with AI assistance.
  3. Learning and exploring Clojure through interactive programming with AI support.

FAQ from Calva Backseat Driver?

  • Can I use Calva Backseat Driver with any AI assistant?

Yes, it can be used with any MCP compliant AI coding assistant.

  • Is it safe to enable code evaluation?

By default, code evaluation is disabled for safety, and you can opt-in to enable it in the settings.

  • What are the prerequisites for using Calva Backseat Driver?

You need VS Code, Calva, and GitHub CoPilot installed to use this extension.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BetterThanTomorrow
Star
8
Language
Clojure
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago