WeSearch

Show HN: Podiom – Persistent project context, goals and scheduling for AI agents

·3 min read · 0 reactions · 0 comments · 4 views
Show HN: Podiom – Persistent project context, goals and scheduling for AI agents
TL;DR · WeSearch summary

Podiom A thin orchestration layer for local LLM agents (Claude Code and OpenAI Codex). Podiom shells out to the native claude and codex CLIs and leans on their MCP, tools, and skills, while owning its own durable truth: named agents, durable chat sessions, a canonical history that replays onto a fresh backing CLI session on any profile/provider switch, an embedded scheduler, and a shared project ledger. It ships as a single Go binary with an embedded Svelte web UI.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 4,032 of its stories.

Original article
GitHub
Read full at GitHub →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGitHub
Canonical URLhttps://github.com/Podiom/Podiom
Publication timeFri, 07 Aug 2026 21:24:57 +0000
Retrieval time2026-08-07T21:35:41.962Z
Last seen2026-08-07T21:35:41.962Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterEwGxC8t3z8HW · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Podiom A thin orchestration layer for local LLM agents (Claude Code and OpenAI Codex). Podiom shells out to the native claude and codex CLIs and leans on their MCP, tools, and skills, while owning its own durable truth: named agents, durable chat sessions, a canonical history that replays onto a fresh backing CLI session on any profile/provider switch, an embedded scheduler, and a shared project ledger. It ships as a single Go binary with an embedded Svelte web UI. Why Podiom? Managing multiple local agents is easy to start and hard to keep coherent. Podiom stays thin on purpose: Durable sessions that survive provider and profile changes. A shared project ledger so work does not get lost between runs. Built-in scheduling for recurring work and follow-ups.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub