Site Navigation

ThinkForge home

Our mission and story

Frequently asked questions

Get help

How we protect your data

Usage terms

Latest news and updates

Get early access

Welcome to ThinkForge

What's next

AI chat assistant for your browser

Frequently asked questions about ThinkForge Chat

Get started in minutes

Explore every ThinkForge feature

Your desktop command center

Create tools and agents from prompts

Find and reuse project context

Your in-app and floating project workspace

Capture web pages, chats, and research

Connect the tools you already use

Recover and act on working context

Your project control center

Map ideas and relationships visually

An agent that builds other agents

Coordinate multi-step agent workflows

ThinkForge inside your editor

Create better content faster

Ship with fewer rewrites

Discovery to roadmap

From source to draft

Learn smarter

Choose your plan

Get the desktop app

Welcome to ThinkForge. This is the user documentation for the current beta.

ThinkForge is a Windows desktop environment for project-based knowledge work. It keeps documents, search, reusable context, agents, automations, and capture tools connected to the same local project instead of scattering them across unrelated apps and browser tabs.

Status: Closed beta behavior for 0.9.0-beta.4

A reference for the names ThinkForge uses for its systems and surfaces.

This document covers installing the ThinkForge desktop application, where it puts things on disk, how to update it, and what uninstalling does and does not remove. For what to do after the app is running, see Getting Started. For installing the browser extension, see Chrome Extension / Installation.

This guide covers the first beta launch, creating a project, and verifying the main desktop, Chrome, AI, and MCP features.

ThinkForge documents support links as part of the document content. Links are stored in ordinary Markdown, remain visible in the source file, and work in both the rich-text editor and Project Navigator's focused document reader.

The folder tree is the primary navigation surface in ThinkForge. It appears as a sidebar panel showing project content organized into collapsible sections — physical files and folders, workspaces, pinned items, shortcuts, recents, tags, tools, automations, Smart Clipboard, and trash.

The Global Dashboard implementation is retained as a cross-project widget canvas, but its main-window tab is disabled for the current MVP.

ThinkForge separates application shortcuts from Windows-global hotkeys. Application shortcuts work while ThinkForge is active, including while the rich-text or code editor owns focus. Windows-global hotkeys work from other applications.

A ThinkForge project is a folder on disk initialized with a hidden .fire/ directory. Your content remains ordinary files arranged in whatever folder structure you choose.

Settings is a full-window page in the main application, opened from the command bar. A navigation sidebar on the left selects which section appears on the right.

ThinkForge uses tags to organize and find documents across a project. Tags are stored alongside the document's indexed content, not in sidecar files on disk. Every indexed document can have tags added, removed, and searched.

ThinkForge's task system is a per-project tracker with list, kanban, timeline, and table views. The same task data is available in a main-window Tasks tab and in the standalone Task Board window opened from Power Strip.

Use document links to move directly between related project documents or between headings in one document. Links are saved as ordinary document content, so they remain visible in Markdown and are not limited to Project Navigator's relationship views.

The project-scoped Automations tab is the beta editor for sequential multi-tool workflows. It hosts the canvas, an automation selector, canvas commands, a collapsible Project Navigator column, and the document and tool info panel.

An automation library artifact or surface deployment is a version 1 JSON file in the project.

Automations connect existing Agent Tools into a repeatable sequence on a dedicated project-scoped authoring page.

Connections determine a run order, then every tool runs in sequence. Connections do not activate routes.

An automation canvas is the editable workflow. Deploying it publishes a runnable project version. Placing that automation on the Tools page or Power Strip creates an independent deployment.

The beta has two sequential execution paths: one for the editable canvas and one for deployed scripts. Both run each tool the same way, but they do not share a scheduler.

The Think Forge Extension is an optional Chrome extension that connects supported AI-chat pages and browser content to the ThinkForge desktop app. Its active beta features include conversation navigation, bookmarks, cross-platform branching, desktop launchers, project-document insertion, and browser-to-project capture.

The beta extension is installed as an unpacked Chrome extension. There is no Chrome Web Store installation step for this beta release.

The Think Forge Extension version 2.0.0 supports eight AI-chat platforms. Site support depends on page structure, so a site redesign can affect extraction until support is updated.

The Quick Command Menu is a separate in-page Chrome extension feature, not the desktop Power Strip.

The Think Forge side panel is the extension's main browser interface. It runs beside the active page and has four tabs: Navigator, Organize, Tools, and Settings.

Web Capture moves browser content into the active ThinkForge desktop project. The extension extracts the page or selection, sends the result to the desktop, and ThinkForge saves and indexes the resulting project file.

ThinkForge opens each editable file in the editor suited to its format. Documents and Markdown use the document editor; source code, configuration, and plain-text files use the code editor.

Floating Navigator is a detached, always-available window that wraps the same folder tree used inside Project Navigator. It floats on top of other applications so you can browse your project, search documents, access the smart clipboard, and open files without switching away from whatever you're working in.

ThinkForge can open focused help for the control you are currently using. The help window searches the bundled User Docs project, so its results describe the same released behavior as this guide.

The ThinkForge MCP server exposes project knowledge and bounded ThinkForge operations to external AI tools through the Model Context Protocol. It runs locally inside the desktop app on port 3001 and gives compatible clients access to indexed documents, conversations, tags, project instructions, safe document writes, and the active Mind Map's context, semantic node discovery, and revision-checked patch boundary.

This document describes every tool the ThinkForge MCP server exposes to connected AI clients. Each tool is called through JSON-RPC 2.0 via tools/call with a tool name and arguments object. Results are returned as JSON inside the MCP content envelope.

Status: Current

The ThinkForge MCP server works with any tool that supports the Model Context Protocol. This document covers which clients are supported, how to configure them, and how to verify the connection.

Mind Map is a visual workspace for organizing a project, planning a system, or breaking a large idea into manageable parts. You can build a map with ThinkForge's Tool Agent, turn the current project's folder structure into a map, or start with one node and build it yourself.

ThinkForge Mobile is the Android companion to ThinkForge Desktop. Its primary role is to browse and work with the active Desktop project over the local network, while ThinkForge Desktop stays authoritative for project files, tasks, Tools, and writes.

Power Strip is ThinkForge's floating desktop command bar. It stays available above other applications and provides fast access to capture actions, project tools, sidecar panels, agents, automations, and Chrome-aware commands.

Power Strip can run deployed agents and automations directly from the desktop surface. It can also attach agent hooks to supported actions and display execution feedback near the command that started the work.

The AI Activity Power Strip sidecar shows recent successful document changes made through ThinkForge MCP for the active project. It is available in the Power Strip customization catalog but is not added to default or existing profiles automatically.

Browser Commands are Chrome-aware buttons on the desktop Power Strip. They are not a separate browser strip and not an in-page menu.

This document describes Power Strip's command catalog and how the surface behaves.

Power Strip customization opens with the + button at the end of the strip. The modal has three tabs: Commands, Settings, and Status.

Power Strip sidecars are compact panels that open beside the desktop strip. They provide focused access to project content and configured tools without opening the full ThinkForge window.

Overview is Project Navigator's project summary. It is designed for quick re-entry: open the project, scan what exists and what was recently active, then move to the folder, workspace, or document you need.

Cluster View, also called Forge Graph in parts of the interface, is a spatial map of indexed documents. Each document is a node on a force-directed canvas. The view helps you see related material without relying on folder paths alone. Hover or focus the Clusters view selector and press F1 to open a prepopulated search of these User Docs for the SK Memory and relationship features behind the map.

Files is the default file-browsing view in Project Navigator. It shows the current folder's immediate subfolders and supported files. A selection in the folder tree activates the pinned Files tab, so other working tabs keep their state.

Insights View summarizes the active project's explicit document-link graph. It helps you find highly connected documents, documents with no manual links, and the relationship intents used across the project.

Project Navigator is ThinkForge's main project workspace. It combines project navigation, document browsing, activity recovery, and relationship views in one desktop surface. Automation authoring is a separate project-scoped tab.

Workspaces are saved project contexts for a task or topic. They collect references to files, up to three goals, and attached ThinkForge tools so you can return to a stream of work without reconstructing it from memory.

Project templates give new projects a head start. Instead of creating an empty project and building structure from scratch, you select a template that provisions a set of documents, folders, and optionally agent deployments tailored to a specific type of work.

ThinkForge ships with 21 workspace templates organized into four categories. Each template creates a set of pre-configured documents tailored to a specific type of work.

SK Memory is the per-project search and indexing system in ThinkForge. It reads text-based files from the project folder, breaks them into searchable chunks, generates vector embeddings, and stores everything in a project-local database. This index powers document search, semantic similarity discovery, smart links, tag management, the Forge Graph visualization, and the MCP server's search tools.

SK Memory generates vector embeddings locally using a model bundled with ThinkForge. These embeddings power semantic search, smart link discovery, and the Forge Graph visualization.

SK Memory provides four search modes that can be used independently or combined. Each queries the project's index and returns results ranked by relevance.

Smart Clipboard is a persistent, global clipboard stack that runs independently of any project. It captures everything you copy to the Windows clipboard — text, files, folders, and images — and keeps it in a reusable list. Items stay until you remove them or the stack reaches its 25-item capacity, at which point the oldest item is dropped.

ThinkForge themes can be created through the Theme Editor in the desktop app, or by writing JSON files directly. This document covers both approaches and explains the structure of a theme file.

ThinkForge themes control every surface color, font, and spacing value in the application. Switching a theme updates the whole interface immediately — there is no save step and no restart.

Skills are the atomic operations that tools are built from. Each step in a tool invokes one skill. Skills range from deterministic text operations to AI processing, external API calls, public webpage retrieval, and trusted local Python scripts.

External service integrations require credentials — API keys or OAuth tokens — to authenticate. This document covers how credentials are stored, configured, and used by tools.

ThinkForge connects to 11 external services through the CallConnectedAPI skill. Connected services let tools read data from and push data to the platforms you use daily — project management, communication, CRM, scheduling, and financial tools.

Tools process the context supplied by the surface where they run. They do not automatically read the clipboard, active document, browser page, or every open project file.

This document covers the core skills available to user-created tools: AI processing, text manipulation, data operations, and local Python execution. These are the building blocks of most tool pipelines.

Create a reusable tool from the Tools page by describing the workflow in a conversation.

A tool stores a reusable workflow. A deployment places that tool on the Tools page, Power Strip, Ribbon, or a project folder.

The CallConnectedAPI skill connects tools to 11 external services. A single skill handles all services — the service and operation arguments determine which API endpoint gets called.

These skills handle file system operations and project-scoped actions. They allow tools to read secondary files, write output, list directories, and search for files.

Python Script Tools let an Agent Tool run an existing local .py file through the normal ThinkForge tool runtime.

ThinkForge Mobile is a local-network remote control for the desktop's active project and deployed tools. The desktop remains authoritative for project identity, documents, filesystem writes, SK Memory, credentials, and execution.

A saved tool runs its skills in order and returns the final step's output.

Detailed operation reference for each connected service. For each service, this lists the available operations, their target parameters (configured once), and content parameters (provided per execution).

A saved tool contains a reusable workflow. A deployment is the configured placement you run from the Tools page or another surface.

A tool reports progress as its steps run and shows the final result or error.

A tool contains a reusable workflow. A deployment places that tool somewhere you can configure and run it. Each deployment can have its own context, settings, AI model, and triggers.

This page separates shipped behavior from designs that are not implemented.

Triggers run a deployment automatically. Each deployment can have its own schedules and watched folders.

ThinkForge MCP does not currently expose user-created Agent Tools.

The Chrome extension does not provide a browser-native tool library or result viewer.

Agent Tools are reusable workflows built from ThinkForge skills. You describe a task in natural language, review the proposed steps, and approve the tool before it is saved.

Voice to Text turns an explicit microphone recording into editable text with a local Whisper model. Desktop recordings are captured and transcribed on your Windows computer. The Android companion can send a recording directly to the paired desktop, where transcription still runs locally. No online transcription service is used.

Chrome extension documentation

First steps

Core documentation

Organize your chats

Tag your content

Navigate efficiently

Custom AI personas

Find tags fast

Power user shortcuts

Security guide

Fix common issues

All resources

Latest articles

Common product questions

Request new features

Plan, script, record, edit, and publish videos

Episodes, guests, show notes, and publishing

Plan, draft, and publish newsletters

Shorts, Reels, TikTok content pipeline

Turn one piece into many

Modules, lessons, scripts, and feedback

Offers, clients, content, and admin

Discovery, scope, pricing, and follow-ups

Welcome packets, contracts, and checklists

Messaging, assets, and launch tasks

Goals, channels, assets, and reviews

Leads, follow-ups, and deal stages

Sources, citations, drafts, and feedback

Competitive analysis and synthesis

Long-running multi-source investigation

Outline, draft, revise, and publish

Client sessions, notes, and follow-ups

Modular web app project structure

iOS and Android project management

Chrome, Firefox, and Edge extensions

Mechanics, assets, and playtesting