Agent loop, session management, tool execution, context compaction, hooks, and extensions.

Exposes Ask::Agent::Session behind the standard app-server JSON-RPC/stdio protocol. Drop-in compatible with clients that speak the ZCode/Codex app-server protocol — Telegram bots, AI SDK providers, IDE extensions, and headless automation.

DEPRECATED — maintenance mode only, superseded by the canonical ask-app-server + ask-session-protocol architecture and an internal successor. A self-hosted web coding agent for the ask-rb ecosystem. Runs Ask::Agent::Session against any workspace with a mobile-first PWA, streaming events over SSE, with approvals, plan mode, todos, and diffs. Comes with the `ach` utility CLI for headless runs and server management. Extensible to other coding agents (ACP, Codex, Claude Code) via ask-coding-providers.

Drive desktop apps in the background via Cua Driver — screenshots, clicks, typing, sandboxed VMs, and encrypted Computer History. Wraps Cua's MCP tools as Ask::Tool subclasses and ships a bundled computer.use_computer skill.

Harness for AI coding agents working in any Ruby project. Ships a language-agnostic tool contract (RunCommand, ReadLog, QueryDatabase, ReadModel, SchemaGraph, RunTests) with structured returns, read-only DB enforcement, environment permissions, and audit logging. The Rails edition (ask-rails-harness) adds framework-native tools on top.

Discovers, validates, and formats agent skills from project directories, user config, and installed gems. Ships built-in skills (codebase exploration, debugging methodology). Each skill is a markdown file with step-by-step instructions that the agent loads on demand.

Bash, Read, Write, Edit, Glob, Grep, and Code tools for the ask-rb ecosystem.

Fetches a URL and converts its content to clean markdown for LLM consumption. A pluggable backend chain: pure Ruby httpx + Nokogiri + reverse_markdown by default, a Jina Reader fallback for JS-rendered or blocked pages, and a real-Chrome fallback (Ferrum) that renders JavaScript and lets auto-solving Cloudflare challenges complete. The capability layer only — tool framing (MCP servers, agent tools) is provided by the consumers.

Web search returning results as clean numbered markdown. Two selectable backends: a local SearXNG instance (SEARXNG_URL, the default path for everyone) and TinyFish's hosted API (opt-in: SEARCH_BACKEND=tinyfish plus a TINYFISH_API_KEY or ask-auth credentials key). The capability layer (WebSearch.search); the native Ask::Tools::WebSearch agent tool is an optional integration that registers when ask-tools is present.