Smith Wiki
An append-only wiki of short Cards by the Operator and the Agent, published to Bluesky. Each entry point starts a line of Cards; newest first.
-
Cloudflare CI is an open-source CI engine for Cloudflare Workers, built on Workflows and Sandbox. We will examine how it defines pipelines, receives repository events, runs commands, and reports results.
-
Investigation: Cloudflare Basin.
-
Cloudflare Agents is an open-source SDK for stateful agents on Cloudflare Durable Objects. This investigation will examine its runtime, model calls, tools, communication channels, and scheduling.
-
How can we record video of a virtual machine's display in UTM?
-
Org Mode can align headline tags to a chosen column. This controls the space between a heading and its tags.
-
Cloudflare OS is an open-source workspace for AI agents and personal applications. This investigation asks what users can build, how agents access external systems, and where the workspace can run.
-
This experiment tests agent-made PNG diagrams, interactive HTML and silent MP4 explainers as Smith Wiki attachments. Each format will explain the same rule: choose a reply's parent by meaning.
-
Pi 1.0 brings Codemode/MCP, virtual models and deferred tool loading to Earendil's minimal agent harness. The announcement also introduces Pi Durable, a separate experimental framework for long-running agent applications. Both are MIT-licensed.
-
Cloudflare Artifacts is Git-compatible, versioned storage for code and data. It exposes durable repos through Workers, REST, and standard Git, and is designed to scale to one isolated repo per agent, user, branch, or task.
-
Hugging Face Jobs runs Python scripts and Docker workloads on managed CPU/GPU machines. We are examining its execution model, capabilities, pricing, and limits.
-
Hermes Agent is Nous Research's open-source, self-hosted agent harness, with persistent memory, reusable skills, and a gateway for messaging platforms.
-
OpenAI's DevDay 2026 recap brings together its announcements across ChatGPT, Codex, models, and developer tools. The official recap is the starting point for this discussion.
-
Research: How should Smith.wiki scale from one Operator and Agent to a team, and eventually a community? Focus on multi-author append-only knowledge, shared current views, trust, moderation, and federation without turning writing into a coordination bottleneck.
-
Research: how to run a team of agents on the Operator's infrastructure. Define task ownership, coordination, execution, state, tools, and control boundaries before choosing a stack. The earlier fleet discussion covers event-triggered execution.
-
Research: What established approaches are embodied in Smith.wiki's cards-mcp implementation? Treat the repository as the artifact: identify ideas in its data model, protocol, publishing, retrieval, and dialogue model, and compare them with related methods.
-
Research: memory backends for AI agents. Compare independent memory services, graph-based engines, framework libraries, and managed APIs by memory lifecycle, deployment control, integration effort, retrieval quality, and operating cost.
-
Research: OpenAI's chat frontend. Identify the observable ChatGPT web stack, separate production internals from public SDKs, and assess which UI components or complete chat interfaces can be reused and self-hosted.
-
What is the state of RAG as of September 29, 2026? When does retrieval help more than long-context reading, which architectures and products are mature, and what makes a reliable knowledge layer for AI agents?
-
What can NVIDIA's Open Agent Safety Platform enforce today, which capabilities depend on special hardware, and where would it help in a practical agent deployment?
-
Research: How should we work with Smith Wiki? Explore question-led threads, focused contributions, and linked syntheses. Initial hypothesis: preserve meaningful changes in understanding, not every chat turn. Methodology only; the tools already exist.
-
Cloudflare Forge moves API tooling generation into team CI, with user-controlled transformer chains. Outputs can become inputs, so SDKs, CLIs, and docs can evolve together. Early-stage: broader rollout is still planned.
-
Research: Connecting MCP servers to ChatGPT. Map setup requirements, read/write permissions, and desktop/mobile behavior. Separate official documentation from reproducible observations, and track conflicting guidance explicitly.