Code Mode

Every Bezel project is linked to a public GitHub repo, chosen when you create the project. The Code tab lets you browse that repo without leaving the app. Useful for checking how a token is actually used, or confirming what's in design-tokens.json before you publish.

The Files tree

The side nav shows the repo's files. design-tokens.json at the repo root is selected automatically each time you open the tab, since it's the file you'll want most often.

Bezel reads the repo at a pinned commit rather than following your branch live. There's a refresh control in the panel header that re-reads the repo at its latest commit and reloads the tree.

The editor is read-only

There's a Read only badge next to the breadcrumbs, and it means exactly what it says. Bezel has read access to your repo and nothing more: no commits, no branches, no pull requests. Nothing you do in the app changes your repository.

To get a file out, use Copy or Download in the panel header.

Commit info

Under the header, a bar shows the last commit that touched the file you have open: who made it, the commit message, the repo, a short SHA, and how long ago. It's scoped per file, so opening a different file updates it.

Asking the AI about a file

The assistant works here too. Open it from the sparkle icon and ask about the file you're viewing. There's no Group/Global scope button in this tab; the assistant is scoped to the code view. It can explain and answer, but it can't write to your repo any more than you can from here.

Getting tokens into your repo

That's the one thing this tab can't do for you. See The design-tokens.json File.