# feat\(gitcafe\): call GitCafe's API directly with a cafe-sourced token · gitcafe/t3code

[View on GitCafe](https://git.cafe/gitcafe/t3code/commit/70e4ec10570cd3e266798e2329720805847cfc80)

Repository: [gitcafe/t3code](https://git.cafe/gitcafe/t3code)

Visibility: public

Requested revision: 70e4ec10570cd3e266798e2329720805847cfc80

Requested commit: 70e4ec10570cd3e266798e2329720805847cfc80

Commit: 70e4ec10570cd3e266798e2329720805847cfc80

Tree: 0b99239d7fffb15d4908b785b53cb1a2a8659faa

Author: versecafe

Committer: versecafe

## Message

```
feat(gitcafe): call GitCafe's API directly with a cafe-sourced token

GitCafeCredentials resolves a token the way GitHubCredentials does for gh:
CAFE_TOKEN for the host cafe targets, otherwise cafe's own Git credential
helper, cached and dropped on a 401. REST calls and private attachment
downloads now go over HTTP instead of spawning `cafe api`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [bc9e181450539d5ca03c250359a757010ffa6e56](https://git.cafe/gitcafe/t3code/commit/bc9e181450539d5ca03c250359a757010ffa6e56?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/t3code/tree/70e4ec10570cd3e266798e2329720805847cfc80?format=markdown)