Skip to content

Project Status

Jump to bottom
Kuray Karaaslan edited this page Oct 5, 2026 · 1 revision

Project Status

Tepegoz is pre-release software. It builds, the source is organized around strict quality gates, and a large amount of functionality exists, but the project is not yet a stable released browser.

Current Truth

  • Builds are development artifacts. Installers are currently unsigned and not notarized.
  • There has been no independent security audit.
  • The agentic browser mechanism exists, but the full AI competence program is still measurement-owed.
  • Windows 11 is the primary target. macOS and Linux builds exist, but they are not treated as first-class tested targets yet.
  • The roadmap is source-controlled in phases/; a phase is not closed just because code landed.

Works Today

  • Electron desktop browser shell with tabs, tab strip, omnibox, history, bookmarks, downloads, uploads, find-in-page, settings, context menus, tray behavior, and native browser chrome.
  • Agent panel and runtime with browser tools, model gateway, tool plane, live console, and human approval for risky actions.
  • BYO-key model providers through the model gateway, with cloud-provider keys stored in the OS keychain.
  • Security kernel foundations: policy classification, tool gateway, egress checks, credential vault, event journal, and fail-closed patterns.
  • Per-tab and per-group network routing through user-provided VPN/Tor/SOCKS endpoints.
  • First-party extension system and several internal extensions.
  • English and Turkish localization infrastructure.
  • CI-style quality gates: typecheck, lint, tests, build, dependency boundaries, coverage, e2e, and documentation link checks.

Landed But Not Proven

Some capabilities are implemented or partially implemented but not yet proven by the measurement bar the project requires:

  • AI agent competence phases S0-S12.
  • Safe Browsing service paths without a configured release API key.
  • Notary/proof-of-run, transaction mandates, verifiable policy bundles, recipe compiler decisions, Kamu classifier work, and supply-chain gate decisions.
  • Some future-facing local memory, adapter, sync, and cloud seams.

Not Built Or Not Promised Yet

  • Signed production release channel.
  • Independent security audit.
  • Full Chrome MV3 extension compatibility.
  • Managed cloud tier and E2EE sync.
  • Durable resume across app restarts and full parallel multi-tab DAG execution.
  • Broad integration adapters such as Google or Canva.
  • Inbound MCP server surface.
  • macOS/Linux as primary quality targets.

Sources

  • Product status and roadmap summary: README.md
  • Known gaps: docs/known-issues.md
  • Phase ledger: phases/README.md
  • Security policy: SECURITY.md

Clone this wiki locally