Arbtr Code Tools

Integrations

Let Arbtr analyze your codebase, search PRs, and explore repositories to give context-aware answers.

Arbtr's AI assistant understands your decisions and can connect to your codebase for context-aware analysis.

What Arbtr Can Do

Code Search

Search for patterns, function names, or specific code across your repositories. Arbtr can find implementations related to your architectural decisions.

PR/MR Search

Search through pull requests and merge requests to find related changes, discussions, and implementation history.

Repository Browsing

Browse directory structures and understand how your codebase is organized. Useful for understanding where decisions apply.

File Reading

Read specific files to analyze implementations, configuration, or documentation that's relevant to architectural decisions.

Setup Requirements

Arbtr's code tools require a connected Git provider. You can use Read-Only mode—no write access is needed for code analysis.

Quick Setup

Go to Team Settings → Integrations
Connect your Git provider (GitHub, GitLab, or Bitbucket)
Use Read-Only mode for minimal permissions
Arbtr will automatically use the connected provider

Multiple providers? If you have multiple Git providers configured, Arbtr uses the one set as default in your integration settings.

Using Arbtr with Code Context

When chatting with Arbtr, you can ask questions that reference your codebase. Arbtr will use the available tools to find relevant information.

Example questions:

→"How is authentication currently implemented in our codebase?"
→"Show me recent PRs related to the payment system."
→"What files would be affected if we changed our database from Postgres to MySQL?"
→"Find all usages of the deprecated API endpoint."

How It Works

• Arbtr receives your question and determines which tools to use
• It searches your repository using the connected Git provider
• Results are analyzed and summarized in the context of your decisions
• You get an answer that connects code reality to architectural intent

Decisions + Code = Context

Arbtr's real power comes from combining your documented decisions with actual code. This helps you understand:

Implementation Status

"Is this decision actually implemented?" Arbtr can search for patterns that indicate whether a decision has been put into practice.

Drift Detection

"Are we following our own decisions?" Find code that might violate architectural decisions you've made.

Impact Analysis

"What would this decision affect?" Before making a decision, understand what code would need to change.

Historical Context

"Why was it built this way?" Search PRs and code history to understand the reasoning behind implementations.

Privacy & Security

Read-Only Access

Arbtr's code tools only need read access to your repositories. No modifications are made to your code or PRs.

On-Demand Queries

Code is only fetched when you ask Arbtr a question that requires it. We don't continuously index or store your codebase.

Same Provider Permissions

Arbtr can only access repositories that your Git integration has access to. If you limit the GitHub App to specific repos, Arbtr respects those limits.

Arbtr uses the same Git integration you configure for publishing. If you want to enable code analysis but not publishing, use Read-Only mode.

Troubleshooting

'No Git provider connected'

Arbtr needs a Git integration to search code. Go to Team Settings → Integrations and connect at least one provider.

Arbtr can't find files

Make sure the repository configured in your integration settings is correct. Arbtr searches the repository specified in your default Git provider.

Switching repositories

To have Arbtr search a different repository, update your Git integration settings or set a different provider as default.

Bitbucket Setup

Back to

All Integrations

Command Palette