Tools Reference

FreeRide gives your AI agent 13 tools, organized by workflow stage. You don't call these directly — your agent uses them based on your conversation. This reference helps you understand what's available and when each tool is used.

Session

Tools that manage the conversation lifecycle.

Tool	What it does
start_session	Opens a session and returns your project's current state — features, recent progress, open ideas, documentation index. Called automatically at the start of every conversation.
end_session	Closes the session with a rich narrative summary on top of the structured completion log. Triggered by saying "end session." If you don't, FreeRide auto-closes idle sessions with a less-rich rollup.

Working on Features

Tools for the core work cycle: get context, do the work, log what happened.

Tool	What it does
begin_work	Loads context for a specific feature before implementation — open ideas, prior decisions, existing docs, file manifest. Use for substantial work.
complete_work	Logs meaningful progress and tags it to one or more features. The primary record of work done. Returns doc snapshots so the agent can check if documentation needs updating.
complete_feature	Marks a feature as done for the first time. Verifies an implementation doc exists, transitions the feature status, and logs a completion.

The typical cycle: begin_work → do the work → complete_work. For small changes, complete_work alone is enough — the full cycle is for substantial implementation.

Creating & Capturing

Tools for adding new items to your project knowledge.

Tool	What it does
create	Creates a new feature or backlog idea. Features give your project structure. Ideas capture thoughts — attached to a feature or project-level. "Let's track this as a feature" or "Add this to the backlog"
capture	Records a decision or learning. Decisions capture a choice and the reasoning behind it — architecture, scope, direction, anything worth remembering (alternatives optional). Learnings preserve insights worth keeping. "Let's go with Postgres because..." or "TIL WebSockets don't work behind..."

Knowledge & Documents

Tools for maintaining your project's documentation.

Tool	What it does
save_document	Creates or updates a knowledge document. Seven types: overview, implementation, architecture, guide, backlog, UX flow, vision. Multiple docs per feature supported.
patch_document	Applies targeted edits to an existing document — small changes without resending the full content. Like a surgical edit instead of a full rewrite.
search	Queries across your entire project — features, documents, ideas, completions, decisions, learnings, files. Full-text search with filters by feature, date, status, priority, and more.

Updating & Logging

Tools for modifying existing items and logging mid-work updates.

Tool	What it does
update	Updates metadata on features or backlog ideas — status, priority, description, title. Also handles feature status transitions (backlog → in progress → done).
log_progress	Logs a mid-work update, blocker, or insight without marking a full completion. For when you want to note something without closing a work cycle.
confirm_docs	Records the agent's documentation decision after reviewing doc snapshots from complete_work. Part of the doc freshness flow — ensures documentation is actively considered after every significant piece of work.

How You Interact With These

Most of the time, you don't. The agent calls these tools on its own — opening a session at the start, logging completions after meaningful work, capturing decisions as they come up in conversation. That's the point: structured project knowledge as a byproduct of the work, not a chore on top of it.

When you do want to nudge it, plain language is enough — the agent maps loose phrasing to the right tool:

• "Track Authentication as a feature" → create
• "That's a decision worth keeping" → capture
• "What did we figure out about the database last week?" → search
• "The implementation doc needs a refresh" → save_document or patch_document
• "We knocked that one off already" → update
• "Wrap up what we just built" → complete_work
• "What should I work on next?" → start_session context + search

You don't have to think in tool names.

Related

• How It Works → — the session flow these tools sit inside
• Dashboard Guide → — where the data these tools capture surfaces
• Customization → — tune when and how often tools fire