Dicty.io
Knowledge Base & Workspaces

Project Context & GitHub

Ground voice notes in repository commits, pull requests, and generate architecture docs autonomously.

Dicty integrates with GitHub to ground spoken documentation directly in your team's code, commits, and active pull requests.

Workspace & Git Context Selection#

GitHub Project & Branch Context

In Settings (⌘ ,) → Projects:

  1. Target Repository: Choose from your list of accessible public and private GitHub repositories (e.g. vkazmin/dicty).
  2. Branch Selector: Target your active working branch (e.g. main or feature/audio-stream).
  3. Active Context Selection: Check the specific recent Git commits and open Pull Requests you want the AI Librarian to review.
  4. Autonomous Architecture Generator: Click Generate Architecture Document to let the agent analyze your workspace structure and synthesize an authoritative ARCHITECTURE.md baseline.

Setting Up GitHub Integration#

  1. Go to Settings (⌘ ,) → API Integrations.
  2. Enter your GitHub Personal Access Token (PAT) with repo read permissions.
  3. Click Save. Dicty securely stores your token in the macOS Keychain.

Active Context Selection (Commits & PRs)#

Before dictating architectural rationale, select the relevant code context:

Context SourceSelection ExampleRole in Documentation Synthesis
Recent Git Commits7126588 Merge PR #34 from vkazmin/14.08Informs the LLM of recent code modifications, diffs, and author rationale.
Open Pull Requests#33 Merge pull request from vkazmin/mainGrounds generated documentation in active feature PRs, branches, and discussion threads.

When you synthesize documentation in Librarian mode, Dicty passes the selected commit diffs, author metadata, and PR details to the LLM. The generated architecture documents link directly to the exact code and pull requests being referenced.

Autonomous Architecture Generator#

Dicty can analyze an entire repository to generate a comprehensive architecture document:

  1. Select your target repository in Settings → Projects.
  2. Click Generate Architecture Document.
  3. The Librarian agent traverses the codebase directory tree, analyzes manifest files (Package.swift, package.json, Cargo.toml, or requirements.txt), and drafts a system architecture document.
  4. Review the generated document in Pending Updates before publishing.