Loa/Workspace
English
  • English
  • 简体中文
  • 日本語
  • Español

What it does

Twenty-four tools, one repository.

An agent reaches the repository only through these. Each one does one thing, says what it did, and answers in the same shape every time. The two that reach a remote, git_fetch and git_push, are there only when you set one up.

The tools

Look7

  • workspaceWhat this workspace is, and what a call may do.

    Its root, its repositories, its secrets by name and never by value, and how a command is confined.

  • readA text file, as numbered lines.

    In place of cat, head and tail.

  • statWhat is at a path, without reading it.
  • listWhat is under a directory, to a depth.

    In place of ls and tree.

  • globFiles by the shape of their path.
  • grepText files that match a regular expression.

    In place of grep and rg.

  • outlineThe definitions in a file or under a directory.

Change6

  • editReplaces text in a file.
  • writeCreates a file, or overwrites one.
  • patchChanges several files in one call that lands whole or not at all.
  • changeWrites, deletes and moves files, each held to its version.
  • file_snapshotsThe snapshots kept of the files, newest first.
  • restore_filesPuts the files back as they were before a command.

    Files the snapshot holds are written back, and files made since are removed.

Run5

  • shellRuns one command, confined to the workspace.

    Each call stands alone, and nothing is interactive. Git there can read the repository but not change it: commits, fetches and pushes go through the git tools.

  • process_listThe processes running, newest first, with the ports they listen on.
  • process_outputWhat a process printed, running or ended.
  • process_waitWaits for a process to exit, listen or print, without polling.
  • process_killEnds a process and everything it started.

Git6

  • git_statusWhere the repository stands.
  • git_diffWhat changed, as a unified diff.
  • git_logThe commits on the branch, newest first.
  • git_commitCommits to the branch the tree is on.

    The commit carries the workspace's author, whatever git configuration the repository has.

  • git_fetchFetches the remote's branches, and moves nothing of yours.
  • git_pushPushes this branch to the branch of the same name.

    To the one remote the owner named, with a credential the server holds and the model never sees. No other branch, no tag, no delete.

What it does not do

  • It holds no agent and no model. Bring your own, like Claude Code, or any MCP client.
  • It works in one directory and pushes to one remote, both named by you.
  • A push never forces, and makes no tag and no delete.
  • It won't start where it can't confine commands, unless you turn the sandbox off with sandbox: none. Then it refuses a git token.
  • On a Mac, it runs in your login session and stops when you log out.
  • Experimental. It also runs in Amazon Bedrock AgentCore Runtime, one microVM per session, with the same sandbox inside it. The container recipe (arm64) is in deploy/agentcore. For now it sets up one repository when the container starts; setting up a session from its first call isn't built yet.