Any thoughts on equipping a cloud agent like <Char...
# how-do-i
t
Any thoughts on equipping a cloud agent like Charlie, who occupies an actual seat on our GH repo, with Graphite? Is there a good/recommended way to ensure that the agent sets up + auths in Graphite? (Does it even need auth?) I need my top agents making stacks graphite fractal
✅ 1
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
t
Also acknowledged that the Cursor Agent now exists in Graphite, but not relevant to me; 1. I don't use Cursor or have a Cursor Pro account 2. The agents are invoked to create these PRs elsewhere (eg slack) 3. I'm already using agents that i'm happy enough with
p
I don't know if we have recommendations on-hand for this, but I'm checking with the team.
🫡 1
p
It sounds like if you want to use an agent account you: • Give them a GitHub seat • Then log that account into Graphite and that should just work after giving it the Graphite token
t
hmm, they don't have a persistent state. but i can provide it as an env var for them... then i suppose i'd have to force it to run
gt auth --token THAT_ENV_VAR
i'll toy around.
thanks connor and co 🫡
p
lemme know how it goes in case this comes up again 😅
t
No luck on this so far - would love a "service token" or "agent auth" support of some kind. My friend works at Charlie, so I might be able to get him to bypass it manually somehow for me for now... thinking
👀 1
given that i suspect we'll move toward fleets of cloud agents... i'm not sure how graphite plays a role in the future of our development workflows without the ability to utilize Graphite via cloud agents (and without having to lock ourselves into Cursor cloud agents) our team is moving increasingly toward agentic-driven development. currently trialing agent workflows driven by Linear. i love working with graphite and want agents stacking PRs — it's such a natural fit. but agents can't stack with Graphite right now unless we do it locally, and that's increasingly a problem. really curious if this is workflows that Graphite wants to enable or if the goal is ultimately to convert folks to Cursor cloud agents. EDIT: and to be clear, Charlie isn't the cloud agent we're set on; i view that as a short-term bridge toward cloud-based agentic workflows right now. i imagine we'll move toward more stand-alone agents/environemnts vs an 'product agent' like that.
p
I don't know that I can really speak to this authoritatively right now, but I think it's safe to assume we're moving in the direction of wanting folks to use Cursor's products from Graphite 😅
👍 2
🫡 1
t
thanks connor — i appreciate the directional feeling. we're still a ways out from any sort of "pure cloud agent" development story, and we'll certainly consider using Cursor cloud products, though i am skeptical of the lock-in that forces us into right now. when the graphite team is ready to share a more formal roadmap/direction, i hope that it can make room for folks like us in that vision 🙂
💘 1
heya, friends. i'm trying cursor cloud agents this week and just want to confirm: > can cursor cloud agents stack in graphite? Docs don't mention stacking: ❓ https://graphite.com/docs/agents EDIT: ah is the trick that cursor cloud agent would need MY graphite auth token so it could act as me?
p
Not natively, but we're working on it!
❗ 1
👀 1
t
lmk if i can beta test when ready enough 🥹
🫡 1
Heya Connor / other graphite friends — I've been playing with Cursor cloud agent runs. Curious if maybe using the "My secrets" at the bottom of settings (
My Settings
tab, NOT team settings) to provision with my local graphite token could enable stacking. Have yall tried this? Any cautions against it?
p
I haven't tried this personally, but it sounds like folks internally are doing this and it seems to be working!
👀 1
t
The "My secrets" approach in Cursor cloud with my personal gt token has been working for me. That said, still really looking forward to a more first-class integration as new cursor agents (and cursor's web ui) get very confused about Graphite stacks still.