Team context, from your own systems
Repositories, documentation and tasks become working sources for an assistant. Configure connections and tools in a shared workspace, then select the access each use case needs.
Your model subscriptions and plans
Agents run using accounts connected in RemoteHangar with subscriptions or coding/token plans. Buying a separate pay-as-you-go model-provider API key is not the product’s primary onboarding path.
Available models, limits and terms depend on the selected account and plan. Requests and necessary context go to the chosen model provider; the workspace, configuration and history remain on company infrastructure.
Tracker, Git-host and RemoteHangar API tokens serve a different purpose: authorizing access to those systems. They do not replace the model subscription.
Tasks and your delivery process
Select work for the agent and add it to the queue as text or a ticket link. A connected tracker provides tools to read context, prepare issues and report results.
The queue executes added requests in sequence. Your team decides how tasks enter it and which changes the assistant may make in the tracker.
| System | Why connect it | What to agree |
|---|---|---|
| YouTrack | Read, search and create issues, comments and status changes | Projects and user permissions |
| Jira | Issue context and delivery updates within your existing process | We validate your Cloud, Server or Data Center connection setup during the pilot |
| Notion | Pages, databases and related tasks | The administrator’s integration and user access |
| Linear | Tasks for product and engineering teams | We agree on the connection and required operations in the pilot |
Repositories and changes
GitHub, GitLab and Gitea give agents code and change context. Connect a working repository and any reference projects needed to understand the system.
An agent reads code, prepares changes and runs available checks. Your team defines branches, the review handover and permitted operations.
Personal SSH keys and HTTPS Git-host tokens can be configured when the administrator enables credential storage. Repository access is agreed separately from model access.
Knowledge, memory and tools
MCP is the protocol agents use to call tools. One assistant can receive knowledge search, another tracker tools, and another the tools needed for development.
Outline is a company knowledge base for instructions, architecture and team decisions. Its connection enables document search and work; source links help your team verify an answer.
Graphiti retains related facts and their history: which service belongs to a project, which team owns it and what decisions were made. It requires a configured Graphiti server.
| Source or tool | Value in a working use case | Connection |
|---|---|---|
| Outline | Search and work with team documentation | An administrator-configured OAuth application and user connection |
| Graphiti | Linked facts, dependencies and decision history | Your Graphiti server |
| Confluence | Documentation and instructions in an existing knowledge base | Cloud or Server / Data Center: we validate configuration and required operations during the pilot |
| Code search | Navigate working and reference repositories | Tools on the RemoteHangar server |
| Browser tools | Check interfaces and work with web pages | A configured browser environment |
| Remote servers | File and shell tools on an enrolled host | The RemoteHangar connector and agreed permissions |
| Another MCP server | Access to your service through its tools | Endpoint, authentication and validation of required operations |
Shared skills and plugins
A skill explains how to do a kind of work: write tests, review code or investigate failures. Plugins can combine skills, commands, subagents, hooks and MCP servers.
Administrators manage them in the web console. Useful instructions and tools can be reused across team workflows without rebuilding a setup on every laptop.
- Built-in skills: 58
- Plugins in the catalog: 19
- Plugin marketplaces: 7
Prepared bundles for a kind of work
A bundle combines skills, plugins and MCP tools for development, testing, review or operations. Users select suitable bundles for an agent’s workspace.
RemoteHangar includes 22 baseline bundles. Administrators can prepare their own combinations and instructions. Together with agents and connections, they form the team’s shared harness.
Assistants in your own applications
The same prepared agents are available to an internal portal, help desk or another company product through the RemoteHangar API. The application backend opens a session, sends questions and receives streamed answers and events.
Give the application a separate RemoteHangar token with the API operations it needs. Keep it on the backend, not in the employee’s browser. Architecture and request examples are on the API page.
Connect sources for one useful process
Tell us about your repository, knowledge base and tracker. We agree on the necessary operations, validate your configuration and scope the required connections into the pilot.
Discuss a pilot