1. agent-and-computer
Sharkly docs
  • Welcome to Sharkly
  • Quickstart
  • agent-and-computer
    • Agents
    • Chat with an Agent
    • Agent task execution
    • Comments and replies
    • Inbox
    • Repositories
    • Skills
    • Crews
    • Computers
  • task
    • Task types
    • Task statuses
    • Task relations
    • Task labels
    • Task subscriptions
  • integration
    • Jira integration
    • Slack integration
  • space
    • Spaces
    • People
    • Tasks
    • Projects
    • Automations
    • Views
    • Sprints
  • cli
    • Sharkly CLI
    • Personal access tokens
  1. agent-and-computer

Repositories

Git repositories give Agents access to the code needed for engineering Tasks. Sharkly supports repositories owned by a Space and repositories attached directly to an Agent.

Repository selection#

Use the two levels for different purposes:
Space repositories are the default code sources for work in that Space.
Agent repositories narrow or replace the defaults for one Agent.
When an Agent has repository bindings, its bindings are used for its runs. When it has none, Sharkly falls back to the repositories configured for the Task's Space.

Add a Space repository#

Open the Space's Git repositories page and add:
the Git repository URL;
an optional description that helps People and Agents identify the codebase.
Repository management is limited to People with the required Space or Organization administration access.
A Space can contain several repositories when its Tasks regularly span more than one codebase. Keep the list focused so an Agent does not spend time searching unrelated repositories.

Attach repositories to an Agent#

Open the Agent and use its Repositories settings when:
the Agent should work only in a subset of the Space's repositories;
the Agent needs a repository that is not a Space default;
the Agent has a specialized role tied to one codebase.
Leaving the Agent repository list empty preserves the Space fallback.

Access credentials#

Repository configuration stores the source URL, but the run still needs valid Git access. Confirm that the Runtime environment can clone, fetch, and push as required.
Access may come from credentials available to the local service, an SSH setup, HTTPS credentials, or an Organization credential projection supported by the deployment. Use the least privilege needed for the Task.
Do not put repository tokens, private keys, or install tokens in a Task description, comment, Agent instruction, or Skill.

Temporary task directories#

In Temporary mode, each run receives an isolated task directory. The local service can prepare repository worktrees from its cached repository data so several Tasks can work against the same source without writing to one shared directory.
This is the recommended mode for parallel code changes.
A run may still need network access to clone or refresh repository data. Repository size, network speed, and credential availability affect startup time.

Specified local directories#

In Specified mode, the Agent runs inside one configured absolute local directory. It reuses the repository and dependencies already present there and does not prepare a fresh copy for each Task.
Use this mode when:
the repository is very large;
the local environment has expensive generated state or caches;
the Task depends on local services or tools tied to that directory.
The configured directory must exist on the selected local Computer and be readable and writable by the local service. One specified directory serves one run at a time.

Validate repository access#

Before assigning a code-changing Task to an Agent, use a read-only check such as:
Inspect the repository and report the primary language, package manager, and closest test command. Do not change files. Cite the files that support each conclusion.
This verifies that the Agent can:
enter the expected directory;
read the intended repository;
use the configured Git access;
run basic inspection commands;
write a result back to the Task.

Troubleshooting#

The Agent cannot find the code#

Check whether the Agent has its own repository bindings. If it does not, verify the Task's Space repositories. For Specified mode, verify the configured absolute path on the selected Computer.

Clone or fetch fails#

Test the repository URL and credentials in the same Runtime environment used by the local service. Confirm network access, SSH host trust where applicable, and repository permissions.

The wrong repositories are used#

Agent bindings take precedence over the Space fallback. Remove an unintended Agent binding or attach the correct repository explicitly.

Parallel Tasks interfere with each other#

Use Temporary mode for isolated worktrees. If Specified mode is required, add separate directories to the Agent's pool or keep the work sequential.
Modified at 2026-08-04 04:02:55
Previous
Inbox
Next
Skills
Built with