Commenters debate whether Goldman Sachs restricted Claude Code usage for traders primarily due to security risks like the 'lethal trifecta' or financial losses, versus potential motives related to their Anthropic IPO underwriting and cost management. While many argue that uncontrolled agents on sensitive workstations pose unacceptable operational and data exfiltration risks, others suggest the timing indicates strategic positioning ahead of the IPO or simple budget clawbacks.
496 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4smartcomputer-ai
lightspeed
Rust2026–2026
smartcomputer-ai / lightspeed
lightspeed
Deterministic agent harness for Temporal (in Rust)
2Distinct people
12Mentions
0Explicit recommenders
274GitHub stars
What to know before exploring
What it is
Deterministic agent harness for Temporal (in Rust)
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 AM UTC.
Mentions over time
HN mentions by week12 dated mentions
Observed mentions: 2026-06-14 18:21:16 UTC to 2026-10-01 20:57:12 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jun 8 | 2026-06-08 00:00:00 UTC | 2026-06-15 00:00:00 UTC | 1 | 0 | 1 |
| Jun 15 | 2026-06-15 00:00:00 UTC | 2026-06-22 00:00:00 UTC | 0 | 0 | 0 |
| Jun 22 | 2026-06-22 00:00:00 UTC | 2026-06-29 00:00:00 UTC | 0 | 0 | 0 |
| Jun 29 | 2026-06-29 00:00:00 UTC | 2026-07-06 00:00:00 UTC | 2 | 0 | 2 |
| Jul 6 | 2026-07-06 00:00:00 UTC | 2026-07-13 00:00:00 UTC | 1 | 0 | 1 |
| Jul 13 | 2026-07-13 00:00:00 UTC | 2026-07-20 00:00:00 UTC | 1 | 0 | 1 |
| Jul 20 | 2026-07-20 00:00:00 UTC | 2026-07-27 00:00:00 UTC | 0 | 0 | 0 |
| Jul 27 | 2026-07-27 00:00:00 UTC | 2026-08-03 00:00:00 UTC | 0 | 0 | 0 |
| Aug 3 | 2026-08-03 00:00:00 UTC | 2026-08-10 00:00:00 UTC | 1 | 0 | 1 |
| Aug 10 | 2026-08-10 00:00:00 UTC | 2026-08-17 00:00:00 UTC | 1 | 0 | 1 |
| Aug 17 | 2026-08-17 00:00:00 UTC | 2026-08-24 00:00:00 UTC | 0 | 0 | 0 |
| Aug 24 | 2026-08-24 00:00:00 UTC | 2026-08-31 00:00:00 UTC | 0 | 0 | 0 |
| Aug 31 | 2026-08-31 00:00:00 UTC | 2026-09-07 00:00:00 UTC | 0 | 0 | 0 |
| Sep 7 | 2026-09-07 00:00:00 UTC | 2026-09-14 00:00:00 UTC | 1 | 0 | 1 |
| Sep 14 | 2026-09-14 00:00:00 UTC | 2026-09-21 00:00:00 UTC | 0 | 0 | 0 |
| Sep 21 | 2026-09-21 00:00:00 UTC | 2026-09-28 00:00:00 UTC | 3 | 1 | 2 |
| Sep 28 | 2026-09-28 00:00:00 UTC | 2026-10-05 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
1 sourcesLUlukebuehler·Jun 14, 2026
Agent harness for durable workflows, starting with Temporal.
Most agents for durable workflows feel like toy examples. There is no "Codex" or "Claude Code" for, say, Temporal. So I'm building full-featured agent for these runtimes. Why? Because it makes long-running agents easier to operate and scale. Currently, all frontier harnesses need to run inside a guest OS and need a dedicated process, this is quite challenging to orchestrate and maintain.
To make it work, I had to figure out what part to run as deterministic workflow code, and what part to run as I/O or side effects (aka activities). I'm using a CAS for most of the payloads to maintain a lightweight footprint in the workflow code.
Currently supporting skills, MCP, prompts, a virtual file systems, and soon sandboxes.
https://github.com/smartcomputer-ai/lightspeed
In Ask HN: What are you working on? (June 2026)