Jarela documentation¶

A local-first desktop workspace for building, running, and extending LangGraph agents.

Jarela is a local-first desktop chat UI for LangGraph agents. It runs as a single Next.js process on your machine, keeps state in SQLite, and exposes a structured tool ecosystem for agents, integrations, document indexing, and provider-backed workflows.

Version scope: This documentation snapshot targets Jarela 3.0.0 and covers repository changes through commit 50f0be5ce99917e2f580ad74716cc4169be14e71 (2026-10-27). Features listed under Unreleased are not part of 3.0.0. Workspace package documentation follows that package's version and identifies unreleased behavior separately. Update this baseline after each full documentation review.

Find your path¶

Release updates¶

Read the per-release changelog for user-visible changes and agent upgrade details for prompt/tool schema deltas. The project history chart shows automatically generated commit statistics and accumulated net text lines without an editorial storyline. Machines should use the JSON changeset feed, not scrape the HTML preview. The schema-versioned feed includes each release's predecessor, adoption hints, prompt deltas, and tool parameter changes. Automatic adoption uses bundled changesets for the installed version and asks the agent to prefer this feed for supplementary guidance when web_fetch is available and permitted. It excludes Unreleased/future entries and reports unavailable web access while continuing with local evidence.

Using Jarela¶

Start with installation and the first-run setup, then learn the runtime model and main extension points.

Install Jarela · Set up your first assistant · Operate Jarela · Understand the architecture

Developing Jarela¶

Set up the repository, run the checks, and use the architecture docs before changing a shared boundary.

Set up development · Explore extension surfaces

For planned future-work priorities and minor-upgrade tracking, read the post-3.0 product direction and ADR-0111. The direction is accepted for planning; implementation contracts and release gates remain pending. These plans do not change the released feature or permission contract.

Teaching the agent¶

The built-in documentation skill makes local documentation the first source of truth and uses the public site only as a fallback.

Read the architecture · Read the extension guide

Why Jarela exists¶

• Local-first: a single app on your own machine, no hosted backend required.
• Multi-provider: Anthropic, OpenAI, Google GenAI, Cohere, DeepSeek, and GitHub Copilot can all be configured.
• Agent-first: conversations are checkpointed, tool policies are per-agent, and scheduled/background flows are first-class.
• Extensible: providers, tools, MCP servers, harnesses, and integration manifests all have explicit extension surfaces.

Core documentation map¶

Documentation contract¶

The agent itself should not guess at the codebase. Instead, it should discover the relevant docs and extension surface before acting on repo-level changes.

Use the built-in documentation skill and the describe_extension_surfaces tool when the task touches:

• provider integration
• tool registration
• MCP server wiring
• harness behavior changes
• app branding or runtime configuration

The installed local docs are the preferred source because they are available offline and match the app version. The GitHub Pages site is a public mirror for browsing and a fallback when local docs cannot be read.

Architecture note¶

The codebase is intentionally organized into a few stable layers:

• app and API routes
• agent runtime and prompt assembly
• storage and persistence
• tool/provider/MCP registries
• integration and docs surfaces

This separation is what makes the app extendable without collapsing into one monolith.

Further reading¶

• README
• CONTRIBUTING.md
• CHANGELOG.md