0 Fork 0

Files

T

OpenHarness BotandClaude Opus 4.7 a4642042de feat: oh config slack — in-sandbox Slack integration setup wizard

Standalone CLI at apps/oh/ (Node TS, esbuild ~13kb, no runtime deps).
Walks user through token entry (xapp-/xoxb- prefix validation), allowlist
mode (users/channels/both with U…/C… ID validation), atomic .env merge
(temp+rename for crash safety), and agent-pi tmux restart with
'connected and listening' poll. Pluggable as oh config <integration>
namespace for future github/postgres/cloudflare wizards.

Bundled prerequisites and adjacent polish:
- Migrate .pi/extensions/slack/{index,tools}.ts from deprecated
  @mariozechner/pi-coding-agent to @earendil-works/pi-coding-agent
  (per upstream npm deprecation notice)
- Sidebar label Agents → Harnesses; per-harness pages get unified
  Authentication section (codex login / opencode auth login / etc)
- New T3 Code harness page (browser UI on port 3773)
- Docs theme: prose links now green + underlined for affordance
- Slack docs § 5 leads with `oh config slack`; manual procedure
  demoted to <details> Manual fallback
- Drop orphaned .pi/onboard-steps/ (logic moved to apps/oh/)
- Makefile help adds Configuration wizards section pointing at
  oh config slack (3-agent council picked CLI over Make-target
  due to docker exec -it TTY fragility)

Closes #281

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-12 22:26:26 -06:00

4.4 KiB

Raw Permalink Blame History

Upstream Tracking

Lineage

Property	Value
Upstream	`earendil-works/pi-mono` (formerly `badlogic/pi-mono`; not directly used)
Reference Source	`.worktrees/agent/portfolio-advisor/packages/slack/` (Pi harness agent worktree)
Reference Commit	Latest on `portfolio-advisor` main branch as of 2026-05-07
Vendored	No — this is a port, not a vendor
Port Date	2026-05-07

Relationship Model

This extension is a port (one-way), not a vendor (bidirectional sync):

The reference source is .worktrees/agent/portfolio-advisor/packages/slack/ at the latest portfolio-advisor commit.
Future bug fixes in the reference code are reviewed and ported manually into .pi/extensions/slack/.
NEVER auto-sync or merge upstream/reference changes.
NEVER force-push harness changes back to the reference.

This model prevents coupling and allows each codebase to evolve independently.

Customizations Carried Over

3 of 5 harness-specific behavioral customizations from the reference port directly; 2 dissolved into Pi's native handling:

Ported (preserved from reference)

threadTs event support — events can target existing threads by threadTs field. All 8 sites in events.ts preserved (parse, dispatch, synthetic-event builder, tests).
threadParent routing — when creating a response context, if the triggering event has a threadTs, responses post to that thread (not start a new one). Implemented in context.ts:createSlackContext().
Exported testing utilities — parseEventContent() and buildSyntheticEvent() exported from events.ts for test harnesses.

Dissolved (no port needed)

Configurable LLM provider/model — was a mifune-bot-specific delta (agent runner could switch providers). Pi handles model configuration natively via its own settings.json. Not ported.
Tool output suppression (errors only) — the reference's agent.ts suppressed raw tool output, posting only status icons (✓/✗). In the new shape, this customization is obsolete: Pi's UI renders tool output natively, and the Slack bridge only posts the agent's final text response (via turn_end), never tool outputs. Not ported.

Factual Corrections to Reference's UPSTREAM.md

The reference's UPSTREAM.md contains inaccuracies that are corrected here:

threadParent location claim: Reference claims it's in slack.ts / context.ts, but actual location in reference is main.ts:121 (in the agent runner). In the new shape, it moves to context.ts:createSlackContext() since there is no agent runner.
Tool output suppression description: Reference claims "errors only," but actual behavior is status icons (✓/✗) for both success and error; raw output is suppressed in threads. This customization doesn't port anyway.

Sibling Dependencies

These packages are consumed from npm (NOT vendored):

Package	Pinned Version	Notes
`@slack/socket-mode`	`^2.0.0`	Socket Mode WebSocket client
`@slack/web-api`	`^7.0.0`	Slack Web API client
`croner`	`^9.1.0`	Cron-like event scheduler (file watcher trigger)
`chalk`	`^5.6.2`	Terminal color output for logging
`@sinclair/typebox`	`^0.34.0`	TypeBox for Pi tool parameter schemas

Quarterly Review

Owner: @ryaneggz
Schedule: Quarterly (review against reference HEAD)
Last reviewed: 2026-05-07

On each review:

Check if reference has bug fixes or features that should port.
If changes are found, create an issue with title task: port <description> from portfolio-advisor/packages/slack and PR with reference commit links.
Update Reference Commit above in this file.
Do NOT auto-apply upstream changes — always review and port manually.

Why Port, Not Vendor?

Vendoring (tight sync) couples the two codebases and makes divergence expensive. Porting (one-way, reviewed) lets each codebase evolve independently while still capturing high-value fixes. The harness and portfolio-advisor have different deployment shapes (Pi extension vs. standalone bot) and will diverge in behavior over time.

Cleanup Notes

After this port is stable and tested in production, the reference in .worktrees/agent/portfolio-advisor/packages/slack/ can be archived or left as historical documentation in case a future bot needs the same patterns. The sync relationship ends with this port.

4.4 KiB Raw Permalink Blame History