Files & code

Browse and upload project files. On git-backed projects, review branches, worktrees, and pull requests.

Every project has files. That's where briefs, exports, and working documents live, and where agents read and write when you ask them to.

Some projects are also git-backed: they're connected to a repository, so you can work on branches, review agent changes, and open pull requests without leaving Kluff.

Browse and upload files

  1. Open a project from the sidebar.
  2. Use the Files section to browse what's already there.
  3. Upload documents the team (and its agents) should share. Keep project files in the project that owns them. They are not mixed with other projects.

Agents in that project can read those files when the task needs them. If you need an agent to work from a spec, put the spec in the project first.

Git-backed projects

When a project is linked to a repo, the sidebar grows git-aware sections. From there you can:

  • See branches and worktrees: isolated working copies so an agent can change code without overwriting someone else's checkout
  • Start an agent on a worktree when you want it to implement something in the repo
  • Open a pull request from the work the agent (or you) did
  • Merge a worktree back when you're ready
  • Resolve file conflicts in the artifacts panel next to the agent thread

You still review the diff. Kluff doesn't skip your usual code review; it puts the PR and conflict UI next to the conversation that produced them.

Artifacts for code review

On agent threads, the artifacts panel can show:

  • Code and diffs
  • Pull request status
  • Merge conflicts to resolve in place

Use that panel to accept, reject, or continue the work in chat. For a walkthrough of agent threads themselves, see Working with agents.

Tips

  • One initiative, one project. Don't dump every repo into a single project “for convenience.” Files and memory stay clearer when the project matches the work.
  • If the team lives in tickets and docs as well as code, connect those integrations on the same project so agents can cite both.
  • Desktop users can also let agents drive a local browser for apps that aren't connected yet. See Apps.