Knowledge Base

Talk it through.
Walk away with the documentation.

Record an expert explaining how something works. The transcript becomes skill files, guides, FAQs and references — ready to publish.

0
Total Sessions
0
Generated Articles
0
Skill Files
0
Step-by-Step Guides

Recent Sessions

No sessions yet. Start capturing knowledge!

Outputs
0 chars
Template None
Domain General
Model GLM-5.2 (Cloud)
Participants None

Session History

Title Domain AI Model Status Duration Articles Date Actions

No sessions found

No generated files yet

Documentation

Knowledge capture, written up for you

Record a working session and get back the documents you would otherwise have written afterwards from memory: a skill file, a step-by-step guide, an FAQ, a glossary, and a quick reference. Connect a ServiceNow instance first and the model checks what was said against the live system before it writes any of it down.

How it works

8 steps
  1. 1
    Name the session Give it a title and describe what will be covered. Both feed the prompt.
  2. 2
    Choose what you want back Output formats, a template, the domain, the AI model, and who is in the room.
  3. 3
    Connect ServiceNow Open Settings and connect the instance. Skip this and the documents are written from the transcript alone.
  4. 4
    Start the capture Transcription is live from the moment you click Start Knowledge Capture.
  5. 5
    Talk through the work Speak naturally. The speaker bar tracks who is talking.
  6. 6
    Mark what matters Bookmark moments, grab screenshots, clip video, and drop notes as you go.
  7. 7
    Stop recording The transcript, screenshots, and record context are saved together.
  8. 8
    Collect the documents Every format you ticked is written in parallel and lands in Generated Files.

Getting a good transcript

  • Speak clearly and stay near the microphone.
  • Use the speaker bar so the transcript attributes people correctly.
  • Bookmark concepts as they come up, not afterwards.
  • Connect ServiceNow before you record, so the model can check what was said.

Reference

6 topics

Output formats

Five documents, written in parallel

Every format you tick is generated from the same transcript at the same time. All five are on by default.

  • Skill file — a Claude Skill in markdown with frontmatter, key concepts, steps, best practices, and pitfalls
  • Step-by-step guide — prerequisites, numbered steps, tips, and a troubleshooting table
  • FAQ — the questions the session answered, paired with their answers
  • Glossary — terms and acronyms defined the way they were used
  • Quick reference — a card built for scanning, not reading

AI models

Your pick first, then a fallback chain

The model you choose in the composer is tried first. If it fails, the chain falls through the rest, so one provider outage does not cost you the session.

glm-5.2:cloudDefault
deepseek-v4-pro:0813Text only
claude-fable-5-1Reads images
claude-opus-5Reads images
claude-sonnet-5Reads images
gpt-5.6-solReads images
gemini-3.1-pro-previewReads images
qwen3.8:27bLocal only

Screenshots are sent only to the models that read images. The rest work from the transcript alone.

Running locally, the Claude models generate through your logged-in Claude Code CLI and bill your Claude plan instead of the Anthropic API. Screenshots are not sent on those turns, because that bridge is text-only. Switch it off under Settings → Claude subscription.

ServiceNow (MCP)

Documents checked against the live instance

Connect an instance in the Settings tab and the model reads it, read-only, while writing.

  • Confirms tables, fields, stored choice values, scripts, catalog items, flows, and records before stating them
  • Reads every input you gave it — description, guiding questions, typed comments and notes, captions, transcript — and corrects any of them against the instance
  • Trusts what you typed over what was transcribed, because a transcriber mishears table and field names and a typed note does not
  • Tags anything it cannot confirm as [UNVERIFIED] instead of inventing a sys_id
  • Ends every document with a Verified Against ServiceNow table listing what it checked

Nothing is written back. Generation takes longer while the model queries, and if the instance cannot be reached your documents are still written from the transcript. Articles verified this way carry an instance-verified tag in Generated Files.

During a session

What you can capture while recording

  • Live transcription with speaker tracking and word corrections
  • Bookmarks for the moments you will want to find later
  • Screenshots of a screen or a region, downloadable as a set
  • Video clips that can be transcribed into the session description
  • Meeting notes — comments, questions, instructions, action items and decisions, saved with the session and fed to the model
  • Session replay, console capture, and code dependencies in the right column

Drag any panel by its grip to float it over the page, then Dock to put it back.

Templates

So a recurring meeting starts the same way

A template pre-fills a new session. Build them in the Templates tab.

  • Name, description, and domain
  • Default output formats, all five unless you narrow them
  • Guiding questions, folded into the generation prompt
  • Default participants

Guiding questions

From the template on the current session

Select a template to load guiding questions, or start fresh.

$5.00 Per session

Pricing

Charged once when you start a knowledge capture, covering the transcription and every document the session generates. Usage tier only.

Deducted on success and refunded automatically if generation fails. Admin accounts are not charged, and ServiceNow (MCP) grounding costs nothing extra.

ServiceNow (MCP)

Not connected

Connect the instance this session is about. Once connected, the AI model can read it while generating your documents: it confirms the tables, fields, stored choice values, scripts and records the session covers, corrects the transcript where the instance disagrees, and lists what it checked. Access is read-only; the connection stays saved in this browser until you disconnect.

Grounding Not connected
The model looks up the tables, fields, stored choice values, scripts and records the session is about — drawn from your description, typed comments and notes, captions, and the spoken transcript alike — corrects any of them where the instance disagrees, and closes each document with a Verified Against ServiceNow section. Nothing is written to the instance.
Connect an instance above to turn this on.

Claude subscription

Checking…

Choose how the Claude models are billed. Subscription generates through your logged-in Claude Code CLI, so the work goes against your Claude plan rather than per token; it is available only when Knowledge Base runs on your machine. API uses the Anthropic API key. ServiceNow (MCP) grounding works either way: on a subscription turn the instance tools are carried to the CLI as a text protocol and executed against the same read budget.

Billing Checking…
Bill Claude models to
Checking for a logged-in Claude Code CLI…
What to expect
  • Applies to Claude models only. GLM, DeepSeek, GPT and Gemini are unaffected.
  • Choose API to bill the Anthropic API key per token instead.
  • Your choice is remembered on this browser and applies to the next session you record.
  • Screenshots are not sent on a subscription turn — the CLI is a text pipe, so session images reach the vision-capable models only.
  • Unavailable when the app runs in the cloud, where there is no logged-in CLI. Generation falls back to the API automatically.

Session Templates

No templates yet. Create one to get started.

New Template

Article

100%
Screenshot

Session Screenshots

Video Clips

Loading video clips...