What's new

New public pages. /pricing (Solo $19, Team $80 billed yearly, your own AI key explained in plain words, a per-question cost estimate with its assumption stated, FAQ), /changelog (built from this page’s changelog…

waitlist_open event — every "Join the waitlist" CTA now fires waitlist_open (GA + dh-track) when the modal opens, so the funnel reads page_view → waitlist_open → waitlist_click → waitlist_join.

link previews (X, LinkedIn, Slack) showed the old violet “company brain that shows its receipts” card.

took the "Launched on Fazier" badge off PersonalityPage.jsx, App.jsx and the crawler footer in landing.html, at the founder's request.

One registry of everything posted.

the scroll-reveal treated the hero like any other section: it started at opacity 0 with its fadeUp animations paused until an IntersectionObserver fired, then ran a .7s fade plus a further .1–.2s delayed fadeUp.

the Sep 30 repositioning only edited the old landing (App.jsx).

/support, needed for the Slack Marketplace listing.

/alternatives/dashworks-alternatives (HubSpot bought Dashworks; product shut down 16 July 2025, sourced), /alternatives/glean-alternatives (self-serve options for small teams) and /alternatives/guru-alternatives.

Fixed (Sentry ENHANCIAR-BACKEND-15): MCP clients calling get_page without both category and name hit a pydantic ToolError.

Changed: the hero headline, page title, meta description and social (OG/Twitter) tags now lead with “Ask your company anything.

a small “Launched on Fazier” badge in the landing footer (both landing variants and the crawler-visible static footer), required for Enhanciar's free Fazier directory listing.

/alternatives/unblocked-alternatives, /alternatives/swimm-alternatives and /compare/best-tools-to-understand-a-codebase.

/guides/understand-legacy-codebase-fast, /guides/git-blame-alternatives and /guides/onboarding-engineers-large-codebase.

The symptom. The secrets job (gitleaks over full history) failed on three historical findings: two generic-api-key hits in scripts/run_retrieval_eval.py and PLAN_GRAPH_MEMORY_IMPL.md (commit 99751f1), and a private-key…

The symptom. Searching “enhanciar” on Google returned results for “enhancer”.

New admin page: Promotion.

“5–50 person engineering teams” removed from /vs/glean.

Deploy target fixed. The devhive→enhanciar rename (2026-09-20) also changed deploy.yml to deploy main to a new Cloud Run service named enhanciar.

The brain names who can answer.

The marketing page is rebuilt from a Claude Design file, mechanically.

The force simulation is gone, and the cloud with it.

The error blamed the only part the user had right.

A saved key and a locked model list, both true, neither explained.

The pane had grown by accretion and read like it.

“None is available” was never true.

Every application log line reached Cloud Run as DEFAULT.

“Confirmation is on its way to your inbox” — for a message that did not exist.

Two repos with the same file path — real, and worse than a gap.

A workspace with two databases could query only one of them.

The structural-question block shipped hours earlier and was called done.

The log said the pipeline had already won: reason=ok · blocks=1 · image_cols=['images'] · q='show me photos from CustomPopularTreks'.

Expansion kept the first 15 inner keys.

cols=['Details', 'price', 'isCustom'] · image_cols=[] — the diagnostic added minutes earlier settled it.

Two prompt fixes in a row failed to produce a picture.

The photos question fetched everything it needed and still answered in prose.

“What treks do you have running between November and January” started answering NONE.

Deep thinking was silently off for every Claude 5 model — the exact bug found in the Gemini path hours earlier, one provider over.

Two repos, two Firebase projects, one reachable.

One data shape, two readers, and the second one was wrong.

A button whose only failure mode is “nothing came back” is unactionable for the user and unfindable for us.

The scan read chats; the connector pipeline writes conversations.

Four panes told a user to connect things they had already connected.

Asked what happens when a question spans more pages than the context budget holds, the answer turned out to be a citation bug.

Capping the row cell would have broken the feature it was meant to protect.

“Explain how the trek booking flow works end to end” read the Orders collection and printed real customers’ email addresses into the answer.

Moving live-data work inside the stream put the await AFTER the prompt was built.

Every server-side test passed, and the answer still arrived in one lump.

Asked to change trek dates, the chat refused and stopped.

A second repo silently deleted the first repo’s pages.

A connector row rendered “Connect” before its status arrived, then flipped to “Connected” a moment later.

Three outages this month were one shape: something written under wiki/<ns>/ that nobody added to the durable-mirror allowlist, so it lived exactly as long as the pod.

The symptom was a vanished “connect Firebase” banner; the cause emptied the whole brain.

Ask “good treks for winter” with Firebase connected and the answer can arrive as cards; ask for date-wise trends and it can arrive as a line chart.

Caught live, watching a README-only auto-ingest re-extract all eight domains.

“worker LLM saw database code” told the user nothing they could check — while the Firebase card beside it named package.json, firebase.json and a projectId.

A Razorpay key_id rode into a stored evidence quote — by policy, not by accident.

On a run with 100% file coverage, 54 of 93 wikilinks still dangled.

The fresh audit showed the bottleneck had moved: the worker could SEE all 66 files and still wrote 40 entities.

“If I rerun, it picks up the failed ones, right?” The honest answer was no — twice.

Naming every file is not the same as covering it.

42% of a real workspace’s files had no wiki page — including its two largest components — and the cause was an 8000-character string cap.

The ingest banner says a detected credential’s value “was never sent to a model or written to the wiki” — and the verify stage broke both halves.

The detected-sources banner lived exactly as long as one pod.

Impact offered “Ingest a repo” beside 256 analysable files.

The whole failure rendered as [object Object].

It opened straight onto whichever run was newest.

Two price tables, disagreeing.

Resuming always worked; nothing offered it.

Same symptom, different engine.

The property covers every subdomain.

The reassurance arrived too late to reassure.

Everyone saw only their own runs.

Picking the only branch on offer failed the clone.

Two screens, two answers.

An owner with a working key was asked to type it again.

Teammates could not see the workspace’s GitHub connection at all.

The button labelled “Accept the invite” accepted nothing.

The one-button install could not tell “nothing to link” from “could not check”.

The switcher offered a choice nobody had been told about.

The remembered workspace and the real list were never reconciled.

Your connected repos were the hardest ones to reach.

“install” and “re-sync” asked the user to know something they cannot.

One browser-wide flag stood in for a per-account fact.

The open menu’s active row drew a square ring inside a rounded panel.

Chips sized to their own labels cannot be a grid.

One flag meant two different things.

The fourth provider was never mentioned at the moment it matters most.

Two components were both answering “is there anything here”, and during a fetch they answered differently.

The direction of the list is the whole design.

The secret-scan test contained a shape-accurate fake GitHub token, and gitleaks failed the build on it (238b68b).

This is a report, and it is not the control.

The guard caught credential files, and the leak was not in one.

redact.py exists because a private clone URL carries a live GitHub token, and every event, job document and outbound webhook that echoed “the source” was publishing it.

132 of 502 claims on one real wiki came back “unsupported”, which a reader takes to mean the product made them up.

Nothing was lost. A team-workspace ingest wrote wiki/ws_…/; three panes read wiki/{uid}/.

“Detected in your ingested code” named no evidence, so it read like a guess.

Open a connector, go to Chat, come back to Connectors — and you were looking at that connector again, with no memory of having asked for it and a “← All connectors” button as the only clue about…

Both buttons on a repo card stayed live while the job they started was still running.

Pressing Ingest code showed a toast ending “Watch it in Ingest → Activity”.

The progress line “📥 Cloning …” printed the job’s source, and for a repo reached through the GitHub App the source is a credential.

A push into any repo the App could see used to trigger a full first-time ingest.

“＋ Code” and “＋ Issues + PRs” told you almost nothing.

Reported on the GitHub pane’s branch picker, but none of it was that pane’s fault.

Twenty browser-default dropdowns were left in the app.

A native <select> gives you Up/Down, Enter, Escape, Home/End and type-a-letter-to-jump for free.

Auto-sync was hardcoded to the repo’s default branch.

Every push-triggered re-ingest went to the installer’s personal brain.

The connector page claimed the App never writes.

The MCP server had no workspace concept at all.

The member column was a raw Firebase uid.

“I couldn’t find anything on that in your brain yet” describes a search that happened.

The panes kept showing the workspace you had just left.

The run header was a different object.

Seven panes, seven widths.

This was the last always-personal ingest.

One key per workspace, supplied by its owner.

The meter recorded one identity, and a team has two.

The symptom. With a team workspace active, connect Notion — the form saves, the badge says connected, the Connectors grid says connected — and the ingest fails with “Notion is not connected for this…

They were one operation, and they should never have been.

Deleting your account used to strand every team you owned.

The symptom. With a team workspace active, uploading a file (or pasting a note, or adding a URL) reported success and queued a job, and the job reported “No documents found in Files & Notes”.

Read this bit first: your figures increase, and nothing got more expensive.

The eleventh bug of one shape, and it broke the two features shipped this morning.

no-undef cannot see JSX element names.

Karpathy’s “LLM Wiki” pattern names three operations: ingest, query, lint.

Ingest checks the wiki; nothing checked the answer.

Any member could overwrite or clear a team’s connector credentials.

Saving a key told you nothing.

Ten instances of one bug have shipped.

Every entry point on the usage meter is uid-scoped, and one write passed a namespace.

The unique-index test read t.indexes, a key the ERD payload has never carried.

Tier 1 reads _ast/*.json and _code_graph/*.json; only the second one survived a restart.

Three lines in the launch and YC docs claimed a “Reviewer” that did not exist and a guarantee nothing could keep — “verifies every claim against the call graph (no hallucinations)”,…

Verify is a real stage now — step 6 of 8.

What tier 1 cannot settle now reaches a model — one call per page, not per claim.

A citation only ever proved a page had been read.

It was removed a few entries ago, and that was right at the time.

the run status pill was hard-coded green for every state.

The dropzone says what it does.

The three source kinds are rows in one card, not three cards.

One measured column instead of three sub-views each inventing their own.

A chat message can carry an icon now, because the emoji in them were not decoration — they were part of the text.

The icon table the sidebar already owned grew to cover the rest of the app.

A DEPTH select with no state and no handler, and three switches that flipped a variable nobody read.

The rule was: high above 20 transitive nodes or criticality 70, medium above 5, otherwise low.

The intake routes were the last three that did not take a workspace header.

It seeded its list from the merged read and then wrote that list back.

Every clear was undone by the next read.

The green banner’s condition was “the App is installed and has at least one installation”.

The answer was rendered into a white-space: pre-wrap div.

The previous pass moved connector credentials to the workspace document and fixed one of four readers.

GET /api/account/preferences raised NameError on every single request.

Every event marker in the ingest feed is a drawn glyph.

The rail and the detail are full-bleed in the pane.

Skills cards say what kind of skill they are and how long the procedure is.

Inviting is why you open a team card, and it was a click away.

The sidebar is 206px (was 212), and the selected item’s icon now carries the design’s duotone fill — rgba(28,82,93,0.20) inside the drawn stroke — so the active row reads as filled rather than…

Attach feeds the file into the brain — the same multipart POST, the same ingest job and the same per-file status the Feed-files pane runs, now shared in one module so the two surfaces cannot accept different files…

One number, everywhere it was wrong.

The idle Ingest card promised Scout, Workers, Integrator, Graph, Verify.

It is a word collision, not a broken toggle.

Slack has short-circuited greetings since it shipped; the web chat did not.

The Tables filter was across the pane from the list it filters.

The progress figure was presented as a measurement.

Citations rendered as a panel stapled under the answer card — its own border, its own background, bottom corners rounded to fake continuity.

Actions, Code Reviews and Impact each rendered a bare grey “Loading…” while they fetched, and their own one-line empty hints when they came back with nothing.

Every card led with the tracker chip — Jira, Linear, GitHub — in the same accent violet, so in a queue of twenty a contradiction and a missing document looked identical and you had to open each one to find…

Events rendered newest-first and never scrolled.

Every entry was an <a> with no href and no click handler.

The design wanted a RISK badge on each dependency path.

Stage information existed only as prose, and the prose had drifted.

A connector ingest was all-or-nothing.

A live wiki-page count during a run.

An ingest was running when a new revision deployed.

The activity feed is the one deliberately dark surface in the app — a #14161a terminal with per-event text colours set inline.

The Ingest rail listed eight connectors from a hardcoded catalog; Database and Confluence were not in it.

Saving the list used to require re-typing every connection string.

Saving wrote users/{uid} unconditionally; every reader resolved by NAMESPACE.

It fetched /api/connectors once, on mount, and never again.

Five CSS variables were used but declared nowhere.

There were two database implementations and they did not talk to each other.

Your own turns were indistinguishable from the agent’s.

Onboarding announced “Your 14-day free trial is live”.

This changelog was the only thing in the site footer a new customer could click hoping to learn how the product works.

Every answer carried a “+ Create ticket from this” button, whether or not the answer implied any work.

In Slack it produced “the provided context does not contain information to answer your query” — true, and a terrible first impression, since a greeting is exactly what a new teammate types first.

It applies to the first ingest only — so the one moment it matters is the moment you are about to press Start ingest, and it was sitting on the Connectors page, a screen you visit to manage a connection rather…

“Available to ingest” showed 1785591344.239279.

The symptom: Connectors said Slack was connected and the Ingest page said it was not — the same question answered two ways on two screens.

It read 254 / 50,000 today while daily token caps existed.

Every colour already matched the design exactly — accent, all four surfaces, borders, text, radii, shadows, token for token.

Settings carried two sections wrapped in {false && …} — an email-notifications block whose toggles persisted to Firestore that nothing read (we send no email), and a beta-features list whose flags…

Nothing on the connected panel mentioned @mentions.

Disconnect used to delete our record and tell Slack nothing.

Five panes rebuilt to the revised design, and the rule was “omit rather than invent”.

Every mockup is full of data.

Impact now answers the question you have next.

Capping tokens protected nobody.

GitHub webhooks can no longer be replayed.

And now it only pulls what changed.

The site published seven addresses; the account has one mailbox.

Almost all of this already existed.

The gap. An invited address that already has an Enhanciar account skips the invite/token path entirely — the uid resolves, the roster updates, the call returns.

The bug. _enforce_member_cap read the owner's stored plan field directly instead of going through billing.effective_plan_id — the one resolver that both honours the sandbox test-plan override and downgrades expired…

Renamed, not rebuilt.

Connected sources had no logos.

Settings was rendering emoji as UI icons.

What shipped. Home is now two columns, per the Claude Design comp (Enhanciar App.dc.html): the activation checklist keeps the left, and a new rail on the right carries Recent sources (drawn from the manifests Home…

The gap. enhanciar.in is served by Firebase Hosting, not Cloud Run: Hosting serves every static page and the built SPA bundles itself and only forwards a few prefixes (/devhive/**, /enhanciar/api/**, …) to the Cloud Run…

Removal was silent too.

New /security page. We ask people to connect their codebase, their Slack and sometimes their inbox, and until now the only answer to "what can this thing actually do with my data" was a four-tile band on the landing…

The identity join. Connector pages now carry doc_id + body_sha frontmatter, and a resolver re-links existing pages to their source documents retroactively (URL first, stored ids second, slug reversal third — and it…

Connector pages had no freshness signal at all.

Ranking penalty, on both retrieval paths.

Every "incremental" re-ingest was secretly a full one.

The bug. MobileChatApp.jsx froze its session_id for the life of the mount (useState(genSessionId)) and the "＋ New chat" button only reset the message list, never the id.

The bug. Verified live with a freshly-created Google AI Studio key: gemini-2.5-flash and gemini-2.5-flash-lite both return HTTP 404 — "This model is no longer available to new users", and gemini-2.5-pro returns 429 (no…

Action chips are now a UI, not just a wire event (A3).

Connect-DB chips on live-data misses.

NL→SQL is provider-agnostic.

Team workspaces now see detected-DB suggestions.

New 🧪 card on Billing (sandbox only).

Delete a team workspace (new).

The landing hero graphic broke every phone.

The problem, measured.

The Early Access endpoint read the same Firestore document five times per request.

A real purchase was invisible in the admin Billing page — two causes.

The pay button came back to life while the payment was still being verified.

Charge currency is switchable from the admin panel too — because it decides which payment methods exist.

Backend waitlist gate (closes the frontend-only bypass).

One build, two behaviours, resolved at runtime.

Enhanciar-only URLs, everywhere the user can see.

Keep an eye on the keys from the ops panel, not the product.

The Pass grants priority in the queue, not an instant unlock.

Numbers nobody outside the repo can check are just adjectives.

Retrieval never found out whether it was right.

Every question used to get the same answer strategy.

The graph knew that two things were related; now it knows how.

You cannot optimize what you cannot measure.

New "From knowledge to action" section (landing/ActionsSection.jsx): a transcript card morphing into an approval queue with a Jira and a Linear card and one violet Approve CTA.

MCP: read + propose, never approve/execute.

Workforce → queue. When a Workforce agent's run report ends with a "## Proposed actions" (or "## Actions") section, its bullet items are filed into the same approval queue as everything else (source="workforce", linked…

Gmail draft (gmail.create_draft): creates a draft and never sends — sending stays a deliberate human click in Gmail.

GitHub issue (github.create_issue): new github_app.create_issue resolves the repo's installation token and POSTs the issue; targets() lists your connected repos.

Doc-type sniff during ingest.

New Actions tab (frontend/src/components/ActionsPanel.jsx, under Ship).

One more field in the same enrichment call — zero extra LLM cost.

Two real executors. enhanciar/actions/jira_actions.py and linear_actions.py are thin ActionExecutor adapters: targets() lists the pickable destinations (Jira projects / Linear teams), render_preview() shows the exact…

New package enhanciar/actions/.

Per-deployment env, declared in deploy.yml.

New precedence tier in feature_flags.is_enabled: ENHANCIAR_FF_FORCE_<FLAG>.

New module enhanciar/sandbox_gate.py + middleware in server.py.

Extracted the BYOK LLM-completion helpers (_call_llm, _litellm_completion, _gemini_completion, _parse_skill_json) from enhanciar/skills.py into a new enhanciar/llm_call.py; skills.py re-exports them for compatibility.

Sync watermark no longer advances past unlisted documents.

The admin-controlled demo-data mode is gone.

Chat streaming dropped tokens split across network chunks.

New module enhanciar/vector_index.py.

The prior pass had softened every Confluence mention on the landing page ("shipping soon") because the catalog flagged it status: P.

Positioning fix. Hero, Problem, Features and the crawlable SEO snapshot all illustrated the product exclusively with code examples ("blast radius," callers/callees, oauth.py:74), even though the ingestion side already…

Accuracy fix — Confluence overstated as live.

No longer instant/priority access.

Headline de-narrowed — "The affordable team brain that knows why" → "The affordable brain that knows why" (H1 + footer tagline).

Removed the old "Enhanciar" brand name from everywhere it could reach a human: the agent system prompts (scout/worker/integrator/query — the chatbot could have called itself "Enhanciar"), the knowledge doc served to AI…

Joining no longer surfaces a position number — the modal success, the confirmation email (subject + body), and the in-app "you're on the list" gate all drop the "#N".

Every "Join the waitlist" CTA now opens a redesigned modal (nav, hero, pricing tiers, CTA band, code-review, demo) instead of an inline form — brand header, one email field, two actions, a highlighted Early Access card,…

Hard "closed" gate. While the waitlist_mode flag is on, every app route (/login, /app, mobile) renders a full-screen "Enhanciar is in early access — join the waitlist" screen before any auth, with no Google sign-in…

Fabricated testimonials removed — the three invented customer quotes ("Mira K., Foundry Labs"…) are replaced with real, attributable quotes about the problem (HN on Confluence rot, HN on hallucinating AI wikis,…

Waitlist capture on the landing page — hero and bottom-CTA email forms post to the new public POST /api/waitlist (per-IP throttled, idempotent by email).

Switching tabs no longer refetches the Drive listing.

Prerendered landing content — the homepage body was an empty React shell without JavaScript, invisible to GPTBot/ClaudeBot/Perplexity/CCBot (and slow for Google's first pass).

Switching a filter (or typing a search) now clears the stale list instantly and shows a spinner ("Searching your whole Drive…") while the server-side Drive query runs — before, the old rows sat frozen for a second or…

Server-side filters in the file browser.

Exact count, not "100+".

Why you only ever saw ~100 files: the Drive connector's first full ingest carried a hard v1 cap of 100 files ("keeps demos quick") — a real Drive with thousands of files silently truncated.

No more blind ingest.

Every Drive file now carries its folder path (📁 Projects/Purplle / release.apk) instead of flattening your whole Drive into one anonymous pile.

The Enhanciar mark in the chat agent avatar was purple-on-purple — the logo rendered in its default brand purple on the purple gradient chip, leaving a barely-visible smudge.

One chip instead of two.

Pressing Enter/Ask while a booking chip is live now opens the booking confirm instead of sending "schedule a meet tomorrow 1pm" to the wiki-grounded Query Agent — which has no calendar tools and could only reply "the…

Cost & quota reset to zeros after every deploy.

The container now builds inside GitHub Actions (docker buildx, cache-from/to: type=gha) and Cloud Run deploys the pushed image — replacing gcloud run deploy --source, whose ephemeral Cloud Build workers reinstalled npm…

Newer Chrome makes scrollIntoView() return a Promise (scroll-completion spec).

The "Available to ingest" list now shows the first 8 items with a "+ N more — Start ingest pulls all of them" footer, instead of scrolling 100 rows of your inbox at you.

Connected Google sources appear under "Connected sources" on the Ingest page.

Root cause: since Jun 28 the prod service ran with --no-cpu-throttling (2 always-on vCPUs billed whenever an instance is awake) — added so background in-process ingests wouldn't stall.

New threads appear in the sidebar the instant you hit send — optimistically, using your first line as a provisional title — instead of only showing up after the answer finished and saved.

Google + Slack OAuth now round-trip on /enhanciar/ in prod.

A workspace must add its own Google OAuth client before connecting.

User-facing URLs now say /enhanciar/.

One paste instead of five hunts.

Google Calendar no longer shows an "Ingest" option.

Chat answers calendar questions in real time.

The app paints far faster now.

The scheduling chip now books.

Two fast/cheap models added to the picker: Anthropic Claude Haiku 4.5 (BYOK) and Ollama Cloud · gpt-oss 20B (free) — the missing lite tiers for those providers.

Invite teammates by email.

Email is private; calendar and everything else is shared.

New Google Calendar connector (gcal).

"Ingest →" now actually starts the sync.

See exactly what the first sync will pull, before you run it.

Ghost buttons fixed. The "one more step" callout after connecting Notion/Slack told users to "hit Refresh, then ⚡ Ingest now" — neither button exists; the real one is Ingest →.

Expired Google tokens now prompt a clean reconnect instead of failing silently.

Upload an image or short video → the brain reads it.

Confluence Cloud pages.

Google Drive now extracts PDF & Word content instead of storing placeholders.

Landing/Settings subscribers were paying but staying paywalled.

WhatsApp no longer leaks sample data in prod.

The paid product was effectively free.

Subscriptions now activate synchronously (no more "paid but paywalled").

F2 · connector secrets encrypted at rest.

A security review found that POST /api/overview/regenerate was gated only by current_uid, not enforce_token_cap — so a free/over-cap user could run LLM overview synthesis for free (unmetered), and with provider=google +…

Usage now mirrored to Firestore.

Trial disabled → hard paywall.

No free tier. The billing overview no longer shows the ₹0 “Free/forever” plan anywhere.

Un-hid Gmail/Drive (previously hidden behind Google's restricted-scope CASA audit).

Fixed the "weird" billing page.

Opt-in daily sync. New per-workspace Daily auto-refresh toggle in Settings (default OFF).

Robust entities in the router index.

The welcome email claimed a “14-day free trial … no card needed” in 4 places — Enhanciar has no trial (it's a paid BYOK product; the landing copy was already fixed, the email was missed).

Fixed wrong copy. An earlier note claimed connector ingest was “raw, no LLM, no cost.” That was wrong — the generic pipeline runs a compulsory per-document enrichment pass (summary · key points · entities) by default…

Ingest connectors like GitHub/Website.

Key box collapses once connected.

Saving a Notion token isn’t enough — Notion only exposes pages you explicitly connect to the integration (••• → Connections → Enhanciar).

Ingest is now the obvious action.

Gmail and Drive use restricted Google scopes (gmail.readonly, drive.readonly) that can’t be opened to the public until a full Google verification + CASA security audit clears.

Gmail / Drive / Slack “Connect” now works.

See what will be pulled before ingesting.

Settings was one long scroll of ~12 sections.

Connector key form. The button was always “✓ Connect” even with a key already saved.

See what each connector pulled in.

Enter the key on the connector itself.

Notion how-to matches Notion’s new UI.

Login lands on Home. A genuine sign-in (signed-out → signed-in) now routes to the Home tab; a plain refresh still restores your last tab, and deep links (post-GitHub-install, billing) still win.

Credential dumps are never ingested.

LLM + deterministic, merged.

Read-only live queries.

The query agent picks the component.

DB detection at ingest.

Overall progress bar on the Activity/monitor — a single weighted bar (scout 15% · workers 55% · integrator 30%) with a live Processing X/Y files · N% label and green/red end states, above the event feed.

Thinking disabled by default.

The deeper cause of duplicates: the Scout routinely emits overlapping domain paths — three domains at /src/Containers, another at /src, etc.

the Scout sometimes assigned the same directory to two domains (e.g.

Root-cause fix — output truncation.

Added Ollama Cloud · gpt-oss 120B and Qwen3-Coder 480B to the Active-model picker (Settings).

Added Groq · Llama 3.3 70B and Llama 3.1 8B to the Active-model picker (Settings).

The graph now carries sources_all per node, and the Galaxy Map gained source-filter chips (Github / Web / Slack…).

Ingesting the same entity from two sources (e.g.

The file detail panel read fields (symbols/loc/in_edges/out_edges) the code-graph never returns, so every stat showed a dash.

Clicking a file node (e.g.

Galaxy is THE Map: the Galaxy | Constellation | Force toggle is gone — the Map tab is the Galaxy view only (the Constellation canvas lives on in the Workforce tab; the 1.1k-line legacy force view is deleted).

New Galaxy view on the Map tab — a canvas-rendered force-directed galaxy of the whole brain: every node as a community-colored dot with organic starburst clustering, hairline edges, and Obsidian-style labels that fade…

New Workforce tab (feature flag workforce, default ON): your agents as hubs on the shared night-sky constellation, their runs as chain stars (done runs ring in the agent's accent).

New Constellation view on the Map tab (default): a dark night-sky canvas (#0c0d10) with a drifting particle core ("the brain"), your graph communities as color-accented hubs on a radial ring, and their top members…

New IA: the 9-tab top nav + "More" overflow is now a grouped left sidebar (Home · Chat · Knowledge · Data · Sources · Ship · Account) with Phosphor duotone icons — zero emoji in…

Connector OAuth redirects fixed: GitHub, Slack and Google callbacks now return to the app via a base-path-aware _spa_redirect() helper (ENHANCIAR_SPA_BASE, default /enhanciar) instead of a bare /app.

Rewrote enhanciar/web_scraper.py as a Python port of the open-source Firecrawl pipeline (we cloned and analyzed the actual source).

Skip the clone when nothing changed: a re-ingest now first runs git ls-remote (one cheap network call, no clone) and compares the remote commit SHA to the last-ingested SHA (stored in the incremental state).

Product Overview page (NEW): ingest now synthesises a plain-English product-overview page from the extracted entities — leading with the product type and domain (e.g.

chats lived only in memory, so a refresh wiped them and the sidebar was a "coming soon" placeholder.

Node labels are now truncated to each box's actual width (mono ≈ 6.8px/char) so text can't overflow or overlap neighbours, and the affected-files band is capped at 6 for breathing room.

Blast-radius graph inline in Chat: ask "what breaks if I change src/App.js?" and the agent now appends a [[impact:<target>]] marker that the chat replaces with a live visual blast-radius graph (new…

Target picker: the 💥 Impact box is now a searchable dropdown of every analyzable file / function / entity in the brain (new GET /api/impact/targets + impact.list_targets), instead of free text you had to remember.

Readable logs: progress events used to dump raw JSON ({"type":"progress","data":{"total":117,…}}) because they carry no message.

deleting an Enhanciar account purges the github_installations mapping, but the App stays installed on GitHub.

media-heavy repos (e.g.

Source field on every node: the graph builder now stamps each node with its ingestion source — github, github issues, slack, notion, jira, linear, zendesk, google drive, web, … (from connector frontmatter; code/file…

the durability layer only backed up .md wiki pages to GCS/Firestore — it never persisted the code-graph artifacts Impact reads (_code_graph/*.json caller/callee edges, _index/cross_index.json, graph.json).

Code Reviews — repo & PR pickers: the owner/name box is now a themed, searchable dropdown of your connected GitHub repos (new StyledSelect.jsx — a light-theme popover with a filter, replacing the unstyled native…

Reflects the whole product, not just code: the "What happens next" steps now read Connect your sources (GitHub + Slack) → Agents read everything (code · threads · docs) → Ask · review · trace impact; plus a new "One…

Problem: the hero image was weak and only 1 of the 3 "How it works" step cards had a visual.

Problem: the Add-source view left the bottom half of the screen empty and barren.

GET /api/connectors returned credentials_configured: null for GitHub, Slack and Google (their connection state lives in installations/OAuth, not the user doc) — so the Connectors grid + Ingest "Connected sources" showed…

Per-connector setup guides: a new reusable SetupGuide block on every connector's detail page — numbered steps + a prominent external link (new tab).

Add source trimmed: removed the "Local path" source type, renamed "ZIP / tarball" → "ZIP", and a little top margin added above the Add source / Feed files / Activity sub-tabs.

One flow, one tab: the separate Ingest, Feed and Monitor primary tabs are now a single ⚡ Ingest tab with a segmented control — Add source · Feed files · Activity — since they're really one journey: add a source / drop…

Impact / blast-radius analysis (NEW): a new 💥 Impact tab + GET /api/impact?target=…&depth=… + an impact MCP tool.

The launch-blocker: pasting a bare GitHub slug (pallets/itsdangerous) on the Ingest page reported "Pipeline complete 🎉" but built 0 nodes.

Removed the standalone "Code Review" pricing tier from the landing Pricing section and the billing.PLANS catalog — it ships inside the existing Solo/Team plans, so there's no separate plan and no Razorpay plan IDs…

PR summary + type/risk: every review now opens with a plain-English summary, a change-type tag (feature/bugfix/refactor/…) and a merge-risk read, rendered above the findings table.

Before: login and the app shared one URL (/enhanciar/ rendered SignupScreen when signed-out, the app when signed-in); landing was at /.

returning, already-signed-in users hitting the root URL saw the full marketing landing paint for a split second before onAuthStateChanged resolved (Firebase persists auth async in IndexedDB) and redirected them to…

Landing page: new dedicated CodeReviewSection (id #code-review) between Features and Steps — headline "Senior-level code review.

Shipped a 30-second cinematic SaaS launch video (1920×1080) modeled on the best AI-SaaS launch references (LangEase / kinetic-type style).

New "🔍 Code Reviews" tab (More ▾ → Features) — a front-end surface for the BYOK review engine.

Shipped the backend engine that reviews PRs with the workspace's own LLM key.

Reshot the full 2-minute launch film with an identity-locked recurring cast.

Shipped a 2-minute stop-motion claymation launch film for Enhanciar.

All jobs are now visible in the Monitor.

The repo was missing from the wiki.

"Show me the code" now works in chat — the root cause was the production chat using the BYOK path (user's own Gemini key, since Vertex is off in prod), which calls the model directly with wiki context and never invokes…

Billing tab no longer crashes — PaymentFlow called .toLocaleString() directly on plan fields (price_inr_monthly, daily_token_cap, …) that can be null in the catalog, throwing Cannot read properties of null inside the…

Graph now has real edges — connector pages (tickets/chats/docs/schemas) almost never use [[wiki links]], so the graph was 30 nodes with ~1 edge (a cloud of disconnected dots).

Source filter chips — the Wiki sidebar now has a row of connector chips (All · GitHub · Slack · Jira · Linear · Zendesk · Gmail · Drive · Files · Database · WhatsApp …) with per-source counts, so you can isolate "just…

Fixed Monitor "stuck on 1/24" — the demo/generic pipeline was emitting every per-doc progress event correctly (verified: a completed demo job had all 24 progress events + status done), but the UI froze on the first one.

No more sideways jump when switching tabs — each tab is its own scroll container (.dh-body .tab-pane { overflow:auto }).

Live enrichment counter in Monitor — the generic/demo pipeline now emits a per-document progress event (🤖 [i/N] Enriching…) before each LLM call, and the Monitor shows a live "Enriching i/N" count + a Workers progress…

New "🔌 Connectors" tab (after Tree) — a hub listing every source (GitHub, WhatsApp, Slack, Notion, Jira, Linear, Zendesk, Gmail, Drive, Files, Database) with live connection status; each card jumps straight to where…

New WhatsApp tab (More ▾ → Integrations) — Connect kicks off a session, the panel polls for a QR code every 2.5s and renders it inline; scan it from your phone (Settings → Linked devices) and the panel flips to…

LLM digestion now required for ingestion — generic ingests fail fast with a clear, actionable error when no model key is configured ("add one in Settings → Models & API keys, then re-run"), instead of silently…

Model-written digests — Feed/connector documents (Notion, Linear, Jira, Zendesk, files, notes, URLs, database schemas) now get LLM-written Summary, Key points and Decisions sections when a BYOK model key is present,…

Hero copy broadened — "code, Slack, Notion, Jira, tickets, docs — anything", plus the skills-compiler promise: knowledge compiled into executable skills agents can run.

New primary "🧠 Skills" tab — a grid of every compiled skill (GET /api/skills) showing the when-to-use description, a subtle confidence meter, last-compiled date and source-document count; click a card to read the full…

New "👥 Workspaces" tab (More → Account) — lists every workspace you own or belong to with personal badge, plan chip and member count, plus a create-team-workspace form (POST /api/workspaces).

New "Integrations" section in Settings — one card per connector group with per-card Save buttons, success/error toasts, and a short setup hint (e.g.

New primary "📥 Feed" tab — the front door for the personal brain: feed anything — notes, PDFs, transcripts, links — and your brain learns it all.

Auto skills compile — every successful ingest (GitHub code, Issues/PRs, Slack, Gmail, Drive, Notion, Linear, Jira, Zendesk, Files, Databases) now automatically enqueues a skills-compile job for the workspace, so the…

Team workspaces shipped — POST /api/workspaces creates a shared brain (owner = caller, plan inherited), GET /api/workspaces lists yours, and owner-only POST/DELETE …/members invite by email or uid / remove members.

6 new connectors — Notion, Linear, Jira, Zendesk, Files & Notes (PDF/docx/md/transcripts/pasted text/URLs), and Databases (Postgres/MySQL schema maps).