Tegh🛡️

128 posts

Tegh🛡️ banner
Tegh🛡️

Tegh🛡️

@teghsm

Lead AI Engineer @Coinbase | Opinions my own | @uoft alum

Katılım Ocak 2015
103 Takip Edilen248 Takipçiler
Siddharth Kulkarni
Siddharth Kulkarni@siddharthkul·
The GPT 5.6 Sol + Composer 2.5 pairing is really, really good 👏
English
1
0
3
118
Alessandro Rodi
Alessandro Rodi@alrodi·
some of the stuff we shipped in H1 on the card team @coinbase mux: an internal tool that lets you code with any harness or cli that coinbase eng have access to. mux also helps with token spend. (see @brian_armstrong’s recent post on AI spend) for example: - use one opus 4.8 session for planning and route to @cursor_ai composer 2.5 for implementation by spawning new mux sessions on different worktrees rolled it out across the company. read more here -> coinbase.com/blog/coding-ha… card agent on slack, which basically turned into another teammate: - every page or monitor alert is triaged by Card agent and it effectively builds an intelligence to help for future pages - you can ping it for investigations and it retains memory from past interactions - runs our weekly ops reviews - logs every bug, triage, page and monitor alert into linear, which doubles as its memory - if it sees a page or monitor it can fix with code, it uses our in-house software factory (Forge @chintanturakhia) to do it partnered with agentX @kylecesmat @siddharthkul in the platform org(@rwitoff) on a slack multiplexer that lets any team spin up a slack bot trivially with only one slack app. AI advisor bot @teghsm and more! product side: - travel portal: 5% bitcoin back on flights, hotels and cars, no monthly cap. lives in the app, built with rocket travel - secured card: post $500 to $5,000 in usdc as collateral to get approved with no credit history, and you still earn rewards on the deposit - web onboarding - card management improvements - many more improvements and more coming :) feels like we were an army of 100, but we're ~9 ICs in the card team with @vladberteanu. the company makes it easy to partner across orgs and ship together, which is most of why any of this works.
English
4
1
6
688
Tegh🛡️
Tegh🛡️@teghsm·
🫶🚀
Alessandro Rodi@alrodi

some of the stuff we shipped in H1 on the card team @coinbase mux: an internal tool that lets you code with any harness or cli that coinbase eng have access to. mux also helps with token spend. (see @brian_armstrong’s recent post on AI spend) for example: - use one opus 4.8 session for planning and route to @cursor_ai composer 2.5 for implementation by spawning new mux sessions on different worktrees rolled it out across the company. read more here -> coinbase.com/blog/coding-ha… card agent on slack, which basically turned into another teammate: - every page or monitor alert is triaged by Card agent and it effectively builds an intelligence to help for future pages - you can ping it for investigations and it retains memory from past interactions - runs our weekly ops reviews - logs every bug, triage, page and monitor alert into linear, which doubles as its memory - if it sees a page or monitor it can fix with code, it uses our in-house software factory (Forge @chintanturakhia) to do it partnered with agentX @kylecesmat @siddharthkul in the platform org(@rwitoff) on a slack multiplexer that lets any team spin up a slack bot trivially with only one slack app. AI advisor bot @teghsm and more! product side: - travel portal: 5% bitcoin back on flights, hotels and cars, no monthly cap. lives in the app, built with rocket travel - secured card: post $500 to $5,000 in usdc as collateral to get approved with no credit history, and you still earn rewards on the deposit - web onboarding - card management improvements - many more improvements and more coming :) feels like we were an army of 100, but we're ~9 ICs in the card team with @vladberteanu. the company makes it easy to partner across orgs and ship together, which is most of why any of this works.

ART
0
0
1
163
Tegh🛡️
Tegh🛡️@teghsm·
Stretch while your agent babysits your PR running in CI
English
0
0
1
60
Tegh🛡️ retweetledi
Brian Armstrong
Brian Armstrong@brian_armstrong·
Coinbase is one of the most AI-enabled companies in the world, based on all the feedback I hear. We’re in the age of the super builder.
English
205
164
1.6K
178.4K
binji
binji@binji_x·
I genuinely, after a long time, bought more $ETH after reading this. Ethereum is an undoubtedly rare and special technology. ethereum.org/reports/basics…
English
53
122
1.3K
151.2K
mark
mark@markletree·
At @coinbase our AI spend is down nearly half this quarter while token usage keeps climbing. My team built the infrastructure behind it: routing, caching, cheaper defaults, and the spend services that track it. We route everything through our own gateway: a single endpoint and format for dozens of models, with cross-provider failover, redaction, logging, and cost controls all applied before anything reaches a vendor. We started with cheaper defaults and caching. 91% of employees weren't hitting their usage caps. Instead of lowering caps, we set cheaper model defaults to cut spend. Caching took more work to get consistent across every tool and model family. A cache hit needs the prefix to match exactly, so we keep building a long, stable prefix across turns. Each request only pays full rate on the new tokens and reads the rest from cache. Our routing accounts for caching too. The naive approach scores each turn on its own and sends it to whichever model fits, which seems reasonable but would run up spend. The cache is per-model, so switching mid-conversation invalidates it. Our router weighs cache state alongside how hard the task is: a conversation keeps its model while the cache is warm, and the chance to re-route comes only when it goes quiet long enough for the TTL to lapse. Once it does, the router is free again to pick the best model for the task. These improvements happened at the gateway, so they apply across every team and tool. Next we're going deeper on the coding harness, where we have the most signal and flexibility, tuning how subagents and context get managed.
Brian Armstrong@brian_armstrong

How to keep AI spend flat while token usage grows exponentially: Not with friction and spend alerts. With better defaults, routing, and caching. Better Defaults (not Usage Caps) – Engineers can choose any model they want, but defaults matter. We’re experimenting with defaulting to open weight models like GLM 5.2 and Kimi 2.7 through our LLM gateway, while still encouraging engineers to choose the right model for the task. 91% of our employees were never hitting their usage caps, so instead of lowering caps and driving up alerts, we're moving to cheaper defaults. Note that code reviews use a diversity of models, so they can check each other's work. Better Routing – In our custom harnesses, we preprocess prompts and route to the best model for the job, considering cache hits and model pricing. For instance, you may want a frontier model for planning, but not for execution where they can be overkill. Ultimately, humans shouldn't be choosing models - AI can automate this task. Better Caching – Cache misses are the easiest way to drive your cost up. All of our requests are cache aware, so we’re reusing a warm cache wherever possible. For example, our cache hit rate went from 5% → 60% in LibreChat once properly implemented. Keep Context Lean – Start fresh sessions when switching tasks. Scope file context narrowly. Disconnect unused tools. Don't just compact. The goal isn't fewer tokens used, it's fewer tokens wasted. Better Visibility – Our engineers can use as many tokens as they want, from whatever model they want, but we’ve made usage visible – and the more you spend on AI, the more impact we expect. The goal isn't to suppress usage. It's to build the infrastructure that makes exponential growth sustainable. Putting this into practice has cut our AI spend nearly in half, while our token usage continues to grow.

English
102
179
1.8K
580K
Ksenia Moskalenko
Ksenia Moskalenko@kseniam0s·
Is your team using Claude, Cursor, or Codex right now ?
English
25
1
18
3.1K
Jason Zhao
Jason Zhao@byjasonz·
coming home and seeing this view after pulling off a generational lockin in sf where we: > started a new company > shipped 500+ updates for our product > launched an mvp > got our first customers + design partners > graduated from an accelerator > made lifelong friends (from toronto too) > got funded > all in under 5 weeks i dont think you need to be in sf in 2026 to build but damn does it help.
Toronto, Ontario 🇨🇦 English
30
5
157
12.5K
Alessandro Rodi
Alessandro Rodi@alrodi·
it is fun building here. we have the choice to route to frontier models for complex tasks and also have access to powerful ways of routing for example, in one of our internal tools Mux we can choose to plan with opus 4.8 and route the implementation by spawning sessions on different git worktrees using composer 2.5 @cursor_ai CLI
English
1
0
3
369
Brian Armstrong
Brian Armstrong@brian_armstrong·
How to keep AI spend flat while token usage grows exponentially: Not with friction and spend alerts. With better defaults, routing, and caching. Better Defaults (not Usage Caps) – Engineers can choose any model they want, but defaults matter. We’re experimenting with defaulting to open weight models like GLM 5.2 and Kimi 2.7 through our LLM gateway, while still encouraging engineers to choose the right model for the task. 91% of our employees were never hitting their usage caps, so instead of lowering caps and driving up alerts, we're moving to cheaper defaults. Note that code reviews use a diversity of models, so they can check each other's work. Better Routing – In our custom harnesses, we preprocess prompts and route to the best model for the job, considering cache hits and model pricing. For instance, you may want a frontier model for planning, but not for execution where they can be overkill. Ultimately, humans shouldn't be choosing models - AI can automate this task. Better Caching – Cache misses are the easiest way to drive your cost up. All of our requests are cache aware, so we’re reusing a warm cache wherever possible. For example, our cache hit rate went from 5% → 60% in LibreChat once properly implemented. Keep Context Lean – Start fresh sessions when switching tasks. Scope file context narrowly. Disconnect unused tools. Don't just compact. The goal isn't fewer tokens used, it's fewer tokens wasted. Better Visibility – Our engineers can use as many tokens as they want, from whatever model they want, but we’ve made usage visible – and the more you spend on AI, the more impact we expect. The goal isn't to suppress usage. It's to build the infrastructure that makes exponential growth sustainable. Putting this into practice has cut our AI spend nearly in half, while our token usage continues to grow.
Brian Armstrong tweet media
English
476
745
6.2K
4.2M
Tegh🛡️
Tegh🛡️@teghsm·
Cursor composer 2.5 has been effective plan executor here at @coinbase
Brian Armstrong@brian_armstrong

How to keep AI spend flat while token usage grows exponentially: Not with friction and spend alerts. With better defaults, routing, and caching. Better Defaults (not Usage Caps) – Engineers can choose any model they want, but defaults matter. We’re experimenting with defaulting to open weight models like GLM 5.2 and Kimi 2.7 through our LLM gateway, while still encouraging engineers to choose the right model for the task. 91% of our employees were never hitting their usage caps, so instead of lowering caps and driving up alerts, we're moving to cheaper defaults. Note that code reviews use a diversity of models, so they can check each other's work. Better Routing – In our custom harnesses, we preprocess prompts and route to the best model for the job, considering cache hits and model pricing. For instance, you may want a frontier model for planning, but not for execution where they can be overkill. Ultimately, humans shouldn't be choosing models - AI can automate this task. Better Caching – Cache misses are the easiest way to drive your cost up. All of our requests are cache aware, so we’re reusing a warm cache wherever possible. For example, our cache hit rate went from 5% → 60% in LibreChat once properly implemented. Keep Context Lean – Start fresh sessions when switching tasks. Scope file context narrowly. Disconnect unused tools. Don't just compact. The goal isn't fewer tokens used, it's fewer tokens wasted. Better Visibility – Our engineers can use as many tokens as they want, from whatever model they want, but we’ve made usage visible – and the more you spend on AI, the more impact we expect. The goal isn't to suppress usage. It's to build the infrastructure that makes exponential growth sustainable. Putting this into practice has cut our AI spend nearly in half, while our token usage continues to grow.

English
9
10
184
24.7K
Tegh🛡️
Tegh🛡️@teghsm·
@brian_armstrong At @coinbase many of us have also been liking the combo Opus / GPT medium for planning and Sonnet or Cursor Composer 2.5 for execution.
English
1
0
2
214