mirror of
https://github.com/aljazceru/goose.git
synced 2025-12-18 06:34:26 +01:00
docs: added note on outdated blog posts (#1171)
This commit is contained in:
@@ -15,6 +15,10 @@ However, I didn't want to spend hours implementing the CSS for each design trend
|
||||
|
||||
<!-- truncate -->
|
||||
|
||||
:::warning Goose Beta Version
|
||||
This post was written about a beta version of Goose and the commands and flow may have changed.
|
||||
:::
|
||||
|
||||
### My original calendar:
|
||||

|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ Goose will remember previous interactions to better understand ongoing projects.
|
||||
|
||||
### 3. Improved Plugin System
|
||||
|
||||
In Goose v1.0, the Goose toolkit system is being replaced with Systems. Systems are modular daemons that Goose can interact with dynamically. As a result, Goose will be able to support more complex plugins and integrations. This will make it easier to extend Goose with new features and functionality.
|
||||
In Goose v1.0, the Goose toolkit system is being replaced with Extensions. Extensions are modular daemons that Goose can interact with dynamically. As a result, Goose will be able to support more complex plugins and integrations. This will make it easier to extend Goose with new features and functionality.
|
||||
|
||||
### 4. Headless mode
|
||||
|
||||
|
||||
@@ -14,6 +14,7 @@ We're in the early days of a new era in tech, one where companies are innovating
|
||||
|
||||
<!-- truncate -->
|
||||
|
||||
|
||||
### The MCP Open Standard
|
||||
|
||||
Anthropic is leading the charge with the [Model Context Protocol (MCP)](https://modelcontextprotocol.io), an open standard that enables large language model (LLM) applications to connect with external systems, providing the necessary context for more informed and relevant AI interactions.
|
||||
|
||||
@@ -9,10 +9,14 @@ authors:
|
||||
|
||||

|
||||
|
||||
Running into Continuous Integration (CI) failures in pull requests can be quite frustrating but they happen very often. In this post, we leverage the GitHub CLI (`gh`) using Goose to simplify your CI debugging process, fetch detailed information about failed CI runs & annotations directly from GitHub, and even apply fixes directly.
|
||||
Running into Continuous Integration (CI) failures in pull requests can be quite frustrating but they happen very often. In this post, we leverage the GitHub CLI (`gh`) using Goose to simplify your CI debugging process, fetch detailed information about failed CI runs and annotations directly from GitHub, and even apply fixes directly.
|
||||
|
||||
<!-- truncate -->
|
||||
|
||||
:::warning Goose Beta Version
|
||||
This post was written about a beta version of Goose and the commands and flow may have changed.
|
||||
:::
|
||||
|
||||
|
||||
## Getting Started
|
||||
|
||||
|
||||
Reference in New Issue
Block a user