jnakano89
Joined 16 years ago
Karma
50
Submissions
31
Member since
May 17
Building <artifacta.io>
View on Hacker NewsRecent submissions
Comment · 3 months ago
Seems like they cut the tiers(GPT-5.6 Luna) where GLM and Kimi compete and still held margin for their frontier models
Comment · 3 months ago
"Ads were a last resort" is actually the most transparent financial disclosure OpenAI has ever made.
Comment · 3 months ago
Not as sophisticated as yours I’m afraid, the companies are clustered by category/industry. The layout has some semantic structure and proximity tries to reflect shared categories.
The crate co-use looks interesting, and building it without agent swarms still counts :)
Comment · 3 months ago
Don’t tempt me. YC Universe V2: No Man’s SaaS mine ARR, battle churn, and avoid getting acquihired by the black holes.
Comment · 3 months ago
Basically two prompts: 1) One for agent swarms to collect, cross-check, and structure the data. 2) Another to turn the dataset into the interactive galaxy.
I agree though, the autonomous build process is more interesting than the artifact.
Comment · 3 months ago
I built this mainly as a qualitative test of Kimi’s frontend capabilities given the strong frontend score on ARENA. Broadly, I’d say it’s quite capable, it even did a ton of validating, took screenshots, identified its own issues, and iterated repeatedly. The entire session was far more rigorous than I expected
Comment · 3 months ago
^ Builder here, I used Kimi K3 and agent swarms to turn YC companies into an interactive galaxy. Every star is a startup you can click and explore.
Comment · 3 months ago
Working on Artifacta, a place for agents to store artifacts they create and share/publish them. Now supports hosted MCP along with a CLI
[1]: https://artifacta.io
Comment · 4 months ago
Working on Artifacta (https://docs.artifacta.io/introduction)- durable artifact storage for the files AI agents produce across sessions.
The problem I kept hitting with agent workflows (especially cloud hosted agents) was that the artifacts they produced became really awkward to handle across different cloud sessions.
So I built Artifacta as the boring storage layer underneath. Agents store and retrieve artifacts via CLI, REST API, Python SDK, or an MCP server. Artifacts are grouped by session/agent metadata, deduped on identical content, and safe to retry (idempotency keys), making it easy to handle artifacts across different sessions.
Would love any feedback for those who run mutli-agent orchestration or if you deal with artifacts across different agents.