Results for “local-directory”

Index local folders and search documents with BM25, vector, or hybrid queries, plus AI answers with citations and a web UI.

Index local folders and search documents with BM25, vector, or hybrid queries, plus AI answers with citations and a web UI.

Scans repositories for markdown and HTML documentation, classifies files as repo-local or centralizable content, generates an inventory report, and optionally consolidates content into a centralized docs repository.

Manage Google Drive files, folders, and shared drives via the Drive v3 API, including uploads, downloads, permissions, and metadata operations.

Use this when a project needs a better local development workflow for setup, running services, seeding data, testing integrations, or managing multi-service developer environments.

Indexes and searches local Markdown notes and docs with BM25 keyword search, vector semantic search, and local LLM reranking, all running offline without API keys.

Sends and reads email for your own domain through a local mail server using fixed scripts, and creates new mail accounts.

Searches a local-first memory index and returns the top matching entries with paths and headers.

Manages personal local Agent Skill files by detecting reusable material, searching for similar skills, and creating or updating SKILL.md folders after user approval.

Turns a local folder into a searchable, maintainable knowledge base for AI agents, handling setup, navigation, content ingestion, querying, and health checks without external databases or RAG systems.

Saves, retrieves, and organizes personal notes locally as Markdown files in ~/.synapse/notes/.

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.