How it works

What happens when you use Verdical

You work with your agents as usual. Verdical keeps the picture.

01

You connect once

Hosted. Nothing to install or run.

  • Sign in. There are no keys to copy.
  • In the private beta, we link your repositories with you.

After your invite, in your terminal

claude mcp add --transport http verdical https://mcp.verdical.dev/mcp

In Claude: add it as a connector.

02

You talk to your agent as you like

Rough notes are fine.

  • Your agent files issues, decisions and documents in the right product.
  • Every later session can find them.
Example

“Free plan: let’s cap it at 3 projects, most trial users stay under that. Do annual billing after checkout ships.”

  • DecisionFree plan limit: 3 projects
  • IssueAnnual billing, after checkout

03

Every session starts informed

No re-explaining, no rereading the whole repository.

  • The state, the next step and what waits on you.
  • The instructions for its role.
  • Which issues other sessions are working on.
Example
agent · start of session
state3 in progress · 1 in review
next stepmerge PR #212 once CI is green
waits on youthe free plan limit
othersa session is on the pricing page
roledeveloper on Ledgerly

04

Work keeps its own status

Status moves with your merged work.

  • An agent can’t call something done on its word alone.
  • Done needs merged work or a written reason.
  1. In progress An agent starts on it
  2. In review The work is up for review
  3. Done The work is merged

05

What you wrote stays true

Decisions keep their reasons and every version.

  • When code changes, the documents that describe it are flagged.
  • An agent confirms, updates or replaces them.
Example

Card errors show under their field · decision, version 3

  1. MergedCheckout moves its error messages.
  2. FlaggedThe decision that describes checkout needs review.
  3. ConfirmedThe agent checks it: the rules still hold.

06

You answer only what needs you

One screen across all your products, at app.verdical.dev.

  • Your answer becomes the agent’s next step.
  • Jobs run while you’re away (with Claude Code today).
  • Job changes wait for your yes.

07

Your data

Stored in the EU

Stockholm, Sweden.

Your code stays yours

Reads repository activity, never your file contents.

Search

Search by meaning sends text to OpenAI’s embedding service.

Take it with you

Export any product as Markdown, or in full with its history.

08

Today, and next

Today

  • Claude Code and Claude.
  • GitHub.

Next

  • Codex, Cursor and Gemini CLI.
  • GitLab.

Join the waitlist Private beta, free. Stored in the EU.

Technical details (beta)

The connection

  • A remote MCP server over HTTP, with OAuth sign-in. Errors name the fix.
  • Tested with Claude Code and Claude. Other MCP clients with remote OAuth should work.

Sessions

  • verdical_start opens a session and returns the handover: the latest work log, open issues, live sessions, what waits on you and the role.
  • Agents log with verdical_work_log: what was done and the one next step. With no session open, a work log is refused, with the fix.

Status from GitHub

  • A pushed branch or a pull request that names the issue moves it forward. A merged pull request that says “Closes” and names it finishes it; “Part of” leaves it open.
  • Work without a pull request is closed by hand, with a reason.
  • Verdical receives GitHub’s signed webhook events for pushes, pull requests and checks: branch names, commit IDs and first lines, pull request numbers, titles and issue references, changed file paths, and check results.
  • It can use a read-only token to compare a merged pull request’s file paths. It never reads or stores your file contents.

Documents

  • Each document names the code paths it describes. A merge that changes them flags it, unless the pull request already reviewed it.
  • Verdical runs no model to write documents. Agents write them.