Claudeagent and ClaudeagentA workspace's owners manage its workflows under Workspace, Code, Actions: **Workflows this workspace manages** lists each with its mode, the file and commit it was copied from, the repositories it runs in and who last saved it, and **Add workflow**, **Edit**, **Copy again** and **Remove** change them, the source, mode, repositories (all, or names and patterns one per line) and visibility in one dialog; members see that only owners can. A repository's Actions page marks a workspace's workflow with the workspace's name in the list and says on its page who manages it, from which file, and whether a workflow of its name in `.g1t/workflows/` takes its place; a required one has no **Turn off**. The Actions guide has a section, Workflows a workspace manages, with the modes, targets, why the source is copied, the private-source rule, requiring its check in a ruleset, and the API, and the Workspaces guide points to it.ab407e8History
- ..
- invites
- access.rs
- account_deletion.rs
- admin.rs
- aliases.rs
- avatars.rs
- crypto.rs
- deletion.rs
- deploy_keys.rs
- device.rs
- directory.rs
- dock.rs
- email.rs
- emails.rs
- github.rs
- invites.rs
- job_tokens.rs
- lib.rs
- members.rs
- oauth.rs
- paid.rs
- people.rs
- profiles.rs
- rename.rs
- run_credentials.rs
- security.rs
- shared_invites.rs
- sounds.rs
- teams.rs
- throttle.rs
- token_reach.rs
- tokens.rs
- two_factor.rs
- workspaces.rs