Explore a repository in Kode
So you can read a project’s code without going out to GitHub.
App
Kode
Your projects’ code in its own app: repositories, branches, commits, pull requests and CI, linked to the tasks they belong to. GitHub is its first provider.
Desktop app only
Kode works with your repositories —file trees, branches, pull requests and CI— and that needs more resources than a web tab can give. It is a heavy app: in the desktop app it runs on your computer’s resources.
Download the desktop appWhat you can do
Connect your GitHub account
So the code shows up inside Projekt Republic instead of being hunted down.
Link a repository to a project
So that project shows the commits and pull requests of that repository.
Search code across every repository
So you can find where something is used without knowing which repository it lives in.
How it works
Explore a repository in Kode, in three steps.
- 1
Open Kode: the sidebar lists the repositories you can see, grouped by project.
- 2
Pick one, open folders in the tree and click a file to read it; switch branch or tag at the top.
- 3
Click a line number (with Shift, a range) and copy the link to send it to someone.
What the agent can and cannot do
The Kode agent works with your code, and these are the limits it works within.
- It only works in the folders you pick with the system picker and cannot step outside them: paths are checked, resolved and rejected if they cross a symbolic link.
- Destructive or publishing actions (bulk deletes, git push, deploys, ssh, dropping tables, sudo) always ask for your approval, even in autonomous mode. Kode does not offer a mode that skips permissions.
- Restore points and the chunked diff never touch anything outside the project folder.
- Isolated branches live in a folder of the app and are neither deleted nor merged if they have unsaved changes.
- Terminals start with an allowlisted environment. The agent token belongs to that session, has limited scope and expires; it is never your personal key.
- The .env files, keys and credentials do not enter the local index and are not sent to Kern. What Kern receives, you confirm.
- Whatever leaves your machine first goes through a secrets redactor; if it cannot decide, it does not leave.
- You review and save the diagnostic yourself; it carries no paths, ids, terminal output or tokens, and it is not sent on its own.
- The command history is kept only on your machine and drops lines that look like they carry a key.
- The channel between the app and the terminal engine is local, private to your user and authenticated in both directions.
How to use it
The Kode steps, one by one, are in the manual.
Read the Kode manualWhat is included
- Repository explorer, branches and search across repos
- Branches, commits and pull requests linked to tasks
- Up to 3 repositories on Free; metrics and agents from Pro
What it solves
Code and the tasks that asked for it usually live in different places, and linking them is somebody’s job. Kode brings the projects’ code —repositories, branches, commits and pull requests— next to the tasks, with GitHub as the provider, so you can read it without leaving Projekt Republic.
Who it is for
For teams that run the work in Projekt Republic and the code on GitHub and want each commit and each pull request to hang from its task. Kode is a desktop app: it opens in the Projekt Republic desktop app, not in a web tab, because working with file trees, branches and reviews needs more resources than a tab can give.
What you can do
Connect your GitHub account from the organization settings, with GitHub’s authorization (the recommended way) or by pasting a read token. Link one or several repositories to a project so that project shows its commits and its pull requests.
Browse a repository: open folders in the tree, read a file, switch branch or tag, and copy the link to a line or a range to send to someone. Search code across all repositories at once and filter the results by repository, extension or path.
Link a commit to its task by writing the task key —“PJKT-142”, in upper or lower case— in the commit message or in the pull request title: when you push the branch, the task picks it up on its own. Read a pull request from the task, with its changes and its review comments, and see how long it takes to deliver what gets opened.
What to keep in mind
Projekt Republic only reads from GitHub: it does not open issues, comment on pull requests or push code, and pull requests are read here but answered on GitHub. Disconnecting deletes the stored token and turns off the activity feed in all projects; unlinking a repository removes it from that project and touches nothing inside GitHub.
Frequently asked questions
- Does Projekt Republic write anything to my GitHub?
- No. It only reads your repositories, the activity of the linked ones and the reviews. It does not open issues, comment on pull requests or push code.
- How do I link a commit to a task?
- By writing the task key —the project’s plus its number, for example “PJKT-142”— in the commit message or in the pull request title. It does not matter if it is in lower case. When you push the branch, the task picks it up on its own.
- Where does Kode open?
- In the Projekt Republic desktop app. It works with file trees, branches, pull requests and CI, and that needs more resources than a web tab can give.
- What happens to my token if I disconnect?
- Disconnecting deletes the stored token and turns off the activity feed in all projects. Unlinking a repository from a project only removes it from that project and touches nothing inside GitHub.
Pick your plan
You pay per person per month. See Pricing for what each plan includes before you use Kode.
Free
€0per person per month
Team
€7.95per person per month
Pro
€14.95per person per month