explaingit

chartitec/glaskuser

Analysis updated 2026-05-18

1PythonAudience · researcherComplexity · 4/5Setup · moderate

TLDR

Turns archived user research interviews into queryable AI personas, so you can ask new questions grounded in what real users actually said.

Mindmap

mindmap
  root((GlaskUser))
    What it does
      Builds AI personas
      Grounds answers in transcripts
      Flags unanswerable questions
    Tech stack
      Python
      Whisper
      Claude Code
    Use cases
      Simulate past interviews
      Search interview excerpts
      Compare user cohorts
    Audience
      User researchers
      Product teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Simulate a conversation with a past interview participant to ask a new question.

USE CASE 2

Search across archived interviews for excerpts on a specific topic.

USE CASE 3

Compare responses across a cohort of user research participants.

What is it built with?

PythonWhisperClaude CodeAnthropic API

How does it compare?

chartitec/glaskusera-bissell/unleash-liteabhiinnovates/whatsapp-hr-assistant
Stars111
LanguagePythonPythonPython
Setup difficultymoderatehardhard
Complexity4/54/53/5
Audienceresearcherresearcherdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Requires Claude Code, an Anthropic API key, and Python 3.10 or newer.

In plain English

GlaskUser turns archived user research recordings and transcripts into a set of AI personas you can query like having another interview. The problem it targets is that historical interview data is typically shelved once a project ends, making it hard to answer new questions from the same users or compare responses across a cohort. The core idea is to extract a psychological model from each user's interview material, covering core values, decision frameworks, and inference rules, and ground every AI response to that user's actual corpus. When a question falls outside what was discussed, the persona explicitly says so rather than guessing. This makes it distinct from general AI-generated user profiles, which have no traceability to real people. Getting started requires Claude Code with an Anthropic API key. You run a single setup command (/glaskuser_init) and Claude guides the rest: it installs dependencies, downloads a Whisper speech-to-text model and a semantic search model, transcribes any audio or video, builds a vector index, and extracts psychological models for each user. Supported input formats include audio (.mp3.wav.m4a.aac.ogg.flac.webm), video (.mp4.mov.avi.mkv), transcripts (.txt.pdf.md.docx), and spreadsheets for surveys or usage logs. Audio transcription and semantic search run locally, the indexed corpus is passed to the Anthropic API through Claude Code for questioning. Once set up, /glaskuser_simulate opens a conversation with a single user persona, and /glaskuser_search retrieves raw interview excerpts by topic. Python 3.10 or newer is required. The full README is longer than what was provided.

Copy-paste prompts

Prompt 1
Run /glaskuser_init to set up GlaskUser on my folder of interview recordings.
Prompt 2
Use /glaskuser_simulate to ask this user persona about their onboarding experience.
Prompt 3
Use /glaskuser_search to find every mention of pricing across my interview archive.

Frequently asked questions

What is glaskuser?

Turns archived user research interviews into queryable AI personas, so you can ask new questions grounded in what real users actually said.

What language is glaskuser written in?

Mainly Python. The stack also includes Python, Whisper, Claude Code.

How hard is glaskuser to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is glaskuser for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.