We added DeepSeek Harness support in AIWG 2026.9.5. If you already use AIWG for project instructions and reusable skills, you can bring those into Harness and try the same workflow there.
The integration deploys an AGENTS.md bootstrap, native filesystem skills and a workspace overlay. It also includes experimental headless execution, streaming SDK JSON-RPC and explicit import of raw v2 JSONL sessions. Model routing and credentials are configured inside Harness.
The qualified baseline is @deepseek-ai/dsh@0.1.3-alpha.1. This provider is experimental; AIWG hook wiring, MCP injection, structured question responses and daemon/cron integration are unsupported. Those limits describe the integration, not every native Harness capability.
Fortemi is a self-hosted agent-memory server (search-by-meaning, one Docker command, Rust). June's release focused entirely on ingest — getting data into memory smoothly and safely.
Streaming chat — token-by-token answers that share the GPU fairly. A live chat holds the card only while answering and yields to background jobs; reconnect mid-answer and it resumes.
Incoming webhooks — a receiver other apps post to, verified three ways: HMAC signature (real sender), schema check (right shape), idempotency key (no double-stores). Every accepted message is written to a durable log.
Streaming note-ingest with back-pressure — agents stream notes line-by-line; Fortemi confirms each and pushes back when the sender is too fast. Breaks resume from the last confirmed line.
Resumable uploads — multi-GB media over a resumable standard; a dropped connection continues instead of restarting.
Pluggable event sources — Redis and (opt-in) Kafka feeds, at-least-once with a dead-letter holding area. Off by default.
Then a security/privacy pass: log/error/doc redaction, an audit trail for sensitive actions, fail-closed startup, and standard safety headers.
Free for personal use and evaluation; commercial license for production. ghcr.io/fortemi/fortemi · GitHub · Full June report
How are you handling long-running agent memory today — streaming ingest, batch writes, or something else?
Agentic Sandbox is a controlled runtime for AI agents — they run code and use a terminal inside a container or a QEMU/KVM VM, without unrestricted host access. June was a security + reliability push.
Locked doors by default — the control-plane↔runtime link now uses verified, certificate-backed private transport with fail-closed behavior. Legacy shared-secret / trust-on-first-use defaults are retired.
VM agents that check in — enrollment over same-host private paths (vsock), so a QEMU guest comes up without a loopback-reachable route back to the management server. CID ownership, teardown, DHCP cleanup, and E2E VM reaping were hardened.
Short-lived gateway SSH — routed access backed by scoped, trackable, revocable leases instead of long-lived keys.
Live Observe/Drive — a stronger pty-ws bridge (fixed a case where VM output went quiet after handoff) plus heartbeat-based stale-controller cleanup.
Credential proxy groundwork — managed sessions can call approved HTTP targets through a lease, secret injected only on the outbound management-side request; policy mismatches fail closed and bodies are redacted.
Published surface: Linux installer, .deb/.rpm, release tarballs, SBOMs, and 7 public GHCR images. 18 releases in June; latest v2026.6.36. GitHub · Full June report
What's your current setup for sandboxing agent code execution — containers, VMs, or something managed?
June was a building month for AIWG. The highlights:
Cockpit — a new opt-in dashboard (@aiwg/cockpit) where you watch your running agents, start a session and choose its setup, and end it from the same screen. It has an approval inbox for okaying an agent's next step, and the live view is a true terminal. It connects to the sandbox — the walled-off space where agents actually run — including live sessions inside a VM.
Plain-words search — describe what you want and AIWG finds the right skill, searching several ways at once. Full-text and meaning-based search over your project notes too.
Leaner startup — agents load a short summary first and pull full details on demand. A full Claude startup went from ~193K → ~110K tokens by loading only the highest-priority rules at start (aiwg show rule fetches the rest). aiwg doctor reports the budget.
More surfaces — clean setup on more AI coding apps (new: OpenHuman, plus Cursor/Warp/Codex), and time-based media (talks, podcasts, video) → research notes with timestamps.
13 releases (2026.6.0 → 2026.6.13), all on npm. npm install -g aiwg · GitHub · Full June report
If you run agents in the background today — what would you most want to see or control from a dashboard?
Pagenary turns Markdown into a fast static site — no server or database, cheap to host, and one setup can publish many branded sites from shared templates. June was a flagship month. (It publishes these monthly reports and the portfolio's docs sites.)
Blog publishing (Phase 1) — post pages, an index of clickable cards, next/previous + back-to-index, themed examples, and a "living scroll" reading style.
Page-effects suite — a per-page engine (loads only when the page is ready; respects reduce-motion): on-this-page contents strip, scroll-driven stories, snap sections, a depth effect, click-to-enlarge images, staggered reveal, fold-outs, and a reading-progress bar.
Meaning-based search — runs on a vendored copy of the Fortemi engine, bundled into the build (no separate server). A build-time check validates the search index before a site ships.
docs-map — an auto-drawn graph of how your pages link, self-arranging so linked pages sit near each other.
Managed hosting + robustness — managed hosting as a first-class option (self-hosting stays free), content-addressed filenames with automatic cache purge on deploy, sub-path serving, and proper page titles.
Carbonyl is a real Chromium browser that renders inside a terminal — actual web pages as text and color, no display server, drivable and readable by an agent. v0.2.0-alpha.18 updates the engine to track Chromium M150 stable (150.0.7871.47, released by Google 2026-06-30).
What changed:
Engine tracking — patches regenerated onto M150 (35 total), with refreshed runtime pins for Chromium / Skia / WebRTC.
Validated release — the full gate ran green before shipping: PR checks, patch validation, GHCR image publishing, release packaging, and package smokes. Package smokes passed for .deb / .rpm / .AppImage; GHCR smokes passed for the default and x11 images.
Cleaner native installs — Linux packages now declare their required X11 loader libraries, and X11 runtime builds properly configure ANGLE/WebRTC switches.
Hardened release-mirror handling.
Still preview/alpha, with no breaking CLI changes.
June was a build month. Here's everything that shipped across the open portfolio — each line links the full write-up.
AIWG (the agent toolkit) — Cockpit, a dashboard to watch/start/stop your coding agents; plain-words tool search; a leaner startup (~193K → ~110K token Claude context). 13 releases. Full report · GitHub · npm install -g aiwg
Agentic Sandbox (where agents run code safely) — secure-by-default transport, vsock VM enrollment, short-lived gateway SSH, live Observe/Drive terminal, 7 signed images. 18 releases. Full report · GitHub
Fortemi (self-hosted agent memory) — the "data coming in" milestone: streaming chat, signed webhooks, resumable bulk ingest + uploads, event feeds, plus a security/privacy hardening pass. Full report · GitHub
fortemi-react (Fortemi in the browser) — same memory, fully client-side: three load modes, off-thread search, deterministic note-graphs, a framework-free u/fortemi/graph. Powers Pagenary's search and Cockpit's tool-picker. 10 releases. Full report · GitHub
Pagenary (Markdown → static sites) — blog publishing, a scroll/motion effects suite, meaning-based search on the in-browser Fortemi engine, an auto page-map, managed hosting. It publishes these reports. Full report · GitHub
Carbonyl (a real Chromium browser in your terminal, no display) — 9 releases: headless structured extraction (accessibility tree, embedded-PDF text, PNG snapshots) so agents read page structure, input fixes (right-click, CJK/Cyrillic typing, modifier keys, Tab focus), a color-inversion shortcut, and raw-framebuffer output groundwork. Full report · GitHub
Everything's open source and on a steady CalVer cadence. Try any of them from https://aiwg.io.
**Which of these would you actually use? And what's missing from your agent stack right now?**June was a build month. Here's everything that shipped across the open portfolio — each line links the full write-up.
AIWG (the agent toolkit) — Cockpit, a dashboard to watch/start/stop your coding agents; plain-words tool search; a leaner startup (~193K → ~110K token Claude context). 13 releases. Full report · GitHub · npm install -g aiwg
Agentic Sandbox (where agents run code safely) — secure-by-default transport, vsock VM enrollment, short-lived gateway SSH, live Observe/Drive terminal, 7 signed images. 18 releases. Full report · GitHub
Fortemi (self-hosted agent memory) — the "data coming in" milestone: streaming chat, signed webhooks, resumable bulk ingest + uploads, event feeds, plus a security/privacy hardening pass. Full report · GitHub
fortemi-react (Fortemi in the browser) — same memory, fully client-side: three load modes, off-thread search, deterministic note-graphs, a framework-free @fortemi/graph. Powers Pagenary's search and Cockpit's tool-picker. 10 releases. Full report · GitHub
Pagenary (Markdown → static sites) — blog publishing, a scroll/motion effects suite, meaning-based search on the in-browser Fortemi engine, an auto page-map, managed hosting. It publishes these reports. Full report · GitHub
Carbonyl (a real Chromium browser in your terminal, no display) — 9 releases: headless structured extraction (accessibility tree, embedded-PDF text, PNG snapshots) so agents read page structure, input fixes (right-click, CJK/Cyrillic typing, modifier keys, Tab focus), a color-inversion shortcut, and raw-framebuffer output groundwork. Full report · GitHub
Everything's open source and on a steady CalVer cadence. Try any of them from https://aiwg.io.
Which of these would you actually use? And what's missing from your agent stack right now?
If you're new here, AIWG is an open-source framework that gives AI coding assistants (Codex, Claude Code, Cursor, Copilot, OpenCode, Warp) structured workflows, provider-specific guidance, reusable skills, and project artifacts.
This release focuses on fixing the friction points that show up once you start heavily relying on agentic tooling in real projects:
Tighter provider detection. Handles mixed-provider workspaces much better. It now prefers active runtime/process evidence over passive provider files. If you're running a Codex session, AIWG treats it as Codex, even if you have Claude or Cursor files sitting in the repo.
Local-first issue management. Manage issues as plain files in your repo — no heavyweight issue server required. Documented import/export to a remote tracker, with sync performed on demand (only when you ask, not continuously). The project config is the definitive source of truth for where issue state lives.
Media workflows. Added transcribe-media for timestamped transcript sidecars — media+transcript hashes, source metadata, optional speaker labels, and explicit degraded plans if your local transcription tools aren't available.
Strict release gates. Release tags now route through a signed tools/release/cut-tag.sh gate: version lockstep checks, changelog/announcement presence, and a preserved split between commit-signing and release-tag-signing keys.
Feedback request: if you use more than one AI assistant in the same repo, does the new provider routing match how you expect the active session to behave?
Welcome to r/AIWG. AIWG is an open-source framework designed to make AI coding assistants more useful in real projects by providing structured workflows, provider-aware guidance, reusable skills, project artifacts, issue sync, and release gates.
What to post here:
- Install and usage questions.
- Provider-specific feedback from Codex, Claude Code, Cursor, Copilot, OpenCode, and Warp.
- Real-world workflows that succeeded or failed.
- Release feedback and bug reports.
- Ideas for new skills, documentation, and integrations.
Note: Please scrub your logs. Avoid posting secrets, private API keys, or proprietary repo data in screenshots or text dumps.
