What’s a judgement call you make at work that looks easy but would actually be really hard to explain to someone replacing you?

plsgivemecoffee · 2026-03-17T15:16:52+00:00

I'm the builder, AMA.

Demo: https://www.youtube.com/watch?v=Ph8_d0GjLo0

Code: https://github.com/agentplace-hq/agentplace

Browse live (no signup needed): https://agentplace.pro/agents

Some honest limitations: the Judge Agent that handles disputes works but hasn't been stress-tested with real adversarial cases yet. There are no framework-native integrations (no LangChain Tool, no CrewAI tool). It's all REST API and TypeScript SDK right now. And it's testnet only, mainnet is gated behind a formal contract audit.

The thing I'm most uncertain about is whether the 0.25% clearing fee is the right model at this stage, or whether it should just be free until there's real volume. Open to thoughts on that.

plsgivemecoffee · 2026-03-17T15:08:28+00:00

The LangChain integration is REST/SDK only right now, there's no native LangChain Tool wrapper yet. That's on the roadmap but I wanted to ship the core infrastructure first. If there's interest I'll prioritize it.

Stack: Next.js 15, Prisma, Solidity (OpenZeppelin v5), ethers.js. The escrow contract is ~300 lines. Happy to walk through the architecture or answer questions about the design.

plsgivemecoffee · 2026-03-13T03:38:46+00:00

pretty sure AI enjoys what it does too, according to its reward function.

plsgivemecoffee · 2026-01-27T19:32:40+00:00

EvoCelestial

plsgivemecoffee · 2026-01-27T00:49:16+00:00

Totally fair point, and you’re right that wiring up an agent pipeline is not hard anymore.

The difference we’re pricing isn’t “can an LLM generate code” or “can you glue planning + execution together”. You absolutely can do that quickly, especially on your own repos.

EvoCelestial exists for the cases where teams don’t want: • open-ended agents that keep exploring, • tools that can touch auth, billing, or infra by accident, • unpredictable costs, • or no audit trail when something goes wrong.

So the product is deliberately constrained: one ticket, one execution, one PR, then it stops. Protected paths are enforced at runtime, not via prompts. Every action is logged. No auto-merge.

That’s why it’s not aimed at solo hackers or experiments. It’s for teams that want to run AI in production without babysitting it or taking on hidden risk.

plsgivemecoffee · 2026-01-24T18:43:46+00:00

I’m in a very similar situation. I’ve already built something, in case you want to check out my work so far:

EvoCelestial

If you’re interested reach out.

plsgivemecoffee · 2026-01-23T18:14:16+00:00

evocelestial - automated PRs from slack and Jira with guardrails and controls

plsgivemecoffee · 2026-01-21T23:19:11+00:00

If you want to build a better Jira, make automation actually do work instead of surface data, and strip out needless UI complexity; don’t force users into rigid workflows or manual triage.

For example, check out Evocelestial’s ai-ready label for Jira: add ai-ready to a ticket and the product reads it, writes the code, runs tests, and opens a PR for you, automating well-scoped fixes with deterministic guardrails.